Chapter 01
Stand is most useful when it turns a quiet page into a live thread: a visitor asks what they really need to know, your stand-in keeps the thread moving, and the right person can join before the moment goes cold.
Stand Guidebook
Chapter 01 of 11
Field guide
Do not treat website chat as a passive support box. Treat it as a lightweight conversation system for pages where a good question can become a lead, a product signal, or a better explanation of what you sell.
Use this chapter if you are deciding where Stand belongs on your site, what kind of visitor should start a chat, and how to judge the first week of traffic.
Start on one page where visitor questions already have value.
Install Stand on that page and verify the widget before judging anything else.
Make the greeting specific enough to invite a real question.
Let AI cover the first response when a rep cannot answer live.
Where to start
A chat widget on every page can be useful later. For the first run, choose one page where a visitor question has clear value: pricing, services, docs, integrations, comparison pages, founder-led product pages, or a high-intent landing page.
The page should already create questions. Stand then gives those questions a place to go, instead of forcing the visitor into a form, a calendar link, or a tab they will close before asking.
Example
Example
Setup
The front page can say setup is simple. A guidebook should still show the path. Start in Sites, add the domain for the page you chose, then prove the full loop works before you spend time polishing prompts or adding more pages.
Keep the first install boring. Use the real page, the real domain, and the real publishing path your visitors will use. A local-only test can tell you the snippet loads, but it cannot tell you whether production cache, tag publishing, or domain matching is correct.
App link
Use the Sites page to Add Site, Show install snippet, Copy the snippet, set I chat here, and confirm Installed status.
Example embed snippet
<script defer src="https://cdn.stand.chat/widget/stand.js" data-stand-id="060fcbe8-ac11-49fd-aa53-daec6594665f"></script>Use the snippet generated for your own site. The data-stand-id value is site-specific.
Troubleshooting
The opening
Generic greetings produce generic chats. A good Stand greeting should tell the visitor what kind of help is available and give them permission to ask a specific question.
The best greetings sound like a person standing at the booth, not a helpdesk queue. They are short, specific, and connected to the page.
The first week
A small site may not need many chats to learn something. Fifteen good conversations can tell you which pages create intent, which claims confuse people, and whether visitors are willing to share contact details once helped.
Count the boring metrics, but read the actual threads. The early win is not volume. The early win is finding language and objections your page did not surface before.
Practice
Questions
Not necessarily. Start where visitor questions are already valuable, then expand after you understand which pages create useful conversations.
No. Stand can answer support-like questions, but it is strongest where conversations create sales, product, or expert-learning signal.
Continue the guide