Release 5.3.39

What changed

  • In Telegram, you can set keyboard button styles (for example primary, success, or danger) to highlight key steps in a scenario.
  • Telegram group reactions are stored and shown more reliably in the operator experience, including when the update payload is non-standard.
  • For the web widget, you can set a custom channel icon in the operator line so different entry points are easier to tell apart.
  • Quick replies in the message editor safely insert text that contains characters like < and >, and multi-line content keeps its line breaks.
  • Operator workload reports fix time-in-status calculations and the daily timeline, reducing stuck segments and incorrect totals.
  • For external integrations that load large dialog lists, requests now have a bounded wait time; a lighter field set is available when you do not need the full record.

How it changed

Previously, Telegram keyboard buttons could not be styled from the builder; group reactions sometimes failed to persist or display; every widget looked the same in the chat list; quick replies with special characters could break the editor HTML; operator status statistics could show timeline anomalies; very large dialog list queries could run too long or use excessive resources.

Now, button styles are configured in the constructor and reach Telegram clients; group reactions are handled more defensively; widget icons can be customised per setup; quick-reply insertion escapes risky characters and preserves line breaks; status timing aligns better with real state changes; large dialog lists can be fetched in a compact form with controlled response time.

Why it matters: clearer Telegram journeys, fewer surprises in conversations, more trustworthy supervisor metrics, and less load spikes from integrations.