Chapter 08
After Stand works on one page, the next question is coverage. Which sites should have chat? Which agents should answer? Which reps should be eligible? How do you keep context specific without creating a support operation?
Stand Guidebook
Chapter 08 of 11
Field guide
Scale Stand by separating domains, audiences, and responsibilities. One account can cover many sites and agents, but each site should still have a clear reason to exist.
Use this chapter when you manage a marketing site, docs site, app pages, client sites, campaigns, or a team where different people should answer different visitor contexts.
Register each meaningful site or audience separately.
Use site prompts for context that changes by domain, product, region, or client.
Scope agents when a generalist stand-in would give weaker answers.
Use live matching to see who would handle a visitor right now.
Site strategy
A site in Stand is a routing and context boundary. It deserves its own setup when visitors need different facts, different reps, different agents, or different measurement.
Do not split every path just because you can. Split when the visitor's job changes enough that the stand-in should behave differently.
Example
Example
Agent specialization
A generalist agent can cover simple questions. A specialist agent is better when the page has its own domain language, pricing rules, product area, or audience.
When a specialist only belongs on part of a site, select the site in the agent Identity tab and add one Path pattern. Leave it empty for the whole site, use / for the front page, use an exact path such as /pricing, or use /pricing/* for that page and child pages.
Specialization should make the visitor experience clearer. If two agents would answer the same way, keep one.
Routing visibility
The Sites page shows Matches right now for each site. This is operationally useful: it tells you whether a visitor would reach a live rep, an enabled stand-in, or nobody useful.
If multiple AI agents match the same site and path, Stand shows the probability split. In the common two-agent case, the next visitor may be routed 50/50 between the matching stand-ins. When a human rep is available, has I chat here checked, and is below their concurrent chat limit, the human match takes priority over AI coverage.
Screenshot reading
Questions
Yes. Stand supports unlimited sites across plans, each with its own embed snippet, prompt, and usage stats.
Yes. Agents can be general, scoped to a specific site, or narrowed to one path pattern inside that site.
It shows the reps and agents that would currently be eligible if a visitor arrived on that site, including the probability split when multiple AI agents match.
Continue the guide