Skip to content
Widget & appearance

Understand stacked reply previews and unread badges

See how visitors are notified when staff or the bot replies while the standard messenger is closed.

Where to find itPublic website → closed floating chat button

Before you begin

Select the correct AI agent and open Appearance. Keep the public website available in another tab so you can check the customer experience after saving.

Example workspace · Demo data. The newest saved reply appears above the standard floating button. Select the image to enlarge it.
Closed messenger showing a stacked reply preview and unread badge

Example workspace · Demo data. The newest saved reply appears above the standard floating button. Select the image to enlarge it.

Step by step

  1. 1

    Close the visitor’s chat

    Use a test conversation in a separate visitor browser. Close the floating messenger while keeping the website visible.

  2. 2

    Send a reply

    Reply from Inbox, or let a complete bot response finish. Saved assistant messages are eligible; typing indicators and partial streams are not.

  3. 3

    Inspect the stack and count

    The newest excerpt appears above the button with sender, avatar and time. Up to three visual sheets represent multiple replies; the badge counts unread messages.

  4. 4

    Open or dismiss

    Click the card to open Chat and read the replies. Dismiss only hides the current preview; it leaves messages unread.

  5. 5

    Customise the copy

    Open Appearance → Bot messages → Launcher and reply previews. Edit relative times, unread/dismiss text and fallback names; retain {count} in numeric templates. Use default restores the selected-language text.

Good to know

Visible pages normally check about every 15 seconds. Existing history is quietly baselined on first observation; this is not an announcement of every old message.

This applies to the current conversation and standard floating launcher. Inline/custom launchers and fully closed browser tabs do not show these cards.

Preview labels follow the selected widget language, including an explicit data-locale override. Exact saved copies of standard text follow that language; original custom text needs its own translations.

Check the result

Save the change and reload a page that loads this agent. Check desktop and mobile, including text contrast and the collapsed launcher.

Questions & troubleshooting

The badge survived a reload

That is expected until the conversation is viewed. Read cursors are local to this browser and sync across its tabs.

Was this article helpful?

Rate this guide on this device. Ratings are not sent to Corthex.