--- title: "Release 5.11.2" description: "In Facebook Messenger from Operator Line, PDFs and documents can be sent as Messenger attachments; fixes across Scenario Builder, statistics, tickets, broadcasts, and Custom Data." --- # Release 5.11.2 When an operator sends a PDF or another document in Facebook Messenger, the customer can receive the file as a normal Messenger attachment — not only as a link in the text. An instance administrator turns the option on. This release also includes a number of fixes across Scenario Builder, statistics, tickets, broadcasts, and Custom Data. ## Scenario Builder **New** - **Safe restore to a previous scenario version.** "Make this version current" now restores the scenario correctly without breaking cross-process transitions. - **"Keep elements from the current version" checkbox.** When restoring, you can keep sections added after the selected version instead of a full rollback. - **Export a historical scenario version** — a version from history can now be downloaded and re-imported, just like the current one. - **Labels and descriptions on scenario branches (edges).** Each branch can get a short label, description, and color — documentation only, it does not affect bot behavior. **Fixed** - Publishing a scenario is no longer blocked with "section locked by another editor" when the lock belongs to the current user. If a colleague genuinely holds the lock, you now see who and which section. **How it changed** - **Before:** restoring a version could break cross-process transitions; a historical version could not be exported on its own; there was no way to label a branch beyond its button text. - **Now:** restore preserves transitions correctly, you can choose full rollback vs. partial merge, versions are exportable, and branches can carry labels. - **Why it matters:** less risk of breaking a scenario during a rollback, and easier maintenance of complex branching scenarios by a team. ## Operator Line **New** - **Native files in Facebook Messenger.** When an administrator has enabled the option, PDFs and documents from Operator Line arrive as Messenger attachments; if there is text with the file, it is sent as a separate message. **Fixed** - **Copilot: inserting an image from a suggestion.** Fixed an error inserting an image from an AI suggestion, and a duplicate-action bug (one action could fire up to 4 times). - **Closed dialogs list.** Closed dialogs show the client's name again instead of a technical channel identifier, and sorting reflects the actual time of the last message rather than the closing time. - **Live dialog canvas.** Removed a stray "closed by timeout" system message that belonged to a different (already closed) dialog from the same session and incorrectly appeared last in an open dialog. - **Disabling automatic dialog assignment.** When automatic assignment is disabled, a dialog now correctly stays in the queue for manual pick-up even when an operator frees up a slot (closes another chat, transfer, resolved ticket). - **WhatsApp: messages sent directly from a device.** Messages a manager sends directly from the WhatsApp app on the channel's number (not through the platform) appear in Operator Line again. - **Temporary ban in Widget.** A temporary client ban in the Widget channel is now lifted automatically once it expires — previously a client could stay blocked indefinitely. - **Table view pagination with a date filter.** When a saved filter includes a date range, switching pages in table view shows different dialogs on each page again (previously every page duplicated page 1). **How it changed** - **Before:** a duplicated Copilot action, "lost" dialogs in the closed list, another dialog's system messages in a live canvas, assignment overriding a disabled setting, missing WhatsApp device messages, permanent temporary bans, and "stuck" pagination. - **Now:** each of these situations is fixed individually; behavior for cases that already worked correctly is unchanged. - **Why it matters:** these bugs directly affected day-to-day operator work — from finding a client in history to trusting a "queued" or "blocked" status. ## Statistics **Fixed** - **Average reaction time tile.** Values under a minute no longer render as "20h 42m" — fractional seconds are now read correctly. - **"Average operator reaction time" tile renamed to "Average operator connection time"** — it always measured time to connect, not response speed; response speed has its own "Average first reaction time" tile. - **Fast Line Pro time-savings figures** on the corresponding statistics tab were previously understated by roughly 10–20x due to the same rounding defect — they now show the correct numbers. - **Rating filter (CSAT/NPS)** on the "Dialogs" tab of native statistics works again — previously it always returned an empty table regardless of the selected rating or period. - **"Working Hours" report.** Removed phantom multi-hour "after call work" periods caused by a lost end-of-shift offline event. **How it changed** - **Before:** fractional durations were misread (only the part after the decimal point was taken), the rating filter never worked, and an operator's offline transition could be lost, inflating the report by hours. - **Now:** durations render correctly, the rating filter actually filters, and the working-hours report reflects the real end of a shift. - **Why it matters:** these figures directly feed SLA evaluation, operator workload analysis, and time tracking — incorrect numbers led to wrong conclusions. ## Tickets **Fixed** - **Reassigning a ticket to another operator via a scenario.** The previous ticket owner is no longer left incorrectly attached to the chat after reassignment — it was still counted against their concurrent-dialog limit. - **CSAT email after closing a Client Portal ticket.** The satisfaction-survey email is now sent after closing a ticket created through the Client Portal — previously it was systematically not sent for this channel. **How it changed** - **Before:** the previous operator stayed attached to the chat after reassignment, counting against their dialog limit; Client Portal tickets never triggered a CSAT email on close. - **Now:** both cases reflect the correct state. - **Why it matters:** accurate operator workload accounting and complete feedback collection after a case is closed. ## Broadcast **Fixed** - **Templates and lists screen.** Fixed clipped content and controls — the page now fills the available height, and the templates/broadcasts table is fully visible without clipping. **How it changed** - **Before:** on some screens it wasn't possible to fully open or edit a broadcast template — content and action buttons were clipped. - **Now:** the Broadcast screen renders fully at any window height. - **Why it matters:** without this fix, some templates and broadcasts were effectively unreachable for editing. ## Custom Data and integrations **Fixed** - **Custom Data CSV export.** Fixed a "No token provided" error when downloading a CSV export — other formats (xlsx, pdf, xml, html) already worked correctly. - **Custom Channel settings.** Saving the channel form no longer erases the bound phone number for number-based channels (Viber/Telegram via e-chat) — previously any form save could break outbound message delivery. **How it changed** - **Before:** Custom Data CSV export returned a token error instead of a file; saving the Custom Channel form could erase the phone number outbound delivery depended on. - **Now:** CSV exports as reliably as other formats; the Custom Channel form only saves what the administrator actually changed, without touching other channel data. - **Why it matters:** both bugs looked like something broke on its own after a routine settings save or export. ## Notes - Native files in Facebook Messenger: default behavior is **unchanged** until an administrator enables the option — the customer still receives a link in the text. Images and video are not affected by this option. How to enable and verify: [How to enable native files in Facebook Messenger](/en/operatorline/how-to/enable-facebook-native-file-attachments.md). ## Related Documentation - [How to enable native files in Facebook Messenger](/en/operatorline/how-to/enable-facebook-native-file-attachments.md) - [Reply to a client](/en/operatorline/how-to/reply-to-client.md) - [Connect Facebook Messenger / Instagram](/en/channels/how-to/connect-facebook-messenger-instagram.md) - [Scenario version history: why and how it works](/en/scenariobuilder/reference/version-history-explained.md) - [View scenario history](/en/scenariobuilder/how-to/view-scenario-history.md) - [Use Copilot](/en/operatorline/how-to/use-copilot.md) - [View the chats table](/en/operatorline/how-to/view-chats-table.md) - [Automatic dialog distribution](/en/operatorline/explanation/auto-distribute-dialogs.md) - [Connect WhatsApp (MayTApi)](/en/channels/how-to/connect-whatsapp-maytapi.md) - [How to read duration and reaction-time metrics on the Appeals tab](/en/statistics/how-to/view-appeals-duration-and-reaction-metrics.md) - [View shift report](/en/statistics/how-to/view-shift-report.md) - [Configure CSAT](/en/statistics/how-to/configure-csat.md) - [Link tickets](/en/operatorline/how-to/link-tickets.md) - [Export model data](/en/customdata/how-to/export-model-data.md)