I have a Watson Assistant integrated with Facebook Messenger and I need to sent a welcome message to the users when they start chatting. I used the conversation_start before for this but this time it's not working and I cannot figure out why!
https://imgur.com/NPGaL89
The conversation_start condition didn't work on the "Try it out" on the IBM-Cloud I think because the welcome condition works instead but it did work on FB messenger.
What caused this confusion: I was trying the conversation_start condition by entering an emoji (which worked for me before), but now it works only with text and doesn't work if the first user input is an emoji.
Related
I created Lex chatbot and tried to configure it with the Facebook page. The bot is integrated completely, and also replying to me perfectly. The only reason I am facing is that my Lex bot doesn't reply when someone else tries to reach it.
In the start, I thought it was due to a status issue, but now I set my app's status to live but didn't get a response when I tried to text it through another account.
I created a DialogFlow app that works perfectly in my developer account.
But I need to test it as another user, so in my Google Action simulator, I added another test account as a OWNER to the project.
I verified this user has OWNER status in both the DialogFlow and Google Action UI.
They are able to edit both projects with full access.
However, when the test account tries to use the simulator it says:
Sorry, this action is not available for your app. Sorry, this action
is not available for your app. In the simulator, you are only able to
invoke actions that you have added to your app. For more information
on how to invoke your app, click here
https://developers.google.com/actions/discovery/explicit
This makes no sense to me:
I verified the test user has OWNER/ADMIN status on both DialogFlow and Google Actions for the project.
In DialogFlow, I verified the Google Assist is pointing to Default Welcome Intent as the default intent.
In Google Actions, I verified that the Default Welcome Intent is visible on the BUILD > ACTIONS UI.
As others suggested, I tried renaming the app several times with no luck.
I tried publishing an Alpha version, with still no luck.
My gut tells me it is some sort of permission/visibility problem, but I am completely stuck. Any ideas would be of great help.
EDIT:
THIS ISSUE HAS BEEN SOLVED. SEE COMMENT BELOW.
"I revisited my activity controls and noticed my "Web and App Activity" had a special clause due to organization permissions. I completely missed it due to the confusing UI. Posted a picture in the main thread. Thanks for reminding me to double check that area."
After you asked your company admin to enable this feature, it should be same as the image in below.
This error message is quite misleading. I have encountered this error a couple of times, and generally the problem was with one of the privacy settings in my Google account.
In this case you should go to https://myaccount.google.com/activitycontrols, confirm that you are logged in using your test account, and make sure the following are enabled:
Web & App Activity
Device Information
Voice & Audio Activity
I've written a simple bot for Facebook Messenger that takes a user's text, applies a simple transformation and immediately returns the result.
While testing it myself, I've never had a problem, but it seems that for some users, Facebook returns the following error when the transformed message is sent back (from my server logs):
"www-authenticate": "OAuth \"Facebook Platform\" \"invalid_request\" \"(#551) This person isn't available right now.\""
Any ideas what the cause of this would be? It seems to arbitrarily happen to random users, and users should be available as the result is returned immediately.
Thanks!
This is currently a confirmed bug on the Facebook platform. Bug location: https://developers.facebook.com/bugs/465154327166499/ (as mentioned by #m90, Facebook developer account is required to view it).
Bug description and steps to reproduce:
Have a new Facebook user (who never interacted with your app before)
With that user, ask anything that normally produces automated response from the app
Expected result:
Bot should respond
Actual result:
For apps in development mode it is error code 551 as following:
{"error":{"message":"(#551) This person isn't available right now.","type":"OAuthException","code":551,"error_subcode":1545041, ...
For apps in production mode (already submitted and public) it is error 200 as following:
{"error":{"message":"(#200) This person isn't available right now.","type":"OAuthException","code":200,"error_subcode":1545041,...
Note: if the user sends more messages, bot starts to reply normally after the 2nd message from the same user.
Based on the information from the Facebook Platform bug page, the bug has appeared in the end of May 2017. On our side, we have been noticing this for the last week (since around June 5), important to note that new app submissions are also failing because of this issue.
UPDATE June 09, 2017 Bug is marked as fixed and works on our side now. If you still experience issues, Facebook asks to comment on the bug page.
I got the same error, It was due to the fact that my page was unpublished. Once I published the Facebook Page this error was gone.
Maybe FB user has set a barrier to your page.
trying to run a 'Traffic' ad to a Facebook Messenger bot.
In order to initiate the bot conversation I need to use the 'Get Started' button as part of the messenger ad conversation and therefore need to use the "Structured Message (JSON)" option.
I cannot submit the ad since it always fails with this error
"Invalid Page Welcome Message for Messenger Destination Ads: The Message Text (page_welcome_message) is invalid for ads with Messenger as destination."
It's unclear what "page_welcome_message" is and where to set it.
I tried researching the FB community and tried to reach out but to no avail - although I did find other people with the same issue.
Turns out that the JSON that Facebook creates using the "Quick Creation" feature is causing the issue.
With a manually created JSON, I'm able to submit the ad successfully.
It's not very clear to me and perhaps other devs as well. I've read the Facebook Messenger docs maybe 5 times and I can't understand how bots detect when a user enters their chat window.
I started by looking for a postback, when users entered the bot experience. No Postbacks. I looked to see if it was Messenger Greeting, and that seems to only apply the first time a user arrives in your bot experience. This also seems a little different.
It's possible this functionality is not available to everyone. But Poncho has done this several times when I enter their experience and don't type anything.
Anyone seen this or have any ideas?
The postbacks are something completely different. The postbacks are received only when a user clicks on a button which contains a payload mentioned in the payload element of your button template or structured message. Facebook chat bot API sends this payload back to let you know that the user has clicked on a particular button.
What you're looking for is called Welcome Screen and you're right, the default behavior was not clearly listed in the documentation. But one of the Facebook engineers cleared the doubts for me and now they have edited the documentation. The welcome screen appears once and only once for a user on the messenger app i.e the first time when the user interacts with your chat bot even if the user deletes the conversation. From the docs:
The Welcome Screen only appears for new conversations. On mobile,
deleting conversations will not cause the Welcome Screen to appear
again. On desktop web, if you delete the conversation, you can make
the Welcome Screen appear again.
Where as, the behavior is different for the regular Facebook chat in a web browser. A user can see the Welcome Screen in the regular chat if he/she deletes the conversation.
There's no way to detect that the user has just entered the bot experience. I've tested Poncho bot before and I don't get any message when I enter the bot experience after the first conversation.
There's a possibility that you're experiencing this because of Watermarks. Watermarks are received on our webhook when a message is delivered and read by the user. May be they are handling watermarks in such a way that if the timestamp that comes with the watermark is few hours late than the current time, they send the message. You can read further about watermarks in the official documentation here and here.