How to share an AI conversation link from Whizi

The short answer

Sharing creates a public link to one conversation. Anyone with the link can read it in a browser without a Whizi account, and they cannot continue it, edit it, or see anything else in your workspace.

Sharing costs no credits and is available on every plan. You can revoke a link at any time, which immediately breaks it for everyone who has it.

What the recipient sees

A shared link shows the conversation title, the prompts and the answers. The public view is stripped before it is served: user ids, email addresses and internal fields are removed, so the page carries the transcript and nothing about the account behind it. A shared transcript is also screened for safety before it goes public.

What a recipient does not get: the ability to send messages into your conversation, access to any other chat, anything about your account, your plan, or your usage. The link is scoped to one conversation and is read-only.

What the link carries	Visible to a recipient
The conversation title, the prompts and the answers	Yes
Text extracted from an uploaded file, where the thread contains it	Yes, it reads like any other message
The ability to send, edit or continue the thread	No
Any other conversation in your workspace	No
Your account, your plan or your usage	No
Your name, email or account identifiers	No, the public view is stripped of them

Recipients need no account and no app. The link opens in a browser like an ordinary web page, which is the point: sharing an AI conversation with someone who does not use AI tools is one of the more common reasons to do it.

What sharing is actually good for

Three uses that come up repeatedly.

Showing your working. When an AI answer informed a decision, sending the conversation is more honest and more useful than pasting the conclusion. The reader can see what was asked and where the reasoning was thin.

Getting a second opinion on a prompt. If a model keeps producing something unhelpful, sharing the thread lets someone else see what you actually asked, which is usually where the problem is. Sharing gives the recipient a read-only view rather than a copy they can continue, and why there is no copy is covered in can you fork a conversation.

Comparing models in public. A conversation where the same question went to Claude and then to GPT, with both answers sitting in one thread, is a far stronger argument than describing the difference. This is the shape that tends to travel.

Revoking and what to check first

Revoke from the same dialog you used to share. Once revoked, the link stops working for everyone, including people who already opened it. There is no partial revocation and no per-person access, because the link is the credential. Revoking deletes the link record outright, so a revoked link and a link that never existed both land on the same not-found page and are indistinguishable.

That is worth stating plainly, because it decides how a link behaves once it leaves your hands. Access travels with the URL: anyone it is forwarded to reads the conversation on the same terms as the person you sent it to, without an account and without being named anywhere. The URL itself is unguessable (the token is 24 random bytes rendered as a 32-character string, 192 bits of entropy), so the only way someone reaches the page is being given the link. And the only control you keep after sending is revoking, which is all or nothing.

Two things worth checking before you create a link. First, whether the conversation contains anything from an uploaded file that should not leave your organisation, since extracted document text appears in the thread like any other message. Second, whether any earlier turn in the conversation went somewhere you have forgotten about, which is common in long threads that changed subject.

If in doubt, start a fresh conversation with just the exchange you want to show and share that instead. It takes a minute and removes the question entirely.