[Feature Request] Facebook Messenger Feature Requests

[EricDahlvang]

We are reviewing Facebook Messenger features and support. We would like feedback from the community on which features would be most useful. I've looked through the current Feature Requests on this repository, and compiled this list of what seems to be most requested:

~~Multiple Facebook page access tokens https://github.com/Microsoft/BotBuilder/issues/1495~~ (implemented)

~~Add Channel: Workplace by Facebook https://github.com/Microsoft/BotBuilder/issues/2821~~ (implemented)

~~Add support for Facebook Message Tags https://github.com/Microsoft/BotBuilder/issues/2924~~ (implemented)

Show Facebook Webview and Chat Extensions https://github.com/Microsoft/BotBuilder/issues/2250 https://github.com/Microsoft/BotBuilder/issues/3385

~~Handover protocol https://github.com/Microsoft/BotBuilder/issues/4360#issuecomment-444409054~~ (implemented)

setPersistentMenu https://github.com/Microsoft/BotBuilder/issues/4360#issuecomment-400128836

Add support for Facebook Checkbox Plugin opt-in

4199

Buy Buttons using Stripe/Facebook Payments and other buttons (share, location, email, phone number)

4664

Please let us know what Facebook Messenger features or functionality you would like to see in the Bot Builder sdk.

[hpksp]

@EricDahlvang I would vote for having Multiple Facebook page access tokens. In our case we want to link the same bot to different FB pages owned by different customers (Multi-tenant scenario). Thanks for asking our opinion :+1:

[amitbend]

I would ask for support to ref params, and special quick replies such as location, email, phone number etc.

[cove-ming]

We would like support for the Facebook handover protocol. We are able to able to pass thread control from the bot since it's just an HTTP call, but are unable to receive the messaging_handovers event via the Bot Connector.

One solution apparently is to put a proxy between Facebook and Bot Connector to capture that event, but that's far less than ideal as it's added latency.

https://developers.facebook.com/docs/messenger-platform/handover-protocol#handovers

[glasody]

We would love to see multiple page access tokens get implemented which would mean changes in the Bot connector also in azure. We recently ran into a problem trying to use the same bot for different pages. If this isn't implemented, we would have to create new fb apps, get then approved again and register new bot channels in azure.

[xjose97x]

I believe Facebook Webview would be a great feature. The Spotify chatbot (in their facebook page) uses it heavily and provide a great user experience.

Thanks for asking our opinion @EricDahlvang :+1:

[millimoose]

Subscribing a single bot application to an arbitrary number of pages for the same FB app is essential to what our team is trying to accomplish. (Serve many locations of similar businesses with slightly varying offerings between them. I.e. a bot platform with multiple tenants.)

[rysbilinski]

+1 for multiple facebook page access tokens. Thanks

[EricDahlvang]

Add support for Facebook Checkbox Plugin opt-in

https://github.com/Microsoft/BotBuilder/issues/4199

[jhaala]

There's so many important features needed for Facebook. I've had to start bypassing core functionality to make bots work with it. BotBuilder has the best dialog handling, so I haven't given up on it yet in hopes that necessary features like these will start being added.

+100 Multiple page access tokens (Essential for development companies)

+1 Facebook Message Tags

+1 Webviews

+1 Handover protocol

+1 Facebook Checkbox Plugin

+1 Buy Buttons using Stripe Payments

4664

+1 Other buttons (share, location, email, phone number)

[EricDahlvang]

setPersistentMenu

[Sire]

Chat Extensions for their excellent sharing functionality. Without a powerful way of sharing the bot with your friends, it will never be discovered.

https://developers.facebook.com/docs/messenger-platform/chat-extensions/best-practices

[EricDahlvang]

Provide a way to set messenger_extensionswithout requiring the entire message be built using the FB native format in .sourceEvent or .channelData

ref: https://github.com/Microsoft/BotBuilder/issues/4852

[Alexander-0x80]

+1000 To Multiple Facebook Page Access Tokens

[kevinport]

+1000 To Multiple Facebook Page Access Tokens

[amitbend]

@EricDahlvang Multiple Facebook Page Access Tokens was not about to be released a few weeks ago?

[giladaya]

Supporting multiple page access tokens is mandatory for many use cases. It's literally a show stopper for me in my current project :/

[mgbennet]

We're very close to supporting this. I need to change a number of things on the channel configuration page, and then it should be ready for use. I'll give a more exact date when I can, since it depends on our deployment schedule, but soon™.

[rysbilinski]

Great news @mgbennet

