Release 5.13.2
When Telegram looks connected but messages never arrive, Check connection shows whether the token points at this instance or at another system. One bot token can point to only one system.
Operator Line
Fixed
- Full subject path in the chat header. When a subject has several levels (for example “Complaint → product → specific item”), the header shows every level instead of replacing the middle with
.... A long path stays on one line; hover to read it all. A deeper subject no longer falls back to No subject. - Process dropdown options. When a process parameter is a plain list of values (50, 100, 150), the operator sees those numbers and can pick one. Previously the rows were blank, so the process could not be run.
- Tags after deleting a client. Deleting a client card no longer strips tags from unrelated tickets.
Scenario Builder
New
- “Client Updated” event. The Start node’s internal events list now includes Client Updated. The section runs after a client card is saved in the Operator panel (card fields or Custom Data). The scenario receives the changed fields with old and new values. CRM sync can be built as a scenario.
- Scenario on ticket tag changes. When an operator changes a ticket’s tags, Ticket Updated can start a section (for example to update labels in an external system). An administrator turns this on; it is off by default.
Fixed
- Disabled transition after chat close works again. If the Connect to Operator node has scenario transition after chat close turned off, the scenario no longer continues anyway. Check scenarios where that transition must stay off: after the upgrade, behaviour matches the saved setting again.
Channels
New
- Telegram connection check. In Telegram channel settings, Check connection shows whether messages go to this instance (Connected to this system). If another system intercepted the token, the verdict is Intercepted by another system — you then see the actual delivery address.
Fixed
- Instagram waits for the data-collection step. After the customer enters a phone number, the bot asks for a name (Wait for Input). The scenario no longer advances without an answer. Registration could previously finish with the Instagram profile name.
Improved
- Email dialogs by real sender. After an administrator enables it, emails group by reply address, otherwise by sender address — not by a shared subject. Different people with the same subject land in different chats. One customer with new subjects stays in one open chat. The bot’s auto-reply goes to the real customer, not the forwarding address. Off by default.
Statistics
Fixed
- One date = that day. On the Main statistics tab, picking a single day and clicking Apply filters reports that day, not the whole current month. Skill group, bot, and channel survive a page reload.
- Table columns after sorting. On Operators — volume metrics, sorting by operator or missed no longer collapses the table to one column or resets your visible-column set.
- FastLine widgets. Metrics such as FastLine dialogs total count the same dialogs FastLine actually took part in, not a different chat set.
- Working hours after deleting an operator. When you delete or deactivate an operator (Settings → Users), the Contact Centre PRO (Working hours) report closes the last interval at deletion time. Previously a status bar (for example waiting) could keep running for hours after the account was already off.
Quality Assurance
Fixed
- A failed AI evaluation no longer looks like success. If the agent returns no result, the card shows Evaluation failed with a reason and Retry evaluation. There is no green success message and no invented 100/100. In the assessments list the row has a Failed badge and “—” instead of a score. The average in My Assessments is no longer pulled down by zeros from dialogs that were never scored.
Bulk Messages
Fixed
- “Go to Clients” button. On step 3 of Bulk Messages onboarding, the button opens the Clients section again.
Settings
Fixed
- Scenario secrets: clear errors and a working save. In Settings → Scenario secrets, an identifier in capital letters with underscores is rejected. Use lowercase letters and hyphens (for example
crm-api-prod); save is blocked immediately, with the rule under the field. Types such as SMTP, Telegram bot, or a generic secret can be created with the All actions consumer again. If the type is incompatible with Send Request, the form warns before save.
Interface
Fixed
- Icons in Firefox. In Firefox, the Operator panel icon in the main menu no longer covers the label. Left-sidebar tab icons line up with the other items.
Please note
- Email grouping by sender applies to new incoming mail. Open chats are not split or merged after the upgrade.
- If you temporarily duplicated the name-collection step after the Instagram phone step, check the scenario so the customer is not asked twice.
- If the Connect to Operator node has transition after chat close saved as off, the scenario will actually stop on close after the upgrade. That is expected.