Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 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.2.3

Release 5.2.3

What Changed

  • Ticket distribution strategy. Continued improvements to ticket distribution strategy settings between operators.
  • Full-text search. Further refinements to full-text search for dialogs and tickets.
  • Next Response Time metric. Adjustments to how the Next Response Time metric is calculated and used.
  • Chat reminders. Additional optimization of the chat reminder workflow.

How It Changed

Ticket distribution

Before: The automatic ticket distribution strategy was available but needed further tuning for complex scenarios.
Now: The distribution logic has been refined to better handle real-life ticket workflows.
Why it matters: Ticket distribution becomes more predictable and better aligned with the team's processes.

Full-text search

Before: Full-text search was already present but some queries could behave suboptimally.
Now: The implementation has been refined to improve result quality and performance.
Why it matters: Operators can find relevant dialogs and tickets faster, even in large datasets.

Next Response Time metric

Before: The new metric required fine-tuning in how it is calculated and displayed.
Now: The metric logic has been adjusted so that it better reflects how operators actually work.
Why it matters: Reporting on response speed is more accurate, which helps monitor and enforce SLAs.

Chat reminders

Before: Even after previous changes, some reminder scenarios could still behave unexpectedly.
Now: The reminder workflow has been revisited and further optimized.
Why it matters: Operators receive timely and relevant reminders without excessive duplicates.

Prev
5.2.5
Next
5.2.2

On this page