Will there be an API available to add new tokens to an existing bot?

[mgbennet]

@rysbilinski Currently we don't have a public API for configuring channels. You'll have to go through the configuration page.

[rysbilinski]

Thanks for the response Mike.

Is a public API on the roadmap?

[amitbend]

@mgbennet Any updates?

[mgbennet]

@rysbilinski I don't think we have a public API for channel configuration on the road map. It may come some day, but I don't believe any work is being done on that front right now.

Multipage Facebook configuration should be available in the next couple days. I'll post again when it's live.

[mgbennet]

It's live! Go to the Facebook channel configuration page, and you can add multiple pages. Let us know if you encounter any bugs.

[SPACEGHOST904]

So, not clear from this thread. Was Workplace by Facebook channel added?

[EricDahlvang]

@SPACEGHOST904 No, MBF support for Workplace by Facebook has not yet been added.

Bot Framework now works with Facebook workplace: https://docs.microsoft.com/en-us/azure/bot-service/bot-service-channel-connect-facebook?view=azure-bot-service-4.0#connect-a-bot-to-facebook-workplace

[SPACEGHOST904]

Thanks

From: Eric Dahlvang notifications@github.com Sent: Friday, August 17, 2018 1:53 PM To: Microsoft/BotBuilder BotBuilder@noreply.github.com Cc: John Thompson john.thompson@avogadro-creative.net; Mention mention@noreply.github.com Subject: Re: [Microsoft/BotBuilder] Facebook Messenger Feature Requests (#4360)

@SPACEGHOST904https://github.com/SPACEGHOST904 No, MBF support for Workplace by Facebook has not yet been added.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/BotBuilder/issues/4360#issuecomment-413985354, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AblqDMODkk9YJ1VYlP3In4BV8aqCQGbTks5uRy1IgaJpZM4S334c.

[marcasmar94]

These would be great if added as they make a great UX we currently use them by sending them as channel specific data

- Media Template - Email Quick Reply - Phone Quick Reply - List Template - Receipt Template

[JasonSowers]

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.

From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.

As part of this restructuring, we are closing all tickets in this repo.

For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here: https://github.com/microsoft/botbuilder-v3/issues

For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here: https://github.com/microsoft/botframework-services/issues

For product behavior, how-to, or general understanding questions, please use Stackoverflow. https://stackoverflow.com/search?q=bot+framework

Thank you.

The Bot Framework Team

[EricDahlvang]

Note: Message tags can be done with the Bot Builder by using Channel Data:

dot net sdk:

activity.ChannelData = JObject.FromObject(new { tag = "APPLICATION_UPDATE", messaging_type = "MESSAGE_TAG" });

node sdk:

   let msg = new builder.Message(session).sourceEvent({ facebook: {         
      "messaging_type": "MESSAGE_TAG",
      "tag": "NON_PROMOTIONAL_SUBSCRIPTION",
      "text": "Hello Facebook!"
    } });

[gostore-aicom]

+1 Handover protocol

[Alexander-0x80]

+1 to Handover Protocol

[odannyc]

+1 Handover protocol

[Unders0n]

@EricDahlvang trying to know if we can use botbuilder in FB group chats, is messenger_extensions is the only way to address that and so i should track #4852 ? Thanks

[EricDahlvang]

@Unders0n I have not heard of bots in FB Group Chats. I do not know if it is possible right now. Please file an issue here: https://github.com/Microsoft/BotFramework-Services and we can flag it as a Feature Request for the Messenger channel (if it is not already supported).

[dchathu]

Can we use the same bot in Facebook Messenger and Workplace by Facebook at same time? There is no option in channel settings to configure both at the same time. Any solution?

[Unders0n]

@EricDahlvang , hi any updates on Webview and Stripe/Facebook Payments features? If not implemented natively, how do you think would it be possible to address using workaround like ChannelData and webhooks?

[EricDahlvang]

Hi @Unders0n

I don't know about Facebook Payments, but you can do WebViews with ChannelData. Please find a node.js example here: https://stackoverflow.com/questions/55087150/messenger-webview-for-botframework-v4/55128551#55128551

The Bot Framework Services team might have more information. If you wish to pursue this further, please open a feature request here: https://github.com/microsoft/BotFramework-Services/issues

[chybisov]

Any updates on Facebook Checkbox Plugin opt-in?

[thejvdagaang]

have the ability to pin chats on top

[shayandaneshvar]

Delete Spam messages automatically after some fixed time range, e.g. a week or a month. I have Spam messages that are 10 years old!!!