Sites and chat behavior
Chat behavior rules
Chat behavior rules are an ordered, runtime configuration for where and how the floating widget appears on one Site. The first enabled rule whose path matches supplies the reveal trigger, greeting treatment, display mode, and any owner-approved experiment.
- Availability
- All plans
- Configured in
- Dashboard → Sites → select a Site → Chat widget behavior
- Category
- Sites and chat behavior
- Reference status
- Current
Rule matching and order
Rules are evaluated from top to bottom against window.location.pathname. Query strings and hashes are ignored. Put exact rules before broad wildcard and default rules.
| Pattern | Scope |
|---|---|
| Empty path | Default fallback when no earlier enabled rule matches. |
/ | The Site root page only. |
Exact path such as /pricing | That page, with trailing-slash equivalence, but not descendant pages. |
Trailing wildcard such as /docs/* | The named path and every descendant beneath it. |
Rule controls
| Control | Behavior |
|---|---|
| Enabled | Keeps a rule saved while including or excluding it from evaluation. |
| Widget show trigger | On load, after a time delay, after a scroll percentage, or no automatic floating reveal. |
| Greeting | Use the default greeting, suppress it, or replace it with custom greeting text. |
| Open on desktop | Opens the full chat window when an eligible greeting would be presented on desktop. |
| Half-sized | Starts the floating invitation in a more compact presentation. |
| Step aside | Allows the floating invitation to move away from page content after appearing. |
| Custom JavaScript | Runs approved experimental code after Stand finds availability and before the normal widget reveal. |
When changes take effect
- Behavior is returned during the widget’s availability lookup, so the installed script itself remains unchanged.
- A newly saved rule affects later visitor page loads and evaluations; it does not retroactively rerun inside an already active conversation.
- Only the selected first matching rule supplies behavior for that evaluation.
- Disabled rules are skipped but retained for later experiments.
Advanced JavaScript and support access
- The Site owner must explicitly enable advanced behavior before a rule exposes custom JavaScript.
- One rule accepts up to 20,000 characters of customer-visible custom JavaScript as a platform guardrail.
- The code runs on the customer website and can affect or break page behavior; use it for controlled experiments, then move durable behavior into the website implementation.
- A separate owner opt-in can temporarily authorize Stand support to configure advanced behavior on the customer’s behalf.
- Disable support access when the agreed assistance is complete.
Limits and non-goals
- Behavior rules do not change which Stand-in is eligible; use specialization for routing coverage.
- A reveal rule cannot create availability when no rep or Stand-in can answer.
- Custom JavaScript is not a secure place for secrets because it executes in the visitor page.
- Rule path matching is not access control and must not be used to protect private content.