Action Google Custom Search # Content
Learn how to use the Google Custom Search action inside your bot to answer each of your users’ queries and enrich your fallbacks.
This action’s mission is to make a research on a previously set domain or web site, from your users’ query, and displays its answers with Cards.
To learn how to create your Google Custom Search engine, please refer to this link: https://support.google.com/customsearch
User Request # Content
⚠️ This feature is not accessible by default. Do not hesitate to contact us ([email protected]) to discuss your project and benefit from this feature.
Request creation and configuration #User request feature consists in a particular configuration in your platform that will automatically create a user request each time your user reaches a specific step of a story.
Utiliser Valeur Entite # An entity’s value can be used to jump directly to the right step, without having to ask another question to the user.
We will use an example to show you how this works.
Here, we have an intent “Customer service”, containing the entity “contact” in required and “contact_channel” in non-required.
Sessions Et User Attributes # Content
Sessions and User attributes allow you to store & display information within the conversation.
What’s the difference between Session and User attributes? #A Session is limited in time, and is usually defined by a Story. You can also extend a Session if you jump from one Story to another through Steps.
On the contrary, User Attributes persist beyond the lifetime of a story. They are useful to retain information about your user, such as his name or his email for example.
Quest Ce Quun Fallback # Content
The Fallback is essential to a working chatbot. It is what happens when the chatbot doesn’t understand, which can happen sometimes — even with the amazing CKODA NLP 🙂
In this article, we will explain to you the different levels of Fallbacks in the CKODA platform, and how to create and use them.
There are three levels of Fallbacks: