Decide on a version for your deployed agent.Consider using a Log webhook to make sure you get notified when users trigger fallbacks.Make sure your app is in a ready state.For other platforms, we recommend using two different agents, one for drafts and one for production. As the feature matures, it will be supported in Narratory. This is due to the fact that versioning is an experimental and not stable function in Dialogflow at the moment. Note: currently, deploying is only supported for Google Assistant. This allows you to launch your app to users while working on new features in the same agent. On the Narratory side, deploying means freezing the current stage of your app and giving it a version. The only thing you have to do differently is to use the this Voximplant scenario script (remember to change the top variables) as your Voximplant scenario instead of the script posted in the tutorial. Voximplant supports both both incoming calls and doing outgoing calls, we recommend this getting started guide. Using Voximplant to interact over phone # There are also a number of open-source integrations available on Github, including Skype, SalesForce, Kik, Spark, Twilio, Twitter and Viber. Dialogflow Phone Gateway (US numbers only).Alexa - With our Alexa bridge, soon to be released.Google Assistant - See instructions below.Botcopy: Supporting websites and human handover through Janis.ai.Kommunicate: Supporting websites, mobile apps and supports human handover.Dialogflow Messenger: Supporting websites.This means that deploying your Narratory app on the following platforms is done in a whim: Websites and apps # Since Narratory uses Dialogflow under the hood, any integrations that Dialogflow supports work with Narratory out of the box. Supported platforms for your Narratory agent # Once you have reached the point in your creation to deploy you will find that this is an easy process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |