Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.3.40
  • 5.3.39
  • 5.3.38
  • 5.3.37
  • 5.3.36
  • 5.3.35
  • 5.3.34
  • 5.3.33
  • 5.3.32
  • 5.3.31
  • 5.3.30
  • 5.3.29
  • 5.3.28
  • 5.3.27
  • 5.3.26
  • 5.3.25
  • 5.3.24
  • 5.3.23
  • 5.3.22
  • 5.3.21
  • 5.3.20
  • 5.3.19
  • 5.3.18
  • 5.3.17
  • 5.3.16
  • 5.3.15
  • 5.3.14
  • 5.3.13
  • 5.3.12
  • 5.3.9
  • 5.3.6
  • 5.3.5
  • 5.3.3
  • 5.3.2
  • 5.3.1
  • 5.3.0
  • 5.2.14
  • 5.2.13
  • 5.2.12
  • 5.2.11
  • 5.2.10
  • 5.2.9
  • 5.2.5
  • 5.2.3
  • 5.2.2
  • 5.2.1
  1. Docs
  2. /Release Notes
  3. /Release 5.4.0

Release 5.4.0

What changed

  • Saved filters in Operator Line: customer rating (CSAT) conditions save and apply reliably together with other conversation search criteria.
  • Instagram (Meta): broader scenario automation in the channel — easier responses and actions after events in Meta.
  • Merged tickets: clearer limits and hints when a ticket was merged into another — less confusion about connecting and participants.
  • Ticket status in Operator Line: you can pick the ticket status in the conversation context and open new rooms linked to the ticket more reliably.
  • Mailgun email: after soft-deleting an email account you can connect again without the old state blocking you.
  • Constructor UI theme: switch between light and dark theme in the constructor and related screens.

How it changed

Previously, CSAT in saved filters could behave inconsistently, Instagram scenarios did not cover every case, merged tickets sometimes looked like normal tickets for connection, ticket status was less convenient from the line, reconnecting Mailgun after deletion could get stuck, and only the light look was effectively standard.

Now, filters with ratings are more stable, Meta automation is more flexible, merged ticket UX is clearer, ticket status in Operator Line is easier to manage, Mailgun can be brought back after soft delete, and the constructor UI can match comfort preferences.

Why it matters: faster searches by service quality, fewer manual workarounds for Instagram support, fewer mistakes with merged tickets, smoother email operations, and more comfortable long sessions.

Related documentation

  • What filters are
  • How to create a filter
  • How to configure an Instagram scenario
  • How to link tickets
  • How to change request status
  • How to configure the instance (email provider)

On this page