Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.5.1
  • 5.5.0
  • 5.4.4
  • 5.4.3
  • 5.4.2
  • 5.4.1
  • 5.4.0
  • 5.3.42
  • 5.3.41
  • 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
  • 5.1.1
  1. Docs
  2. /Release Notes
  3. /Release 5.5.1

Release 5.5.1

When a customer replies to your email through Gmail, the reply now lands in the same ticket — no duplicates. The operator UI no longer freezes after a ticket is created. Scenarios block saving two entry points with the same alias.

Email

Fixed

  • Duplicate tickets in Gmail conversations. When a customer replies to your message, the reply attaches to the same dialog and ticket — no separate "side" thread with its own ticket.
  • ~50-second UI freeze after a ticket is created inside a scenario. The email body and operator panel no longer hang while a ticket is created within a transaction.

Operator Line

Fixed

  • Empty close-chat dialog. When you open the close-chat dialog, statuses now load (previously the form could appear empty), and a spinner is shown while data is loading.

Scenario Builder

New

  • Unique entry-point alias validation. If two entry points in the same scenario share an alias, the builder shows a dialog listing the conflicts and blocks saving. The same check applies when an alias collides with one in another section of the bot.

Integrations — Google Business Profile

Fixed

  • Replies to Google Maps reviews used the wrong account. Previously, a single hardcoded account was used for replies — now the correct account is resolved dynamically from the review's location_id. If the location cannot be found, the system returns a clear error with the review and location identifiers.

Heads up

  • The Gmail conversation improvement (Email Threading V2) is enabled by an administrator in instance settings. Until enabled, email behaviour is unchanged.

Related documentation

  • How to configure the instance (email provider)
  • How to edit a scenario
Prev
Release Notes
Next
5.5.0

On this page