--- title: "Release 5.18.9" description: "\"Channels\" and \"Receives broadcasts\" columns in the clients list, video in broadcast templates, a daily summary in the supervisor monitor, new registrations in native statistics, the ticket number in the right panel, and fixes for Facebook, email, scenarios, quality assessment and SLA resilience." --- # Release 5.18.9 Release 5.18.9 is built on version 5.18.8 and includes all changes of releases 5.18.7 and 5.18.8. Neither of them was deployed separately, so instances receive their changes together with 5.18.9. They are described in the [release 5.18.7 notes](/en/releases/5.18.7.md) and the [release 5.18.8 notes](/en/releases/5.18.8.md). Below is only what is new in 5.18.9: the clients list gets columns for channels and broadcast subscription, a broadcast template can contain a video, the supervisor monitor shows a daily summary, and native statistics shows new registrations. Several fixes for Facebook, email, scenarios and quality assessment are included as well. One new feature is off by default — see "Please note". ## Please note - **The daily summary in the supervisor monitor is off by default.** The "Today" and "Online today" columns appear on an instance only after they are turned on. Contact your ConnectiveOne manager. Until then, the monitor works as before. - **If you customised the set of columns earlier, the new clients list columns do not appear on their own.** Turn on "Channels" and "Receives broadcasts" with the **"Columns"** button. - **Assessing checklists with many knowledge base criteria may make more requests to the model.** The criteria are split into more groups so that the answer is not cut off, so the number of groups in such an assessment can grow. ## Clients and broadcasts **New** - **"Channels" and "Receives broadcasts" columns in the clients list.** The "Clients" section has two new columns with filters in the header. - **"Channels"** shows the icons of the channels of all the client's contacts. The filter lets you select one or several channels. - **"Receives broadcasts"** shows ✓, ✗ or "—". The filter has the values "Yes", "No" and "All". If channels are also selected, the flag is calculated for those channels only. - The number of clients matching the conditions is shown below the table. To send a broadcast to part of your base only, filter the clients, tick the ones you need and choose **"Actions" → "Send to selected"**. The "Send to all" button works as before and sends to everyone. - **Video in a broadcast template.** A broadcast template can now contain an MP4 video of up to 20 MB. In Telegram, Viber and Facebook the client receives a video that plays, not a picture file. Images work as before (up to 1 MB). - The field in the template form is called **"Image or video"**. If a file does not fit by format or size, the form explains why, and the "Save" button is disabled. - In the templates list and in the broadcast copy in the operator's chat, the video plays right on the page. - If a video could not be delivered, the error is shown separately and the client is not marked as unsubscribed. ## Operator panel **New** - **Ticket (chat) number in the right panel.** In the **"Request fields"** section, the first row shows **"Ticket number"** (**"Chat number"** for a chat). Click the number to copy it to the clipboard. Previously, in the new design the number was visible only in the address bar. - **A daily summary in the "Operators now" table in the Supervisor.** The "Monitor" tab has new columns: **"Today"** (how many dialogs the operator has closed since 00:00) and **"Online today"** (how much time since 00:00 the operator has spent in statuses that accept chats). The values are also shown for operators who have already gone offline but still have chats. The feature is off by default and is turned on for an instance on request. **Fixed** - **An email that an operator starts no longer puts your own mailbox as the client's address.** When an operator created a new email, opening the card could save the address of your own mailbox as the client's contact. - **Before:** the contact held the company mailbox address instead of the client's. - **Now:** the contact gets the client's address. Incoming emails work as before. Contacts saved earlier are not changed by this fix. ## Statistics **New** - **New registrations for a period.** On the **"Users"** tab of native statistics, two tiles appear at the bottom: **"New registrations"** — how many contacts were added to the "Clients" section during the period, and **"New registrations by day"** — the same number by day. The period is set by the usual **"Date"** filter (day, week, month, year), and the "Process (bot)" and "Channel" filters narrow both tiles. All new contacts are counted, including anonymous ones, so the number can be higher than the "Registered" filter in "Clients" shows. The tiles appear right after the update. ## Channels **Fixed** - **Questions from Facebook ad buttons reach the scenario or the operator.** When a client pressed a question button in a Click-to-Messenger ad, in the "Get Started" button or in the persistent menu, the question reached neither the scenario nor the operator. - **Before:** the message was lost. - **Now:** the text of the pressed button arrives as the client's message: in the scenario, or to the operator if the chat is already with them. This also applies to Instagram. A repeated delivery of the same event does not create a duplicate. Scenario buttons work as before. ## Scenario Builder **Fixed** - **A stopped scenario timer no longer fires.** If an instance runs on several server copies, stopping a timer ("Stop timer" and "Stop all timers" blocks) might not affect a timer started on another copy. - **Before:** the timer could fire an hour later and close a chat that had already been handed over to a specialist. - **Now:** after a stop, the timer does not fire, whichever copy handles the messages. Active timers are not interrupted during the update. ## Quality assessment **Fixed** - **Assessing checklists with many knowledge base criteria no longer fails.** The automatic AI assessment could end with the error "The AI agent did not return a result" when one group of criteria had too many knowledge base criteria. - **Before:** the assistant used up its steps and returned an empty answer, and the assessment failed. - **Now:** knowledge base criteria are distributed so that each group has enough steps left to answer. Because of this, there can be more groups, and so more requests to the model (for example, six groups instead of four). ## Reliability **Improved** - **SLA of open tickets is restored automatically after a failure.** If a ticket's SLA did not start because an internal time-tracking service was temporarily unavailable, the system starts it itself after recovery. Deadlines are counted from the original creation time of the ticket, taking calendars and pauses into account. Calculations that are already running or finished are not duplicated. - **Resilience to temporary failures of internal services.** Actions that could not be completed because of a failure (closing, schedule changes, automatic broadcasts and actions) are repeated after recovery. Outdated runs are skipped so that they are not executed with a delay. ## Related documentation - [Release 5.18.7 notes](/en/releases/5.18.7.md) - [Release 5.18.8 notes](/en/releases/5.18.8.md) - [Filter clients by channel and broadcast subscription](/en/broadcastusers/how-to/filter-clients-by-channel-and-broadcast.md) - [Create a broadcast template](/en/broadcast/how-to/create-broadcast-template.md) - [Supervisor monitor: operators now](/en/operatorline/how-to/supervisor-monitor-operators-now.md) - [View statistics dashboards](/en/statistics/how-to/view-dashboards.md) - [Assess a request](/en/quality_assurance/how-to/assess-request.md)