Publishing Chatbots

Learn how to make your chatbot available on a wide variety of messaging channels - website, social media, collaboration tools, voice assistants.

When you are finished developing your chatbot, you need to publish it to one or more channels.

NativeChat supports a wide variety of channels for different kinds of use cases:

Feature Comparison

It is important to know that each channel has different support for the chatbot features. Some channels could have richer messages including images, quick replies, etc. but others (like SMS or voice channels) might not. Check the support if you are planning to use a specific channel feature and provide workarounds.

Feature Facebook Viber Web Mobile Amazon Alexa Twilio SMS Twilio Voice REST1 MS Teams LINE
user profile info2 yes yes no no no no no no yes3 yes
user timezone no no yes yes no no no yes no no
quick replies yes yes yes yes yes yes4 yes yes yes4 yes
single select yes yes yes5 yes5 no no no yes5 yes4 yes
multi select no no yes5 yes5 no no no yes5 yes4 no
carousel yes6 no7 yes yes no yes4 yes yes yes yes
location picker yes8 yes8 yes9 yes9 no yes9 no yes no yes8
date picker no no yes yes no no no yes yes no
authentication yes yes yes yes yes no no yes yes yes
handover yes no no no no no no yes no no
file upload yes6 yes yes yes no yes no yes yes yes
typing indicator yes6 no yes yes no no no yes yes yes
ssml support no no no no yes no yes no no no
rich text10 yes yes yes yes no no no yes yes no
search fallback yes11 yes yes12 yes12 no yes13 no yes yes yes11
live agent yes yes yes yes no no no yes yes yes

  1. REST channel supports all UI features, provided the channel which you are integrating with can implement them ↩

  2. includes first name, last name and avatar URL ↩

  3. includes only first name and last name ↩

  4. lists the items in text format ↩ ↩2 ↩3 ↩4 ↩5

  5. Support filtering. ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  6. Due to Facebook API restrictions applied to pages and users from the EU these features might not work. For more information see section Restrictions for EU citizens and businesses ↩ ↩2 ↩3

  7. shows single select instead ↩

  8. mobile version only ↩ ↩2 ↩3

  9. requires a Google Cloud API key and falls back to the default location if the user does not grant permission to the browser to use geolocation. ↩ ↩2 ↩3

  10. depends on the native support of the UI for the specific channel ↩

  11. Carousel and Text formats are natively supported. Quick action buttons will default to Carousel format. ↩ ↩2

  12. Quick action buttons format is natively supported by NativeChat Website Widget version 3.3.1 and higher. In NativeChat Website Widget version between 3.2.0 and 3.3.1 will default to Carousel, in NativeChat Website Widget version lower than 3.2.0 will default to Text.
    Carousel format is natively supported by NativeChat Website Widget version 3.2.0 and higher, in NativeChat Website Widget version lower than 3.2.0 will default to Text. ↩ ↩2

  13. Text format is natively supported. Quick action buttons and Carousel formats will default to Text format. ↩

Somethings missing or not clear?

Ask a question in our community forums or submit a support ticket.