Release 5.13.1

5.13.1 is a fix-focused release for everyday operator work and reporting accuracy: personal panel settings survive a reload, sorting no longer resets an applied filter, chat content stays inside the operator's skill groups, and two long-standing statistics distortions (inflated dialog duration, missing widget source data) are corrected. Scenario Builder gets the missing Connect to Operator parameters in the form, and the widget configuration page builds a working embed link again.

Highlights

Profile settings stay saved — the default right-panel section and pinning survive a reload, and the instance-level defaults apply again.
Sorting keeps the applied filter in the Operator Line table view — a saved filter is no longer replaced by the full dialog list.
Chat messages follow skill-group access — a direct link to a restricted chat no longer opens its correspondence.
More accurate dialog duration in statistics — long-closed chats no longer keep accumulating time.
Complete widget source data — domain and platform are recorded for returning visitors too, so domain-filtered reports count every chat.
Connect to Operator node — timeouts, the waiting message, and queue weight are now available in the node form.
Variable to Store keeps values with a colon in Scenario Builder node settings.
Widget configuration page builds a working preview and embed snippet on every instance.

Operator Line

Sorting keeps the applied filter in table view

Before: in table view, changing the sort mode through the sorting menu dropped every condition of the applied filter — a saved filter showing a few dozen requests turned into the full list of all dialogs. The filter panel still displayed the old selections, and paging further kept the broken result.

Now: the applied filter conditions (topics, request type, and the rest) survive a change of sort mode; only the order changes. Paging after sorting keeps the filter as well.

Why it matters: you can reorder a filtered work list without losing the selection you built and without re-applying the filter every time.

More: View the chats table, Create a filter

Chat correspondence limited to the operator's skill groups

Before: on instances where topic visibility follows skill groups, opening a restricted chat was refused — but a direct link to that chat could still load its message history. Restricted topics were therefore readable by users outside the corresponding skill group.

Now: message history follows exactly the same access rules as opening the chat. A user outside the skill group gets the same "not found" response as for a chat that does not exist. Access for the request assignee, for operators who took part in the dialog, and for the operator's own outbound chats is unchanged.

Why it matters: sensitive support lines stay closed to users who were never given access to them, regardless of how the chat is reached.

More: Configure skill groups

Right panel and profile settings

Before: in Profile → Settings, choosing a default right-panel section and saving it left the field blank after a reload — the setting looked lost. The "Default" option could never be highlighted, and the instance-level right-panel settings (default section, panel expanded on open) had no effect at all. In instance settings, the default section could show a value that was not actually saved.

Now: the profile page shows the values that are actually stored, "Default" is selectable and highlights correctly, and an operator who leaves "Default" inherits the instance-level choice. The right panel opens in the configured state and stays in sync between the panel and the arrow in the chat header. In instance settings, an empty default section is shown as empty.

Why it matters: personal workspace preferences stop resetting, and the defaults an administrator configures for the team finally take effect.

More: Configure operator settings in profile, Configure chats

Statistics

Accurate dialog duration

Before: a chat that had already been closed could still receive follow-up activity — messages, transfers, a repeat close, or an automatic connection — from an outdated session. The dialog reopened in the lifecycle, so its recorded duration kept growing for weeks or months and inflated the dialog time in reports.

Now: actions coming from an outdated session are ignored for chats that are already closed, so a closed dialog stays closed and its duration stops at the real close time.

Why it matters: average and total handling time in reports reflect actual work instead of being skewed by a handful of dialogs that never stopped counting.

More: View a dashboard

Before: the widget collected visitor metadata (source domain, platform, IP) only when a conversation started from scratch. A visitor who returned to a saved conversation never triggered the collection, so chats created in that session were recorded without a source domain — and reports filtered by domain silently undercounted them.

Now: the metadata is collected once per session, both for a new dialog and when a visitor returns to a saved conversation. If the IP lookup is slow or blocked, the chat is sent without delay and the domain and platform are still recorded. Manually passed values and the recognize_user_meta option keep working exactly as before.

Why it matters: widget reports filtered by domain finally include every chat, so per-site and per-brand numbers can be compared with confidence.

More: Pass parameters from the widget

Scenario Builder

Connect to Operator node — timeouts, waiting message, and queue weight

Before: the Connect to Operator node supported a number of parameters that were not offered in the node form — including the dialog inactivity timeout and the operator waiting timeout. They could only be set manually in the node's code view, so the documented setup steps could not be followed from the interface.

Now: the form includes the two timeouts (in the Timeouts and transitions group), a new Waiting message to the client group, and the queue weight in the routing group. The reference documentation now states the correct units and the prerequisites: both timeouts are set in minutes, the operator waiting timeout must stay below the inactivity timeout, and both require the corresponding Operator Panel settings to be enabled on the instance.

Why it matters: queue and timeout behavior can be configured directly in the node, without editing the node in code view and without guessing the units.

More: Connect to Operator (with message) reference

Variable to Store keeps values with a colon

Before: in the Wait for Input and Message with keyboard node settings, a Variable to Store value containing a colon (for example registration:first_name) was silently cleared whenever any field in the node was edited — including while typing the value itself.

Now: such values are preserved. While Save to Custom Data is on, the field is filled automatically from the selected model and column, is shown immediately, and is locked from manual editing; turning the option off clears only the automatically composed value and never a name you typed yourself. A hint explains that a colon in the name is a valid storage prefix, not an error.

Why it matters: the storage prefixes used to write answers to the client card, files, or Custom Data can be entered once and stay in place.

More: Wait for Input node parameters

Channels

Before: the widget configuration page could build the widget address from a value that was not filled in on a particular instance. The result was a broken script link — both in the live preview on that page and in the embed snippet copied to the website.

Now: the address is determined at the moment the page is opened, from the instance you are working in, so the preview loads and the copied snippet is correct everywhere. The link to the previous version of the widget was removed from bot settings, since that version is no longer supported.

Why it matters: the code you hand over for embedding works the first time, without having to check the address by hand.

More: Set up the widget on a website, Configure widget settings

Please note

In widget reports filtered by source domain, the number of chats will increase after the update — previously part of the chats was recorded without a domain and fell out of such reports. The new figures are the correct ones; historical records are not recalculated.
If an administrator had configured the right panel to open expanded, or set a default right-panel section, those settings now actually apply — operators who never changed the option in their profile will see the panel open in that state.
The new Connect to Operator fields appear after the update is applied on the instance. Existing scenarios keep their saved values; nothing needs to be re-configured.
The widget is delivered as a separate service, so the widget statistics fix reaches visitors on their next page load, independently of this release.