• A new option was added in the Extract text Plugin that lets you store all capture groups in a variable without splitting off the first group to be stored in its own variable.
  • Fixed an issue in the Set conversation path Plugin.

Messaging API

  • A new option was added to set language


  • Request Consent feature is available for every project
  • Link to Reporting Suite



  • FAQ API (can be used from robot, setup only by aiaibot)
  • Semantic search API(can be used from robot, setup only by aiaibot)



Multi-language Support

We are excited to introduce the Multi-language feature, designed to enhance the translation capabilities within our application. Now, users can translate stories into different languages using automatic translation powered by DeepL.

Key Features and Benefits:

  • Automatic Translation: Seamlessly translate stories from one language to another with the help of DeepL’s powerful translation engine.
  • Expanded Reach: Reach a wider audience by providing content in multiple languages.
  • User-Friendly: The translation process is simple and intuitive.

How It Works:

Enable the Multi-language Module: Activate the Multi-language feature within the application settings to unlock translation capabilities.

Language Selection Setup. We will explain it more later

A translation sidebar will be available on the Story Builder page, providing easy access to the translation features.

After the translation is complete, review the translated text to ensure accuracy and make any necessary edits.

Once you are satisfied with the translations, save the changes and publish the stories to reach a broader audience.

We understand the importance of allowing users to have control over the language they prefer to interact with. Therefore, we have implemented a language selection menu that enables users to freely change the language according to their preferences.

  1. Language Selection Menu where user can choose from all the active languages supported by the Chatbot. This menu is easily accessible and allows users to switch between languages at any time during their interaction.
  2. Remembering User Preference: When a user selects a language from the menu, we remember their preference and make every effort to serve all future sessions in the selected language. This means that the Chatbot will attempt to provide a consistent experience in the chosen language whenever the user interacts with it in subsequent sessions.

Language Selection

The system employs a language selection mechanism to determine the language that will be served to the user. This ensures that users can interact with the Chatbot in their preferred language. The following methods are used to determine the language:

  1. HTML Tag: The system checks the HTML tag <html lang="..."> to determine the language preference set by the developer. This allows developers to explicitly define the default language for the Chatbot.
  2. Language Code in the URL: The system analyzes the language code specified in the URL, such as www.example.com/en/ for English or www.example.com/es/ for Spanish. This allows users to navigate directly to a specific language version of the Chatbot.
  3. Browser Language: The system automatically detects the language preference set in the user’s browser settings. It checks the browser’s language headers to determine the user’s preferred language.

Note: The priority of these methods can be customized, allowing to define the order in which the language is determined. Additionally, any of these methods can be enabled or disabled based on the specific requirements of the customer.

Fallback Logic: In cases where the user’s preferred language is not supported or cannot be determined, the system employs fallback logic to ensure a seamless user experience. The following fallback options are available:

  1. Hide Webchat: The system can hide the webchat interface if the user’s language is not supported. This prevents users from interacting with the Chatbot in a language that is not fully supported.
  2. Serve Primary Language of the Story: If the user’s preferred language is not available, the system can default to serving the primary language of the story. This ensures that users can still access the content in the primary language, even if their preferred language is not supported.
  3. Selected Language: Alternatively, the system can choose a predetermined selected language to serve to the user in cases where their preferred language is not available. This allows users to interact with the Chatbot in a different language while ensuring a consistent experience.




  • The Split text Plugin has a new output parameter: numberOfParts. It holds the number of parts the input text was split up into.
  • Fixed an issue where properties of complex variable references were lost when duplicating a project.



  • Grouping of Workflows is not lost when duplicating a project.
  • Fixed a bug related to character encoding in API requests.



  • The Workflow protocol got minor visual improvements.
  • Variables are color-coded and have the proper icon throughout the Workflow Builder.
  • New Plugin: Sleep
    This Plugin stops the execution of the Workflow for a couple of seconds.
  • In the Workflow protocol, the Set conversation path Plugin shows the actual path names instead of their ID.



  • Several small fixes in the Workflow Builder.
  • Adjust the maximum length of text variables sent to the reporting service.



  • At the end of a Workflow, a snapshot of all custom variables gets sent to our reporting service.
  • JSON webhook parameters are not read-only anymore. It’s possible to overwrite them in a Workflow.



  • Preparations for Multi-Language Feature
  • Billing cleanup