Chapter 01
A Stand-in is an AI assistant that answers on behalf of a member of your team, called a rep. Start with one page where visitors need help, give the Stand-in a clear brief, and test both an AI answer and a human reply before inviting real traffic.
Stand Guidebook
Chapter 01 of 12
Field guide
Launch one focused conversation experiment, from choosing the page and installing Stand to writing the invitation and reviewing what visitors ask.
Need an exact capability definition, plan requirement, or limitation? Browse the Feature Reference.
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
Start in Sites, add the domain for the page you chose, and copy its generated snippet. You need permission to publish website changes, or help from someone who can. If you have not created a Stand account, complete the Quickstart first.
For a one-page pilot, use that page’s template or custom-code setting. A shared template loads Stand on every page that uses it; inspect those pages too before publishing. Expand the installation after the first conversation works.
Test the published page on the domain visitors will use. A preview can confirm that the script loads, but it may have a different domain, cache, or publishing configuration. Installed means Stand has received a valid request from a page matching the Site. It does not mean a human or Stand-in is currently available.
App link
Use the Sites page to Add Site, Installation 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="YOUR-SITE-ID"></script>Use the snippet generated for your own site. The data-stand-id value is site-specific. Without it, or with data-stand-id="demo", Stand Chat’s demo Stand-in answers instead of your team.
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.
Keep the greeting short, specific, and connected to the page. In Stand-ins, create a Stand-in or open one and choose Edit. Set its visitor-facing greeting and role in Identity, then Save. Page-specific greeting overrides belong in Sites → Chat widget behavior.
Enable the Stand-in and turn on its owner’s Stand-in coverage. Check the site and any path specialization. To test AI coverage, turn off your own Available to chat and make sure another available rep is not taking priority. Start a fresh chat from the published page, ask a question covered by the brief, and confirm the AI identity and answer.
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.
Compare chat counts with the actual threads. Look for repeated questions, useful answers, and confusion your page did not resolve; high activity alone does not show that the experiment helped visitors.
Practice
Questions
Not necessarily. Start where visitor questions are already valuable, then expand after you understand which pages create useful conversations.
Stand supports both human and AI website conversations. This Guide emphasizes helping visitors evaluate a product or service and learning from their questions; choose a setup that matches the work your team can handle.
Continue the guide