Sharing a conversation
Turn a chat into a link anyone can open — as plain text or as a replay that types itself out. The link freezes what existed when you pressed the button, inherits the agent's sign-in rules, and dies when you delete the conversation.
Some conversations are worth passing on: the answer a colleague keeps asking for, a demo of what the agent actually does, the exchange you want to attach to a support ticket. The share button in the top-right of the chat turns one into a link.
What the link contains
Exactly what existed when you pressed the button. Nothing you say afterwards appears in it. If you keep chatting and want to share the new part too, press the button again — that makes a second link. The first one is untouched, because when you sent it you agreed to publish what was on screen at that moment, not whatever the conversation becomes later.
Attachments you sent — images, PDFs — are included and keep working for as long as the link does.
Two ways it opens
| Replay | The conversation types itself out: the question, a pause where the agent was thinking, the answer appearing word by word, charts drawn as they arrive. Paced for reading, not for speed. |
| Full text | Everything at once, like a document. |
You pick which one it opens with; whoever opens it can switch, pause the replay, or skip to the end.
One honest note about replay: it is an animation, not a recording. The platform stores the messages, not the agent's intermediate steps — so the "thinking" pause is a reconstruction placed where the answer genuinely took a while, not a playback of what was thought.
One part of it is a recording, though. If the agent offers follow-up suggestions, the replay shows those buttons appearing, and when the visitor took one it shows that button being pressed instead of the question being typed. Both the suggestions and which one was clicked are stored at the time — so a shared link shows how the conversation was steered, not only what was said.
Who can open it
Whatever your agent already requires. A public agent gives you a link anyone can open. An agent that requires sign-in gives you a link that requires the same sign-in — which means it only works for people who can log in to your system. That is not a restriction added on top; it is the same rule, applied to the same conversation.
Letting people continue it
Off by default. Turn it on and the page gets a Continue this conversation button: the reader gets their own copy of the thread and can keep asking, with the agent seeing the whole exchange as context.
Two things to weigh before you switch it on. Their questions are answered by your agent and count against your usage. And their continuation is their own — a separate copy, invisible to you, which does not change the conversation you shared.
Taking it back
Every link you have made is listed in the share panel, with how many times it has been opened, and a Revoke next to each. Revoking makes it show nothing from that moment on.
Deleting the conversation revokes every link made from it, automatically. That is deliberate: deleting a conversation should mean it is gone, and a link that still opens would make that untrue.
What revoking cannot do is un-show it to someone who already read it. Which is the one thing worth checking before you press share: conversations often contain names, addresses, order numbers — yours or your customer's.
Related
- Private by design — how conversation content is encrypted, and what changes when you choose to publish one.
- Audit trail — who changed what in your account.