Release
Article MarkdownReport an error

Release 6.5.0

Release 6.5.0 helps operators find their way around the queue: the chat list shows whose turn it is to reply, and the browser tab shows how many customers are waiting. It also brings export of full dialog texts, new events for scenarios, a clear page instead of an empty screen for unavailable sections, and fixes that reduce delays and errors under load. The release includes the changes prepared for 6.4.1, which was not shipped on its own.

Operator panel

New

  • Whose turn it is to reply. The second line of a chat in the list shows a pill: "New", "Client waiting" or "Awaiting client". You can see the state without opening the chat. There is no pill for closed chats, tickets and chats without a connected operator. The switch "Show whose turn it is in the chat row" is on the operators settings page; it can be enabled on request.
  • Browser tab counter. The tab title shows how many of your chats are waiting for a reply because the client wrote last, for example "(3) Dialogs", and the tab icon gets a red badge with the number. In an inactive tab the title blinks "New messages" when the number grows. An operator can turn the counter off in "Profile → Notifications → Channels". It is on by default for everyone.
  • "Section unavailable" page. If a user opens a section from a link or a bookmark and has no access, they see the reason (no permission, the section is for the superadministrator only, the module is not connected, or there is no such address) and a "Go to home" button, instead of a silent redirect to the home screen. Likewise a user who is not a superadministrator and opens "Instance settings" sees an explanation instead of an empty page. If you need the old behaviour, it can be restored on request.

Fixed

  • Creating a chat and adding an operator no longer fail with an error. Under high load a chat could be created with a delay of several seconds, and sometimes was not created at all. The "New chat" notification and the reminder to the operator to reply arrive as before. If the system is extremely busy at that moment, a short delay is still possible.
  • Rare conflicts during simultaneous work. When several operators change the same data at the same time, an operation that can be repeated is repeated correctly, and the rest ends with a clear error sooner than before.

Widget

New

  • Read receipt for the operator's reply. Under the operator's reply in a widget dialog you see a status: "Sent" (one grey tick), "Delivered" (two grey ticks: the widget received the message but the window is minimised or the tab is in the background), "Read" (two ticks in the message colour: the window is open on an active tab; a tooltip shows the time). Updates are live. "Read" means "shown on an open screen", not "the person has read it". An old widget build that does not send such events keeps only "replied, so read". The feature can be enabled on request.
  • Statuses in WhatsApp and Instagram. "Sent" and "Delivered" are now grey, and the time under a message no longer disappears after the status changes.

Scenarios

New

  • "Chat created" and "Operator joined the chat" events. The "Choose event" window of the "Internal events" start step has two new cards. They let you, for example, create a request in your CRM when a chat appears or an operator joins it. The reason for joining (manually, automatically, transfer, direct, takeover, reconnect) can be used in the scenario. The event scenario runs in a separate service chat and writes nothing to the customer. The feature can be enabled on request.
  • "E-chat (Telegram): message delivered" event. Mark a bot message in e-chat with a tag (for example, a lead number), and when e-chat reports that the message was delivered, the matching scenario branch starts. There is also the event "E-chat: message delivery error". Without a tag nothing changes.

Changed

  • All entry points to a scenario open the new editor. The "Scenario" card on the dashboard, the broadcast and Action Jail onboardings, the bot name in settings and the scenario button in the bot card lead to the new editor. It is the same scenario of the same bot. Old scenario addresses also redirect to the new editor. If your instance still needs the old editor, it stays available in the "Scenario (legacy)" menu item.

Statistics

New

  • FastLine tokens. The "Fastline" tab has a new tile "FastLine: tokens used" and a table "FastLine: tokens by model and action" with CSV and XLSX export. It shows the sum of tokens for the period, with filters "Date" and "Process (bot)". The indicator is off by default and can be enabled on request.
  • Export of dialog texts. The "Export table" window of the "Dialogs" card (Statistics → Main statistics) has a new choice "What to export": "Table" or "Dialog texts". For texts you can choose Markdown (.md) or JSONL and the checkboxes "Mask phones and emails" (on) and "System messages" (off). The file is prepared in the background: when it is ready, a notification with a "Download" button appears. Only the person who started it sees the file, and it is kept for 30 minutes. One file holds up to 20,000 dialogs, 300,000 messages and 200 MB; for a period that is too large, split it into parts. The role permission "Export of dialog texts" (Settings → Roles → Statistics) is off by default: an administrator must enable it manually. The files are handy for training knowledge bases and reviewing dialogs.

Fixed

  • The "Statistics → Statuses" report with a selected operator. The report opens faster and no longer prevents other operators from sending messages, even when it is opened for several weeks and refreshed often. The operator list in the filter still shows everyone. The report without an operator filter for a long period remains heavy.

Fast Line Pro

Changed

  • Faster opening of the agent editor. The agent editor, audit, QA checks and the marketplace scanner open the agent faster. The model field and the knowledge bases block show a loading indicator while the list loads, and the "Parameters" button becomes active as soon as the model parameters arrive. If the agent fails to load, an error message with "Back" and "Retry" buttons is shown.

Fixed

  • A new knowledge base from a file is indexed. On some instances a new knowledge base from a file could fail to index because a wrong model was chosen for indexing. Now the model is chosen correctly, and existing knowledge bases stay on their model. If you configured the indexing model explicitly, nothing changes.
  • Delay of FastLine auto-close. A large number of ordinary open chats or comments no longer delays the FastLine inactivity timer check. For this, a service index is added to the instance database, so it is better to carry out the update at a quiet time.

AI Assistant

New

  • Moving a channel contact to another customer card. If a card holds someone else's contact (for example, Viber), the customer's administrator can ask the AI Assistant in "Agent" mode: "Move the Viber contact from card A to card B" (or to a new one). The agent shows a confirmation card: how many contacts, dialogs (of them open) and messages will move and how many contacts remain on the source card. The move happens after "Only this time" is confirmed. A mistake is fixed by the same request in the opposite direction if the target was an existing card; a move to a new card can be reversed only by support. Limits: the last contact of a card cannot be moved (that is a merge of cards, done by support), only cards with a bot and within one bot, up to 5 contacts at a time and up to 20 moves per hour per user. The feature can be enabled on request and requires an administrator to tick "Allow the agent to move channel contacts between customer cards" for the role.

Security

Changed

  • Acting as another user through an MCP key only with an explicit permission. Previously an MCP key with the superadministrator role could get access on behalf of another user without a separate permission. Now the key's role must have the "Log in as user" permission. What you need to do: if your integrations use MCP keys with the superadministrator role to act as other users, enable this permission in the key's role or issue the key on a separate role. Without it such requests will be refused after the update. For a person in the panel nothing changes.

Marketplace

Fixed

  • Installing a scenario from a package. A topic that a scenario refers to is now found by its technical name and not only by its display name, so such a topic is no longer shown as a missing dependency. A required dependency whose target has already been deleted is installed with a warning, and the plan preview shows this correctly.

Documentation

Fixed

  • The assistant in the documentation portal. It no longer refuses valid product questions phrased in ordinary words (for example, about statistics, tickets, macros, tags), including when the question language differs from the page language.
Using your own AI agent?Install the open skill so your AI agent can work with current official ConnectiveOne documentation.Get the skillNeed support?Couldn’t find the answer or need help from the ConnectiveOne team? Create a request in Client Portal.Create a request