Visitor conversations

Answer the visitor who is already reading your site.

CloudSite chat is a shared inbox for every property you run: visitor accounts, message threads, replies, and a clean close when the question is settled. No ticket maze, no lost context.

Start a conversationSee the inbox
Preview links last 1–72 hoursVisitors need no loginUp to 4 languages per site
AK
Visitors inboxPricing page · English
Reply
Today
Visitor

Can we point our own domain at the site, or do we stay on the default link?

10:24
You · support

Yes. Bind the custom domain and CloudSite writes the CNAME on Cloudflare for you. I can show the change on a preview link first.

10:25

Please do. We publish in two languages, so check the German page too.

10:26
Support is replying…
Write a reply…Send

One inbox, every property.

Conversations arrive with the page and language they came from, so a reply never starts with “which site was this?”.

Open conversationsChat
PR
Visitor · pricing page“Can we point our own domain at the site?”
Open
FR
Visitor · form confirmation“The quote form accepted but I never got a copy.”
Waiting
DE
Visitor · German site“Is the four-language limit per site or per account?”
Closed

Threads that keep history

Each visitor account carries its own conversation across pages and languages, so context does not restart every time the same person asks a question.

Reply, then close

Messages, replies, and an explicit end state. A conversation stays open until someone closes it, so nothing quietly disappears from the queue.

Preview before you promise

Share a preview link that works for 1 to 72 hours without a login. If the fix is a page change, read and rewrite the file, then show it.

The conversation sits next to the site.

Support answers are only as good as the change behind them. CloudSite exposes the site as files: list them, read one, write one, delete one. Each file can be up to 2 MB, so a single HTML page or asset is a concrete object to inspect, not a mystery build.

Teams that automate the inbox call the same operations through 75 MCP tools. A read-only token can inspect files and conversations; a read-write token is required before anything is changed.

  1. Reply in the threadAnswer with the page context in view.
  2. Turn the question into a leadCapture name, email and intent through a form with custom fields.
  3. Fix the page, share a previewPreview links stay valid for 1 to 72 hours, no login needed.
  4. Close, export, move onEnd the conversation and pull the record through exports.

Start with one honest conversation.

Generate a site in a sentence, edit it by chat, then let visitors reach you on it.

Open CloudSite