Release 5.3.41

What changed

  • Chat routing and Operator Panel stability: fixes for cases where, after transferring a conversation between skill groups, the chat was not assigned to an operator or the UI behaved inconsistently.
  • More predictable Telegram event handling: messages in the same chat are processed in a safer order — lower risk of duplicates or events “jumping” during peak load.
  • Chat close reason: the system records closure context more accurately — easier to understand what happened in the conversation.
  • Distribution audit: event history is retained longer so routing incidents are easier to investigate.
  • Quick replies: stronger checks for edit/delete permissions and clearer hints about current settings.
  • Broadcasts: simpler template management when a scenario trigger is enough, plus safer handling when building an audience from a file.
  • Custom Data: quick reset of global filters and the date range to return to a “clean” data view faster.
  • Quality Assurance: improved AI assessment view and interactive checklist (scores and comments).
  • Interface: better readability of some working-screen elements (text and icon contrast).

How it changed

Previously, after a skill-group transfer a conversation could stay unassigned or render incorrectly; when several messages arrived at once in a messenger, processing order was not always predictable; some workflows needed extra steps for checks and diagnostics.

Now, routing after transfers is more stable, and handling of events within one chat is more sequential. It is also easier to monitor and analyse key events (distribution, closure) and to work with broadcasts, Custom Data, and QA assessments.

Why it matters: fewer “stuck” conversations and inconsistent states for operators, more predictable messenger behaviour under load, and faster investigation when something goes wrong.