9.1.x Release Details

The Kore.ai Platform now supports the RingCentral Engage as a channel to launch your assistant. Learn more.

This release includes a powerful way to enable multilingual virtual assistants. You can select the specific languages to be enabled for your assistant and also the language to be used for building the NLU models. The NLU model is used for training the assistant, and it can be different from the assistant’s language.

The NLU model can be built using any of the standard 26 languages or you can also choose to use the Multilingual Model. The multilingual model is a language-agnostic NLU model pre-trained with 100 plus languages.

You can also copy the training data, FAQs & Answers, Ontology Structure, Small Talk, and Traits while enabling a new language for a VA.

These features are available for the Standard as well as the Universal assistants. Please ensure to have a common set of languages for Universal assistants and their linked assistants for an optimal experience. Learn more.

You can now customize the appearance theme of the Web/Mobile Client directly from the Builder. This is applicable for both the Kore.ai hosted client as well as the clients hosted directly by you.

You can customize the Web/Mobile Client so that the end-users interact via a Web Client that reflects the business’s branding. Learn more.

The platform now allows a new user to sign up to the Kore.ai XO Platform using Google, Microsoft Office or LinkedIn profiles.  Learn more.

The platform now has enhanced the navigation for the user to start building an Assistant using the Storyboard. The user can build Dialog Tasks, FAQs as well as Mock Scenes from the Storyboard. The Scenes created in the Storyboard are now referred to as Mock Scenes. 

In addition to the above, the Fallback and Welcome tasks are now created automatically for every new assistant. Learn more.

The Kore.ai platform has improved the store template installation and simplified the post installation by allowing users to select values for variables defined for a template. You can also explore the assistant without completing the setup. Learn more.

Kore.ai’s Web/Mobile client is one of the most popular ways to interact with the Virtual Assistants (VA). You can now leverage the Kore.ai hosted Web/Mobile Client so that you don’t have to custom host the SDK. 

• Kore.ai Hosted Web/Mobile Client – Configure the virtual assistant using the Kore.ai hosted Web/Mobile Client 
• Embed Code – You can embed the client script directly into your application.

You can also directly share a URL with your customers so that you can interact with the virtual assistant. 

The Kore.ai hosted client also supports Panels and Widgets. If you would like to present panels or widget to your customers, make sure to enable and publish the Widget SDK Channel. Learn more.

Starting from this release, in the Standard Bot, the Default Dialog feature is transformed into a new event called Intent not Identified. If you have already configured a Dialog Task as your Default Dialog, then the platform automatically links your task to the new event. 

Note: The Intent not Identified event cannot be disabled. However, you can customize the event as you need.

In the Universal Bot (UB), you can customize the ‘intent not identified’ event’s behavior in the UB. You can either trigger the Default Dialog of the Universal Bot or any of the tasks from the linked bots. Learn more.

The Event Handlers are now classified under Conversation Events, Intent Events, and Channel Events for better organization and discovery.Learn more

The platform now allows you to import and export the Intent Patterns without any dependency on the task definitions. You can select the Patterns category under the NLP Data to import intent patterns and negative patterns from the bot definitions. You can also choose the option to either Append or Replace the patterns and negative patterns for the incremental import.

You can export the intent patterns from both Published and In-Development Assistant versions. Learn more.

The platform now lets you present the original values of the PII data fields to the customers for confirmation purposes. For example, you can securely redact an identity number but can choose to read out or present the original value to the customer for confirmation.  

By default, this option is turned-off for all entities. You can choose to present the original values by selecting the option using the ‘Redaction of PII Data’ configuration of the Entity nodes. Learn more. 

Note:  The PII information is always redacted/masked in the Chat History, messages, prompts and all other components irrespective of the option selected

The platform now lets you upload linked FAQs in bulk using a CSV or JSON file without a need to search for each individual path to link the FAQ.

