What visitors see
A tour of the widget as your customers experience it. Worth reading once so you know what you are supporting.
The launcher
A circular bubble in the bottom corner, tinted with your accent colour. Clicking it opens the chat panel; clicking again closes it.
Opening the chat
The panel opens showing:
- Your logo and chatbot name in the header
- Your welcome message, rendered as Markdown
- Your quick prompts as tappable buttons
- A Leave Details chip, if lead capture is on and they have not already submitted
Header controls
Five buttons across the top, each with a tooltip on hover:
| Control | What it does |
|---|---|
| Restart chat | Clears the conversation and starts fresh |
| Expand | Grows the panel to full screen; click again to shrink |
| Dark mode | Toggles light and dark; the choice is remembered |
| Leave details | Opens the lead form (when lead capture is enabled) |
| Close | Closes the panel back to the launcher bubble |
Tooltips are suppressed on touch devices, where hover does not exist.
Answers as they arrive
Replies stream in word by word rather than appearing all at once, so the visitor sees the answer forming immediately instead of watching a blank space.
Answers are rendered as Markdown: bold for key terms, bullet and numbered lists, links, and code formatting where relevant. This is why the default system prompt asks for structured replies — a well-formatted answer is far easier to scan than a paragraph.
Follow-up suggestions
Every reply is followed by three suggested next questions, generated from the conversation. Visitors can tap one instead of typing.
This keeps conversations going and steers people toward questions your chatbot can answer. It is automatic — there is nothing to configure.
Per-message actions
On each reply, the visitor can:
- Copy the message to their clipboard — the button confirms with Copied
- Thumbs up or thumbs down to rate the answer
Those ratings feed the satisfaction view in your dashboard, which is the fastest way to find specific bad answers rather than guessing at general quality.
Conversation memory
The conversation is remembered in the visitor's browser. Navigating between pages on your site keeps the same thread — the widget does not reset on every page load.
It also survives closing the tab and coming back later, because the session is stored locally rather than for the length of a single visit.
Two consequences worth knowing:
- The same person on their phone and their laptop is two separate conversations
- A visitor in private browsing starts fresh every time
Restart chat clears the thread and begins a new conversation.
Leaving contact details
When lead capture is enabled, the visitor can open a short form from the header button or the chip beside the quick prompts.
They fill in whichever fields you enabled, submit, and return straight to the conversation. The prompt does not come back once they have submitted.
Talking to a human
If the visitor explicitly asks for a person and handoff is enabled, the chatbot acknowledges and the conversation is flagged in your dashboard.
If someone from your team takes over, the visitor sees that a human has joined, replies come from a named agent, and they see a typing indicator while that agent writes. When the takeover ends, the bot picks back up.
Dark mode
The moon icon toggles the widget between light and dark, independently of your site's own theme. The preference is remembered for that visitor.
If you have set custom theme colours, check both modes — a colour that reads well on a light panel can vanish on a dark one.
Isolation from your site
The widget renders inside its own isolated container. Your site's CSS cannot restyle it, and its styles cannot leak into your page.
This is why it looks identical everywhere, and why you never need to write defensive CSS for it.
Mobile
The widget is responsive. On a phone the expanded view fills the screen, buttons are sized for touch, and hover tooltips are suppressed since they cannot be triggered.
Test on a real phone before launch — most chat traffic is mobile.