Overview: the Automation section

The Automation section of iAdvize allows you to create chatbots and automate some or all of your conversations. This video briefly summarizes the possibilities, and this article introduces you to each of its sections.



You can refer to our article “What's a bot for?” for ideas on what a bot can do for you and your team.



The “Bots” section and the bot builder

This section is the entry point for all your bots on iAdvize, no matter how complex they are. You will find a list of all bots on a project, in all languages, enabled or disabled. It is also from this list that you can create or duplicate your bots or copy them from another project.


When you create a bot, you first determine its name and settings in the “Identity” section, then configure the steps of its conversation in the “Scenario” section using different types of cards – you can see the list of different types of cards in this article.


To learn about our tips and best practices for building a script, read our articles “Design a scenario for your bot: the essential steps” and “Our writing tips for a helpful, likeable bot”.


The section “Intention Manager” and Artificial Intelligence

The “Intention Manager” section gives you access to the features associated with artificial intelligence, and the detection of your visitors' intentions, language by language.


Why does artificial intelligence work by language?
Intention detection is entirely language-based because artificial intelligence works by recognizing visitor expressions and associating them with similar expressions it already knows and attributed to intentions. Intention detection and bots can only work in one language at a time!

In this section, you can enrich your intentions with suggestions from AI or those your team has given you through collaborative training. You can read our detailed article on intention detection here, as well as our practical tips on using artificial intelligence.


The “Entity Manager” section, for additional references

This section allows you to take into account specific expressions, which would otherwise blur the detection of intent: telephone number, product references, destinations, etc.


To detect entities, the bot always relies on entries, which can be of two types:

  • Value lists: you list reference values (e. g. a list of destinations: Nantes, Paris, Venice. . . ) to which synonyms can be associated (for the reference value “Paris”, you can enter for example: “Paris, France”, “city of love, “the capital”, etc. ).
  • regular expressions correspond to specific shapes that the bot will recognize for sure: email address, telephone number. . . but also order number or parcel tracking number!
    You can see our detailed article on entities.

You can see our detailed article on entities for more information.

The section “API connection”

This section allows you to create a connection between your bot and an external API, to allow, for example, your bot to autonomously answer your visitors on follow-up questions, or to search for an answer on your FAQ.
Once your API connection is configured and variables identified, you can re-use them in your bot scenario using an “API Connection” card.


To use this feature, you can read our detailed article on API Connections.


The section "Automated flows" [Beta]

Automated flows allow you to automate actions or series of actions associated with a conversation.
Two types of automated flow are currently available: the email request and the estimated wait time. Thanks to these functions, you can customise the trigger criteria, durations and messages via which you automatically request their email address from your visitors. And you can also tell your visitors how long they have to wait before speaking to an agent.

Find out more about automated flows for email requests and estimated wait time, their benefits and how to set them up in our dedicated articles.



Detail of functionalities and best practices

Need more information?

Find all the features associated with bots, and all our tips and best practices.