Version 1.67

Release Date: 12.09.2023

Now, you have the ability to get a comprehensive view of the customer conversation journey at a glance! Thanks to the added journal summary on the Conversation Details page, you can easily see details such as which intents were matched, whether it involved a live agent conversation, message sentiment, and more.
Certain changes have been made to the node connector system, including the addition of arrows for improved readability and the implementation of an auto-arrange feature for automatic structure optimization.

In the exported Excel file from the Conversation Details page, the SR confidence level is now visible.
Rating and rating comment have been added to the Conversation Details page.
In cases where we obtain the SR service from external third-party sources, we have enabled the ability to add a "Listen" button next to the text on the reporting page.
IVR integration will continue to be done in the background. The option to perform IVR integration by entering information through the interface has been removed.
On the Conversation Details page, the timestamps displayed in the bottom right corner of message bubbles have been changed from "00:00:00" to "00:00".

The listed issues below have been fixed.

When an error is received upon submitting a rating, the received error and its code did not match.
When exporting the top intents from the dashboard, some headers in the downloaded CSV files were unreadable due to column spacing issues.
In the flow design, connector lines between nodes were not displaying arrows when going from one node to another.
There was a situation where the lines connecting nodes did not overlap each other with a U-shaped jump at intersections.
When adding a list entity and importing synonyms, it was not correctly adhering to the synonym limit.
On the Conversation page, the filter list order in the customer filter field has been rearranged.
The message returned when an error related to session and conversation IDs occurred was incorrect.

After deleting a tenant, data associated with that tenant was still being retained in minIO.