AI Stand-ins
Stand-in specialization
Stand-in specialization limits a Stand-in to one installed Site and, optionally, one path scope within that Site. Routing prefers the most specific eligible match so a purpose-built Stand-in can answer a pricing or documentation area before a general Stand-in.
- Availability
- All plans
- Configured in
- Dashboard → AI Stand-ins → select a Stand-in → Identity → Specialization
- Category
- AI Stand-ins
- Reference status
- Current
Choose the coverage scope
| Configuration | Pages the Stand-in can cover |
|---|---|
| No specialized Site | A general Stand-in can cover otherwise eligible Sites associated with its owner. |
| Site with no path | Every matched path on that specific Site. |
/ | Only the Site’s root page. |
Exact path such as /pricing | That path, treating a trailing slash as equivalent, but not its child pages. |
Trailing wildcard such as /docs/* | The named path and its descendant paths, such as /docs/install. |
Configure specialization
- Open the Stand-in’s Identity tab and select the Site it should specialize in.
- Leave the path empty for Site-wide coverage or enter a supported root, exact, or trailing-wildcard pattern.
- Save the Stand-in. Routing uses saved specialization; an unsaved editor choice has no public effect.
- Enable the Stand-in only after its identity, instructions, skills, knowledge, and coverage are ready for visitors.
How specialization affects routing
Stand first removes Stand-ins that are disabled, belong to the wrong organization, have an unavailable owner relationship, or do not match the installed Site. It then compares the saved coverage of the remaining Stand-ins.
- A matching path-specialized Stand-in is preferred over a Stand-in covering the whole Site.
- A Site-specialized Stand-in is preferred on its Site over a general Stand-in.
- When several Stand-ins remain equally eligible at the same specificity, routing can split probability among them; the Sites page’s Chat widget status shows the current eligible set and split.
- If no enabled Stand-in matches, Stand can still route to an eligible human rep. The absence of an AI match does not create broader Stand-in coverage.
Path-matching rules
- Matching uses the URL path. Query strings and hash fragments do not create a different specialization scope.
- An exact path does not include descendants; use a trailing
/*when a subtree should be covered. - A root-only
/pattern is different from leaving the path empty for the whole Site. - The Site itself still performs domain matching. A matching path on the wrong Site is not eligible.
Availability and boundaries
- Stand-in specialization is available on every plan.
- The selected Site must belong to the same organization and be available in the Stand-in editor.
- Public routing additionally requires the Site to be enabled, installed, and matched and the Stand-in to be enabled.
- Specialization does not change behavior-rule greetings or reveal triggers; those are Site-level chat behavior.
- Changing specialization affects future routing and does not move an active conversation to another Stand-in.