I'm trying to use the Facebook Handover Protocol with an app connected to a chatbot (made with Rasa), following the facebook documentation.
The chatbot is correctly connected to a Page and it's app is subscribed to the webhooks : messages, messaging_postback, messaging_handover and standby
Then I can set the app as primary receiver in the Page settings, but for the Secondary Receiver, "Page Inbox" is not in the list.
If I try to fill nothing for the secondary receiver, I have an error when requesting the Pass Thread Control API.
I would like to allow an operator to respond directly in the inbox rather than having to set up a second app that manages this. I saw many examples where "Page Inbox" is in the list of the secondary receiver and I don't understand why I don't have it..
https://flow.ai/blog/handle-facebook-messenger-handovers
Am I missing something? Is this option subject to EU restrictions or no longer available?
Thanks in advance :)
After several days of unsuccessful research, I gave up hoping to get an answer here or on the Facebook Dev forum.
However this morning when I wanted to try again, I noticed that the "Page Inbox" option mysteriously appeared ...
So I think the main reason could be that I was using a Facebook Page and an app created on the same day and hadn't spent a lot of time setting up the Page.
While waiting for a response to my problem, the only things I have changed are adding a username, profile picture, and banner.
Maybe it was necessary to add these (I am mainly thinking of the page username), maybe we just had to wait for some sort of "verifications" from the facebook side.
This screenshot is from the day this question was written: No "Page Inbox" option
And this one is from today: "Page Inbox" appeared
Related
I am working on a new business and created my page on FB. I tried to verify my business as per instructions at this link on fb.
The instruction article has a hyperlinked for security centre whcih opens a page with pre-populated values (which are correct values). When I clicked the "NEXT" button to goto next section, I got following error.
"Something went wrong. We're working on getting this fixed as soon as we can. You may be able to try again."
I tested this on 3 different browsers (safari, firefox and chrome) and this behaior is showing up. I further browser based extensions, ad blockers, content blockers etc for the purpose of testing this issue and this issue is coming up on all scenarios.
I raised this issue with fb help & support link on my fb page but I have not heard from them yet. I did not get any acknowledgement either. (hey fb, are you listening?)
I have all legal documents in place to upload. But neither the system allow me to do so nor anyone seems to have taken responsibility to fix this.
I am wondering that this flow must have been used by many who verified their business. Anyone to look at the situation and help me to get my business verified.?
Note : I have completed followng steps.
Buiness information primary page created successfully
Connected a WhatsApp account
Brand Safty (Domain cerificaion) completed successfully
Just the "Business Verifiaion Status" is unverified and I want to have it verified.
I appreciate possiible help to solve this problem.
See the error screen below.FB business showing error on clicking NEXT bytton
I read the documentation for facebook messenger bot but I can't find anywhere if it is possible to make two different FB bots(one test bot) and connect to the same Facebook Page(to use the same webhook. Does someone know if this is possible and is it aginst FB rules?
You're going to want to investigate the Handover Protocol (Beta). This will allow you to subscribe two or more apps to the same Facebook page. One of the apps will be configured as the "Primary Receiver", which will have control of any new conversation thread by default. All other apps will be configured as "Secondary Receivers". Any app can pass thread control to another app, but only the Primary Receiver can forcibly take control from another app.
When an app is in control of the thread, it will receive messages on the standard messaging channel. When an app is not in control, it will instead receive them on the standby channel. Standby messages look just like regular messages, except that their entry items contain a "standby" field rather than a "messaging" field.
Here's the kicker: apps are allowed to send messages whether or not they have thread control. This means that you cannot rely on the handover protocol to automatically sort out when your bot can and cannot talk. Instead, your bot will need to keep track of whether or not it has control and only respond at the appropriate times. To accomplish this, the messaging_handovers webhook will be helpful.
Facebook has provided a new version of their page Inbox which supports the Handover Protocol. When configured as a Secondary Receiver, new conversation threads will automatically be filed into the "Done" folder. If one of your apps passes thread control to the Inbox app, the conversation thread will be moved to the "Inbox" folder. When a human page manager clicks the "Done" checkbox on that conversation, the thread is moved back to the "Done" folder, and thread control is passed to the Primary Receiver.
One thing to be aware of, at least as of November 2017, is that the interaction of postback messages with the Handover protocol is a bit unintuitive and possibly even buggy. The postback documentation indicates that an app will always receive its own postbacks on the standard messaging channel, even if it does not have thread control. From the description of the "title" field of a postback event:
Title for the CTA that was clicked on. This is sent to all apps subscribed to the page. For apps other than the original CTA sender, the postback event will be delivered via the standby channel.
As the description of the "payload" field indicates though, the standby version of a postback message omits the payload:
payload parameter that was defined with the button. This is only visible to the app that send the original template message.
I suggest that this is unintuitive because it seems to me "standby" has a different meaning for regular messages than for postback messages. I mention that it might be buggy because I have found my apps often receive their own postbacks on both the messaging and standby channels. (I have taken to ignoring postback messages on the standby channel for this reason.)
Hope this helps.
Yes you can subscribe more than one app to the same Page. You will need to designate one as the Primary Receiver role in the page settings, then use the Platform's handover protocol to pass control of the conversation between that apps.
I applied twice in the google forms for a developer key for soundcloud to use a widget on my website. It has been more than 3 weeks and I have still not got any reply from them. What do I do?
I'm afraid you just have to wait until they respond. I have applied 3 times now and keep getting rejected and the response is a generic answer not explaining why you were denied. For me I think it is the APP URL, yet they don't explain, it is so frustrating.
Did you try email api#soundcloud.com on my first rejection they were very friendly and replied with advice, however second time they did not.
You can also try calling help on +4930467247600 however they have not worked for me.
Lastly I read online that one person heard nothing from them for weeks and checked his SoundCloud developer page under 'YOUR APPS' and his app was there set up and with the client id and secret etc. He was just never informed that he got it. So hopefully that is the story in your case.
For me it took four weeks. I contacted them via Twitter and Email. They responded but all they said was:
"As mentioned previously, we’re currently working through applications
as quickly as possible, although there has recently been more requests
than usual lately causing delays.
You should receive confirmation soon though."
I have a very simple use case. My app lets users send invitations to his friends, say for a birthday party. Friends then accept the invitation(and app).
I am using RequestDialog to send notifications to multiple users. Notification was sent successfully but the message is confusing to the user as it says
"User A Invited you to try APPNAME. Try Now".
Is there a way to customize this message? It should something like
"User A Invited you to his birthday party using APPNAME. Accept it now"
I believe I cannot use app generated requests as invitees hasn't authorized the app yet.
Any other ideas or workarounds to send notification, message with a link so users can click on it and accept the app and thus accept the birthday invitation?
You should use message parameter of Requests Dialog
message - The Request string the receiving user will see. It appears as a question posed by the sending user. The maximum length is 255 characters. The message value is not displayed in Notifications and can only be viewed on the Apps and Games Dashboard. Invites (requests where the recipient has not installed the app) do not display this value.
I memory serves, Facebook used to let you customize (many years ago), but, probably due to abuse, they no longer allow you to customize what the invitee sees. It's all standard. However, when the user comes to your app to authenticate, you can customize the Enhanced Auth dialog to your content.
I don't think there's a way to customize invite messages, and interestingly, to Usman Ashraf's point, as far as I can tell BranchOut can't do this anymore either (or at least I can't replicate it with their app). If anybody else can replicate it, let me know.
What you might want to do would be to allow
new_style_message: true,
Under your
FB.ui({
method: 'apprequests',
new_style_message: true,
message: "is bringing you to the UPicnic !",
display: "iframe"
},somefunction);
What this does is when the notification is sent to the user(s) , it will show up as the message instead. Not much customization but that's the least I can find.
I've used 'Are You Interested', a Facebook APP and when something on that app happens (such as a user sends me a message in that app) then I will see (to the left under APPS) a numeric value representing the number of new events that have happened on 'Are You Interested' since I last looked.
I want to do the same thing with my App, as it's also a niche dating site. I'd like to notify users when someone sends them a message or views their profile. I was told that I should search for app requests. However the code samples that I see seem to be slightly different than what I want to accomplish.
The information I am finding seems as though it is intended for me to allow my users to request things from their friends. That's completely different than what I want to do. There's no need for them to request anything from friends.
When I tried sending one to my test account, just to see what happens..it incremented the numeric value to the left under APPS by 1, which is a good thing, but the text was so generic, it was something like, "So and so is requesting something in [sitename]", but I don't want it to say that and I didn't see anywhere to change this text....furthermore, it added a 'Notification' to the very top of Facebook with the same generic request message. Again, that's not what I'm looking for. When I receive these APP Alerts for other apps, they don't add a 'Notification' up top of Facebook, and I don't want to either. I do believe that the code snippets I found under 'Requests' is something different than what I'm looking to achieve.
Just to summarize: I have a dating app, and people can send messages to eachother. I want an APP Alert (as I'm referring to it) to be seen to the left under Apps and also to the right in the bookmarks area, but I want the message to not be so generic and I don't want users to be selecting friends to request something. I want this action to come from my server and sent to the user that will be receiving the alert. I also do not want a facebook 'Notification' up top each time they receive a message. I hope I'm being clear in what I'm trying to accomplish. Thanks in advance for any guidance. -Chris