Starting from this release, the ‘faqLinkedTo’ is populated with the ‘que id’ of the source FAQ. However, the ‘faqLinkedBy’ column is updated automatically by the platform with the ‘que id’ of the newly linked FAQs. Learn more.

The platform has now introduced a feature to set the user input language only after receiving a certain number of inputs from the users. 

Navigate to the Language Selection Logic and you can enable the Set the user input language on execution count for Per Session or LIfetime options under Language Selection Timeframe. You can choose a value between 1 to 5.  Learn more.

In this release, you can add any Assistant and set permission automatically to execute a process application directly from the Conversational Trigger’s properties panel.

When you add an Assistant, the platform will automatically add the required permission under the bot permissions section implicitly for the selected Assistant.

You can also add multiple Assistants to the conversational trigger from the bot permissions page. Learn more.

Note: You can add or delete any bot that is accessible by account admin.

You can now add an instance to a form and define all the necessary access controls and use it at multiple steps as per business requirements.

You can inherit access controls from one  instance to another instance.  You can change the properties of all the form components from in the new instance as per your requirements.

You can also add instances from the step or from the Form Builder in the platform.

Click the Add Access Control link in the form builder to provide a name for the instance and select the access controls are inherited from.

Click the Edit Access Control link to make any changes to access control of the instance. Once access control is changed, these changes are applied across all the steps where the same instance is used. Learn more.

Kore.ai Platform has now introduced the support for sending proactive notifications to your users. You can send proactive updates to your users even if they have not interacted with a virtual assistant before. The feature is provided via an API.

Note: In this release, Proactive Notifications are supported only on the Microsoft Teams channel. Make sure to enable the Proactive Notification settings for the channel to use this API. Learn more.

The platform now supports concept in multiple languages in the Look Up and List of Values entity nodes. Learn more.

The platform is now updated to support the Google Hangouts configuration and branding changes. The Hangouts chat is now changed to Google chat and Hangouts chat API is changed to Google chat API in the platform.

The configuration procedure to publish a bot in Google Chat channel is also updated. Click Learn more for steps.

You can view the status of the publish requests from the Status Docker of the Builder. This will be helpful for virtual assistants with a high volume of tasks or training data as it might take longer to publish them. It displays the status for both successful and failed publish requests.

The Publish Status can be viewed from the Bot Builder as well as from the Bot Admin Console. A new status API is also introduced to track the publish requests made via API. Learn more.

In this release, the approval task and form task are replaced with the Human Task. Human task offers the abilities of both the approval and form.

In the Human Task, you can now select All the channels along with the bot(s) that are available in the Delivery Channels drop-down. The Delivery Channel shows all bots that are associated to a channel. For example, if there are two bots associated to a Slack Channel you can select both from the drop-down.

You can also select the same configuration for multiple channels to avoid rework. The platform allows you to create a section and by default, the email channel is selected in the Delivery Channel for that section. You can select or unselect the email channel by clicking the action buttons in the section. You can use the Notify stencil to notify users on multiple channels. Learn more.

Note: You can select multiple channels for a section provided the Human Task is selected while configuration.

• There are times when you do not want to present certain information to your users. To help you achieve this, Knowledge Graph now supports disabling selected nodes or FAQs that are invalid for a certain period. You can re-enable these intents anytime when your business needs them. Also, explore the new FAQ API to synchronize the responses and the status of the KG intents. Learn more
• The Webhook channel has a new version of the APIs (Version 2.0) with standardized request and response formats. This release includes a web client for the Webhook channel.
• The Voice Channel’s error flows are standardized to always invoke the call termination handler. 
• The Virtual assistant definition files now support version compatibility checks to prevent imports in non-compatible application versions. These checks are applicable only for the on-premises installations with different application versions in different environments.  
• Slovenian is supported as a standard language now. Learn more

• Version 9.1.0 source GitHub link
• Updated to address minor bug fixes.

• Version 8.1.0 source GitHub link
• Updated with Node Module upgrade and minor bug fixes.
• Usage instructions: Botkit SDK