Sites and chat behavior
Chat reveal triggers and display modes
Reveal and display settings control when Stand’s floating invitation becomes visible and how prominently it appears. A rule can reveal on load, after time or scroll, or only through manual page UI, while greeting memory prevents repeated interruption on ordinary reloads.
- Availability
- All plans
- Configured in
- Dashboard → Sites → select a Site → Chat widget behavior → rule trigger and display settings
- Category
- Sites and chat behavior
- Reference status
- Current
Choose a reveal trigger
| Trigger | Behavior |
|---|---|
| On load | Runs the floating reveal as soon as Stand’s matched availability and rule are ready. |
| Time | Waits the configured number of seconds before revealing. |
| Scroll | Waits until the visitor reaches the configured percentage of the page. |
| None or manual | Does not automatically reveal the floating launcher; page-native UI or StandChat.openChat(...) can open it when availability exists. |
Control the invitation
Stand remembers that the invitation was presented for the visitor’s browser on that website origin so ordinary reloads do not repeat the interruption. Clearing site data or using another browser or device creates a new memory scope.
| Greeting mode | Visitor result |
|---|---|
| Default | Uses the matched rep or Stand-in’s normal configured greeting. |
| No greeting | Suppresses the invitation message while retaining the configured launcher behavior. |
| Custom | Uses the rule’s page-specific greeting as the opening invitation. |
Display modes
- Open chat widget on desktop opens the full conversation window when the selected default or custom greeting would appear.
- Mobile shows the greeting invitation rather than automatically taking over the screen with a full open chat.
- Half-sized starts with a quieter compact presentation and restores full identity emphasis on interaction or open chat.
- Step aside allows the floating widget to move away after it appears so it remains available without continuously covering page content.
- Opening the chat manually overrides the initially hidden floating state for that interaction.
Evaluation sequence
- The installed snippet identifies and matches the Site.
- Stand finds an eligible responder and returns the current runtime behavior.
- The first enabled path rule is selected.
- The configured trigger waits for its on-load, timer, scroll, or manual condition.
- Greeting memory and device presentation determine whether a greeting bubble, full desktop chat, compact launcher, or no automatic surface appears.
Troubleshooting and boundaries
- A delayed or scroll trigger can make a correctly installed widget appear absent during a quick page check.
- Manual mode requires a working page entry point; without one, visitors have no automatic floating invitation.
- Greeting memory can suppress a repeated invitation during testing; use a fresh browser context or clear the Site’s local data when intentionally testing first presentation.
- Display mode does not change routing, plan counting, or the contents of an active conversation.