Release 5.4.2

What changed

  • Operator Line — email: switch between this thread only and all client email messages (one merged timeline); toggles in the chat header and in the history panel; a default for the team can be set in operator settings.
  • Email channel: more predictable multi-recipient replies, fewer surprises with copies and the channel mailbox showing up where it should not; behaviour is better aligned between the chat view and channel setup in the constructor.
  • Mail via Google: more reliable handling of the reply address in email threads — fewer lost or mismatched replies.
  • Email in the chat stream: improved layout width and cleaner formatted text for email messages.
  • Scenario Builder: long multi-line node descriptions with expand / collapse (“show more” / “less”).
  • Chat transfer: transfer dialog with a clearer title and drag-and-drop to move it on screen.
  • Telegram — group chats: clearer view of who sent each message (including profile photo); replies and previews better match group context.
  • UI translations: more consistent wording and keys across the constructor and operator-facing screens in supported languages.

How it changed

Previously, email in the chat was mostly scoped to the current dialog, “reply all” and copy behaviour could surprise operators, wide emails were harder to read, long node descriptions took a lot of space without collapsing, the transfer dialog was less convenient, and in Telegram groups it was easier to confuse the sender or reply target.

Now you can choose an email view mode, better control who receives replies, rely on more stable reply handling in Google mail threads, read HTML emails more comfortably, scan long scenario texts faster, transfer chats through a clearer dialog, and see who is speaking in a group more accurately.

Why it matters: fewer manual fixes to addresses and copies, a clearer email history with the client, fewer reply mistakes, and smoother day-to-day work for operators and admins.

Integrations and scenarios: if you use custom scenarios or external integrations that drive automatic operator connection by skill group, verify their behaviour after upgrading together with your integration owner or support — internal selection logic and lock release when no operators are available have changed.