Release 5.7.1

What Changed

  • Settings: administrators and roles with Login as user can sign in as the selected operator; instance statistics now includes AI Answers (Fast Line Pro) and broadcast recipients.
  • Quality Assurance: filter by chat subject, easier pickers for large lists, operator column in the chats table, correct attachment display in assessment transcripts.
  • Distribution audit and queue: operator load snapshot on connection and rejection, live over-limit banner, updated skip-reason charts, operators over limit widget.
  • Operator Line: wait timer and SLA colors no longer reset on system messages; chat shows the Telegram inline button label instead of an internal ID; internal notes in the widget dialog save correctly after editing.
  • Broadcasts: a campaign does not send via another bot when a contact belongs to a different channel.
  • Statistics: the Blocked users tab separately shows operator bans and cases where a user blocked the bot in Telegram; Fast Line Pro cards load on all instances.
  • Profile, Custom Data, bots: notifications save with one Save click including mandatory channels; Custom Data model creation no longer leaves empty records; bot deletion works even without the polls module.

How It Changed

Before: Verifying an operator’s interface required a separate account. Instance statistics did not combine AI and broadcast metrics. QA had no subject filter; large lists were hard to use.

System events in the dialog list reset the wait timer. Telegram inline buttons sometimes showed a numeric ID. Internal notes in the widget dialog might not save. Broadcasts could attempt delivery via the wrong bot. The blocked-users metric mixed operator bans and Telegram bot blocks.

Now: Authorized users sign in as a selected operator with two-step confirmation. Instance statistics shows AI Answers and unique broadcast recipients for the period. QA filters by subject; distribution audit shows quota and over-limit in real time.

The wait timer counts only client and operator messages. Button labels and notes display and save correctly. Blocked users are split by block type. Profile saves all notification types with one Save click.

Why It Matters

Administrators check operator permissions faster. Analysts get aligned AI and broadcast metrics. The QA team filters assessments by subject more precisely. Supervisors see why a chat was not connected due to limits. Operators keep response-time context without service events resetting the clock.

Product areas in detail

Settings — log in as user

New

  • The user edit form includes Log in as user (for root or a role with Log in as user permission).
  • Two-step confirmation before sign-in; the action is recorded in the action log.
  • You cannot sign in as yourself, an inactive user, or a root user (for users without root access).
  • Return to your own account via sign out and sign in again with your credentials.

Settings — instance statistics

New

  • AI Answers card — count of successful Fast Line Pro responses for the selected period (aligned with Fast Line statistics).
  • Broadcast recipients card — unique contacts who received at least one successfully delivered message (earlier and current broadcast modules).
  • Both metrics update together with the operator activity table after applying the date range.
  • Access is limited to root users.

Quality Assurance

Improved

  • Subject filter on the assessments list and QA dashboard.
  • Shared pickers for large lists of operators and subjects — search and scroll through long lists without slowdown instead of slow dropdowns.
  • The Operator Line chats table can show an operator column.
  • Assessment transcripts correctly show attachment-only messages (without text).

Distribution audit and queue monitoring

Improved

  • On rejection due to dialog or channel limit, the audit shows a quota snapshot (how many dialogs are used out of the maximum, per channel).
  • On successful connection, quota at assignment time is also stored.
  • A banner warns when operators are currently over limit; details are available.
  • On the queue status page — Operators over limit block with a list of chats.
  • Queue health indicator accounts for the case when all operators are at limit but requests remain queued.
  • Skip reason and top operators charts are active; chat ID history lookup is available.

Fixed

  • Email no longer consumes a chat slot when the channel has a separate limit in automatic distribution.
  • The connect over limit setting no longer removes restrictions for automatic distribution — only for manual operator joins.
  • A chat that could not be connected due to limit returns to the queue instead of stalling.

Operator Line — dialog list

Fixed

  • Response wait timer, SLA colors, and last message time count from the last non-system message (transfer, subject change, etc. do not reset the counter).
  • When the loaded list has no client messages, the last client message time from dialog metadata is used.

Improved

  • Header profile menu opens with one click from avatar or initials; improved keyboard and screen reader accessibility.

Operator Line — client messages

Fixed

  • After pressing an inline button in Telegram, the chat shows the button label, not an internal scenario translation ID.
  • Editing internal notes in the widget dialog saves text; success toast appears only after a real save.

Broadcasts

Fixed

  • If a contact in the database is linked to a different bot than the campaign bot, the message is not sent via another channel — a clear delivery error is recorded instead.

Statistics

Fixed

  • Fast Line Pro cards (including dialog count and daily chart) load on all instances.

New

  • On the Blocked users tab:
    • Users blocked by operators — moderation bans (same logic, clearer name).
    • Blocked the bot in Telegram — separate metric when a user blocks the bot in a private chat.

Profile — notifications

Improved

  • All notification types save with one Save click — faster and without partial save on error.
  • Mandatory instance channels apply at sign-in; if an administrator requires sound, it turns on without opening Profile.
  • Mandatory notification types cannot be disabled; in-app notifications and mandatory channels are always applied after save.

Custom Data

Fixed

  • If table creation fails, the model record does not remain in the list without data.
  • In quick create from template, the name you enter is saved, not the template key; creation errors appear in the interface.

Settings — bots

Fixed

  • Bot deletion completes successfully even when the polls module is not deployed on the instance (previously the operation could fail with an error).

Scenario Builder — debugger

Improved

  • During long scenario testing in the debugger, reduced risk of overloading the Constructor interface.

Interface — translations

Fixed

  • On the sign-in page, field labels are restored for en, ru, de, and vn (instead of raw translation keys).

Please note

  • Log in as user requires an explicit role permission or root access; return via sign out.
  • Instance statistics (AI Answers, broadcast recipients) is available only to root users.
  • The Blocked the bot in Telegram metric counts new events after the update; historical blocks before deploy are not added retroactively.
  • Distribution audit changes apply to supervisors with queue monitoring access; operator limit rules are unchanged — only their application is more accurate.
  • The broadcast fix does not add contacts from another bot to the audience — mismatched recipients are rejected at send time.