Skip to main content

JAICP release 1.10.14

New

  • With errors filter in dialog analytics.
  • onDialogError handler.
  • Retrieving call attempts history from the script.
  • Telephony connection via a SIP outbound proxy.
  • Disabling text input when using buttons in the chat widget and Chat API.

Improved

  • Statistics visualization in call campaign reports.

  • Embedding the chat widget in a container.

  • Sending images in Marusia.

    Docs

  • Added documentation on switching the context between different bots.

  • Added a tutorial on developing a multilingual bot.


In release 1.10.14, we have made a number of improvements to the flow of working with script errors that may occur in your chatbot:

  • A new filter for dialogs With errors has been added to dialog analytics.
  • We have implemented a new handler for dialog errors: onDialogError.

If you are an active user of call campaigns in JAICP, good news for you as well: we have improved the readability of call campaign reports and implemented a special $dialer method which allows advanced developers to retrieve the history of call attempts for the customer phone number.

Working with errors

Filter for dialogs with errors

A new filter for dialogs With errors is now available in Analytics > Dialogs. Applying the filter shows only sessions and phrases with unhandled script errors.

caution
When an error occurs during request processing, the bot cannot perform the action required by the script. Use the filter to find weak points in your script and quickly amend the issues.

Dialog error handler

If you want to set up customized behavior for errors which occur during the script execution, use error handlers in your script.

Along with onScriptError and onAnyError there now exists the onDialogError handler type, which handles dialog errors not related to the JavaScript code, such as when a transition is made to a non-existent state.

Call campaigns

Call campaign reports

The campaign results chart shows the top 8 results corresponding to the largest number of calls. All other results are aggregated into Other results.

The table below the chart shows the number of calls in different statuses as well as their percentage relative to the total number of calls.

Call attempt history

The $dialer built-in service now has a method called getDialHistory, which allows retrieving the history of completed and available call attempts for the current phone number.

tip
This method can be used for implementing advanced call scheduling based on how many calls have been already made and how many are left.

Miscellaneous

SIP outbound proxy

A SIP outbound proxy can now be configured for telephony connections. To set up a SIP proxy, go to advanced telephony settings, fill out the proxy address and port, and decide whether it should be used in the dialog with the bot.

Disabling text input when using buttons

In the chat widget and Chat API channel settings, a new option is now available: Disable text input when using buttons. With this option enabled, you can prevent clients from entering text messages when buttons are used in the script.

Chat widget embedding

For the chat widget, a new setting Embedding the widget in a container allows configuring the ID of the container element where the chat widget will be embedded.

tip
This feature is backwards compatible with the old method of embedding the chat widget via defining embedmentContainerId.

Images in Marusia

Bots in the Marusia channel can now send images. Use the standard image reply type from your script to do so, specifying the image URL and description.

caution
Images must be at least 600 pixels high, and their aspect ratio must be no more than 2:1. You also need to fill out the Service access token field in the channel settings.

Documentation updates

  • We have added a new tutorial on developing a multilingual bot. It will help you create bots supporting several languages and capable of switching freely between them.

  • We have also added technical documentation on context switching, which serves as the basis for the proposed implementation of multilingual bots.