Release 5.5.1

When a customer replies to your email through Gmail, the reply stays in one ticket. After a ticket is created from a scenario, the operator UI no longer blocks for tens of seconds. Ticket SLA deadlines can respect the working calendar when it is configured correctly. In Operator Line, animated Telegram stickers (.tgs) render as playable previews instead of a plain file row.

Email

Fixed

  • Duplicate tickets in Gmail threads. The customer’s reply attaches to the same dialog and ticket — a parallel thread with a second ticket is not created.
  • Operator UI stall after creating a ticket from a scenario. The message body and operator panel no longer wait an unusually long time for an internal transaction to finish.

Improved

  • OAuth email setup on setups with multiple public hosts: authorization initialization aligns the domain so proxy-side failures are less common.
  • Gmail accounts. Channel settings include an extended view of stored accounts and a way to remove empty or invalid rows without manual config editing.

Operator Line

New

  • Animated Telegram stickers (.tgs). Messages that include a .tgs attachment show an animated preview in the thread, not only a download link.

Fixed

  • Close-chat dialog with missing statuses. If statuses are not loaded yet, they are fetched before the form is shown; a loading indicator appears while waiting.
  • Duplicate categories in quick replies. Each category appears once in the list, even when tied to several skill groups or bots.
  • Quick reply insertion. After you pick a quick reply, the input field is fully replaced with its text — no leftover typing or mixed fragments.

Improved

  • Ticket file fields. Values from the backend and scenarios (single file, multiple files, links) display and open correctly in chat and on the ticket card.

  • CSAT rating in the chat list and header. When a rating is stored on the dialog (including nested payload fields), stars appear when you hover a chat row; the active chat header shows the same rating.

Tickets and SLA

Improved

  • SLA deadlines with a calendar. When a working calendar is set for the chat, SLA times are adjusted for weekends and holidays; a broken calendar does not break saving the ticket.

Operator behaviour and sessions

Fixed

  • Auto-offline and status after disconnect. If auto-offline is turned off in settings, status is no longer changed merely because a config row exists; when it is on, the administrator-defined status applies. Logic after sign-out and after the last tab disconnect matches these rules.

Customer dialogs (bot)

Fixed

  • Buttons with input validation enabled. In the “message with buttons” block, pressing a button does not run text validation (phone, email, etc.); validation still applies to free text.
  • /start command. The dialog resets to the main section entry, even if the user was mid-flow or testing from the Constructor widget.

Scenario Builder

New

  • Unique entry-point aliases. Two entry nodes with the same alias in one bot, or an alias that clashes across sections, blocks saving with a conflict list.

Improved

  • Workflow constants sidebar. Numbers, objects, and empty values display correctly and remain searchable by name and value text.

Fixed

  • Exit-point targets in legacy saved layouts. If the target section was stored under an older field name, opening the scenario shows the correct target without manual data fixes.

  • Broadcasts — bot picker in the log. After you switch bots in the modal, the channel list matches the new bot immediately without an extra click.

Settings

Improved

  • Users and Roles tables. Table headers and filters stay visible while you scroll; only the row area moves and paging stays at the bottom of the table panel.

Constructor — general

Improved

  • Feedback form under Help: labels match UI language and theme; the entry sits alongside other help actions.
  • Process Library — the filter sidebar scrolls correctly with long category lists.

Integrations — Google Business Profile

Fixed

  • Replies to Maps reviews. The system resolves the account from the review’s location instead of a single fixed account; if the location is missing, the error message is clear.

Heads up

  • Improved Gmail threading (Email Threading V2) is turned on by an administrator in system settings. Until then, email behaviour is unchanged.

  • Some API integrations that load the operator chat-room list. Requests that used the legacy “load everything linked in one shot” flag are rejected with a clear message; callers must use one of the supported view modes. Validate scripts and external systems before upgrading.