Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.6.10
  • 5.6.9
  • 5.6.8
  • 5.6.7
  • 5.6.6
  • 5.6.5
  • 5.6.4
  • 5.6.3
  • 5.6.2
  • 5.6.1
  • 5.6.0
  • 5.5.6
  • 5.5.5
  • 5.5.4
  • 5.5.3
  • 5.5.2
  • 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.3.26

Release 5.3.26

What Changed

  • Terminology in Operator Panel. In the Operator Panel, "dialogs" has been replaced with "appeals" — the UI matches business language.
  • Auto-close tickets. When a chat room is closed, the related ticket is now closed automatically — no need to close the ticket separately.
  • Close subject in statistics. The subject selected when closing a chat is now correctly included in reports.

How It Changed

Appeals and tickets

Before: The UI used "dialogs"; the ticket could remain open after the chat was closed.
Now: The Panel uses "appeals"; closing the chat room closes the ticket automatically.
Why it matters: Clear terminology and consistent chat/ticket state.

Close statistics

Before: The subject chosen at close might not be reflected in reports.
Now: The subject from the close window is included in reports.
Why it matters: More accurate analytics on why appeals were closed.

Prev
5.3.27
Next
5.3.25

On this page