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.3.18

Release 5.3.18

What Changed

  • System messages in QA and AI. System messages have been added to QA dialogs and are sent to the AI agent for more contextual assessment.
  • Broadcasts and working hours. Working hours are now reflected in broadcast workflows: when working hours change, the system rechecks sessions and updates plans; settings show confirmation and a notice about the change.
  • Broadcast logs and errors. The logs/errors section shows total count; the Errors tab has a "Load more" button for additional entries.
  • Broadcast template deactivation. Broadcast templates can be deactivated instead of being fully removed — they no longer appear as active but remain available.
  • Buttons in keyboard settings. Fixed autofill for buttons; added a field for button link or action in the settings.
  • Facebook Ads context in Operator Panel. For messages from Facebook Ads, the operator sees ad campaign context.

How It Changed

QA, broadcasts, and working hours

Before: AI in QA might not get full context; changing working hours might not update broadcasts; broadcast error logs could be cumbersome.
Now: System messages in QA are sent to AI; broadcasts react to working hours changes; logs and errors show totals and "Load more".
Why it matters: Better quality assessment, predictable broadcasts, and easier error analysis.

Facebook Ads and buttons

Before: The operator did not see Facebook Ads campaign context; button values could be filled incorrectly.
Now: Ad context is shown in the Operator Panel; buttons have a correct link/action field.
Why it matters: The operator understands the source of the conversation and can personalize replies; buttons work correctly.

Prev
5.3.19
Next
5.3.17

On this page