Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.7.5
  • 5.7.4
  • 5.7.3
  • 5.7.2
  • 5.7.1
  • 5.7.0
  • 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.7.5

Release 5.7.5

What Changed

  • Auto-distribution (Default strategy): assignments from the queue and when auto-connecting a free operator now update rotation the same way as direct assignment on chat create — load is shared more evenly.
  • Ticket auto-assign uses the same rotation rules as chats.
  • Email: during background refresh of the mailbox connection, operators no longer receive mass “Mail token is set” notifications and do not see forced reloads of the bot settings page without their own action.

How It Changed

Before: An operator who took dialogs from the queue could stay “preferred” for the next auto-assignments — as if there were no rotation between operators. Every background mail connection refresh could spam notifications to the whole team and reload the settings page for anyone working there.

Now: After every successful auto-connect to a dialog (from queue, when going online, on create), the system updates rotation. Mailbox bind by an administrator is confirmed only in that session; background mailbox connection refresh no longer disturbs other operators.

Why It Matters

Fairer workload across the team and fewer interruptions when the email channel refreshes its connection automatically.

Related documentation

  • About auto-distribution of dialogs
  • About automatic connection of free operator
  • Monitor queue and distribution audit
  • Configure email domain
Prev
Release Notes
Next
5.7.4

On this page