Release 5.7.0

Your team documents internal workflows in Knowledge Base, launches tours from articles, and—when an administrator allows it—the AI Assistant can check public vendor documentation without leaving Constructor.

Constructor — instance knowledge base

New

  • Knowledge Base module. After an administrator enables it, your team stores internal instructions, specs, and articles in Constructor: version history with restore, role-based access, pinned items on the welcome dashboard, and a Help menu entry.
  • Instance tours. A dedicated Instance tours area: list, search, draft/ready status, archive; YAML editor with validation before save; import and export of .tour.yaml files.
  • Tour in an article. While editing a document — Insert tour; preview shows a Launch tour card next to the instructions.
  • Role-based access. New tours are restricted by default; management uses Manage instance UI tours under Settings → Roles.

Improved

  • Card statuses. Draft, archived, or no-access tours show a clear state instead of a misleading launch button.

AI Assistant

New

  • Web search and URL fetch. When an administrator allows it, the assistant can search the public internet or summarize a single public web page—separate from ConnectiveOne documentation and your instance knowledge base.
  • Step-by-step output. The chat shows Web Search / Fetch URL steps while the request runs; in Plan mode you confirm a research plan first.

Improved

  • Off by default. Both capabilities require an instance toggle and a role permission—new users do not get web access automatically.

Operator Line

Improved

  • Transfer to online operators only. If operator settings have Show only online operator when transferring dialogues enabled, the transfer modal now lists online operators only—the option previously had no effect on the picker.
  • Translate long messages. The Translate action stays available for texts within the instance AI input limit inclusive—instead of blocking too early on a hardcoded threshold.
  • Settings tables in Operator Line. Lists for tags, priorities, skill groups, metrics, calendars, and statuses fill the viewport and scroll—instead of clipping at a fixed ~300 px height.
  • AI Assistant on mobile. On narrow screens the assistant opener moved to the ? Help menu so the top toolbar stays usable.

Fixed

  • Auto-connect after failure. If automatic operator assignment fails, the chat returns to distribution without waiting up to three minutes—fewer stuck dialogs in the queue on multi-node instances.
  • Dialog export. Exporting the chatroom list with filters completes successfully again—it previously failed with an internal error.

Clients module

New

  • Registered contact. The client list has a column and filter for whether at least one contact left a phone, email, or sign-in (vs. an anonymous visitor only).
  • Visitors without a contact. A separate list mode shows channel visitors not yet linked to a client record.

Improved

  • Client list search. Finds records by chat_id, dialog number, and appeal; in visitor mode—by chat_id and bot_id.

Settings

Improved

  • Users. On edit, password fields stay collapsed by default—browser autofill no longer breaks saving the user card.
  • Roles. Draft state for a new or edited role survives accidental drawer close; unsaved changes are visible until you save.

Fixed

  • Role deletion. After you delete a role it disappears from the list and the system—the server path previously could fail to complete removal.

Notification Center

Improved

  • SLA and normative response alerts. You can subscribe to SLA and normative notification types in profile and operator settings—new operators no longer receive them until they opt in.
  • Bell content. SLA and normative alerts show topic, client, ticket title, and metric or time-in-status context.
  • No duplicates. With Notification Center enabled, one event no longer creates two bell entries.

Broadcast

Improved

  • Broadcast v1 log tab. The log tab shows loaded / total (for example, 50/200); Load more disables when every row is already loaded.

Fixed

  • Message from the correct bot. If a customer wrote to two bots, a broadcast sends from the bot that handled the dialog—not from another bot in the same database.

Channels

Improved

  • Typing indicator in Microsoft Teams. When a reply takes several seconds (AI, Fast Line, or a scenario step with typing), the customer in Teams sees the bot typing—like Telegram or the widget.

Fixed

  • PDF and documents in Telegram. PDF and other files arrive as Telegram documents—not as a link that fails with “wrong type of the web page content”.

New

  • Instagram Ads context. When an administrator enables the instance option, ad context from Instagram Ads is merged into the customer’s next message in the scenario (off by default).

Scenario Builder and tickets

Fixed

  • Ticket description from an action block. If tickets_create / tickets_create_v2 pass ticket_description in the node JSON, the description lands on the ticket—no need to store it separately in dialog state.
  • SLA after ticket completion. When a ticket moves to a completion status, SLA timers stop fully—without stray background triggers.
  • Tags in operator_panel actions. Placeholders in tag_ids resolve correctly before tags are applied to the dialog.

Custom Data

Fixed

  • Table creation. If schema sync fails after saving metadata, the Custom Data record rolls back—you no longer keep an empty table shell in the list.

Fast Line

Fixed

  • Transfer to operator. When no operator is available, the scenario gets a clear transfer outcome—without hanging on the wait step.

Integrations — Cases API

New

  • External Cases API. For CRM or Service Desk integrations: filtered case list, details, message history, and operator replies through a dedicated endpoint set with predictable error codes.
  • External ID on ticket create. Create-ticket requests can include external_id—a retry with the same id does not create a duplicate case after a network repeat.
  • HTML in API messages. HTML message types pass through a restricted safe tag set; unsafe content is stripped.

Improved

  • Delivery before persistence. If the channel (messenger, email, etc.) rejects an operator reply, the API returns a clear error—instead of a system “success” without customer delivery.
  • Rate limits. New endpoints have request limits; when exceeded, the response includes an error code and a hint to retry later.

Please note (integrators)

  • Cases API access requires an integration user with the right scope (bot, subjects, permissions). Ticket create without external_id behaves as before—the response format is unchanged.

Please note

  • Knowledge Base and Instance tours appear only after an administrator enables them—see configure instance settings.
  • Web search and URL fetch in the AI Assistant require separate instance and role permissions.
  • Instagram Ads context and updated Users / Roles screens are optional; check with your instance administrator before expecting them in your account.
  • Show only online when transferring works only if that option is already enabled in operator settings.