What visitors see

View as Markdown

Messenger doesn’t ask visitors to sign in. Anyone can type any email address, so Messenger is careful about what it shows.

A visitor sees

Only the conversations started in this browser. Nothing from other browsers or devices, and nothing they wrote to you by email before.
Your team’s answers: the text and any files. Each answer shows the agent’s first name and initials.
The status of each conversation (Open, Solved, Closed).

A visitor never sees

Internal notes or ticket events.
The text of messages that came in by email — only a line “Replied by email” with the time. This way, if someone typed another person’s email address, they never see that person’s email replies.
Your team’s email addresses.
Other people’s conversations.

What is stored in the visitor’s browser

Messenger keeps two things in the browser’s local storage, both starting with ccm_:

the name and email the visitor used, so they don’t type them again,
a private code for each conversation (up to 20), which lets this browser open those conversations.

Not you? deletes both. Messenger sets no cookies. The support form stores nothing in the browser.

Spam protection

Sending a new message runs a security check by Cloudflare Turnstile, shown as a small box above the Send button. Most visitors pass it without doing anything. Replies inside an existing conversation don’t need it. The number of messages per visitor and per day is limited.