Docs are current in the making

Message Types Supported

Since FlowBridge Connect v7, we have pushed to have feature parity across all channels. This means all message types supported here are supported on all channels.

Message types from Voiceflow

Currently we support all message types from voiceflow, though they may behave differently on different channels. One example is the Carousels, as WhatsApp, Slack and Telegram don't natively support Carousels, we convert each carousel item in to individual cards and send them over as such to those channels so the functionality will continue to work, all be it through indiviual cards. We support:

  • Text

  • Images

  • Cards

  • Carousels (Though read the message above)

  • Buttons

  • Agent steps + Carousels/Buttons they may create

  • All the remaining steps are being handled on the voiceflow side such as set variables & condition steps. They will work by default as they do not require processing by FlowBridge

Message types from social channels

Similar to the above, we have strived as part of FlowBridge Connect v7 to have feature parity on all channels, so all channels support:

  • Messages from the user

  • Images being sent by the user

  • Files being sent by the user

  • Voice notes (They automatically get transcribed and sent to Voiceflow as normal text)

  • Location message (This will set variables automatically, see Automatically Populated Variables)

  • Video messages

  • Stickers (For Meta platform)

Voice Notes

One of the great things FlowBridge Connect offers is the ability to accept voice notes. This requires not changes in your flow what-so-ever and works on all social channels. We use the open AI whisper model to convert speech in to text and send it over as text to your Voiceflow project. This means out of the box, users will be able to send voice messages and it will just auto-magically work!

Last updated