Widget installation | Stand Feature Reference

01

Install the Site snippet

Representative installation shape

<script defer src="https://cdn.stand.chat/widget/stand.js" data-stand-id="YOUR-SITE-ID"></script>

Copy the generated snippet for the actual Site. Do not reuse this placeholder or another Site’s ID.

Open the Site, expand Installation snippet, and copy the generated script without changing its Site identifier.
Add the generated deferred script once through the website’s shared page template, code, tag manager, or builder custom-code area. The document head is suitable; placing it before the closing </body> tag also works.
Publish the change to the real visitor-facing domain; a saved draft or local preview does not verify production installation.
Visit the published page so the widget performs its Site lookup, then return to Sites and confirm Installed status.

02

Status	Meaning
Pending	Stand has not yet observed a successful matching request from the generated Site snippet.
Installed	A page on the normalized Site domain loaded the snippet and reached the Stand availability path for that Site.
Installed but no chat	The script is present, but Site enablement, routing eligibility, I chat here, Stand-in coverage, behavior rules, or organization capacity prevents a visitor conversation.

03

The data-stand-id selects one Site record and its configuration.
The page domain must normalize to the Site’s saved domain. Preview and staging hostnames need their own matching configuration when they should run Stand.
Protocol, path, and a leading www. are removed for the Site-domain comparison.
Path-specific behavior and Stand-in specialization are evaluated only after the Site and domain match succeeds.

04

Confirm the copied snippet was published in the active template or tag-manager container, not only saved as a draft.
Inspect whether cache or CDN output still serves the previous page.
Confirm the page hostname matches the Site rather than a preview or alternate domain.
Check that the Site is enabled and Chat widget status lists an eligible rep or Stand-in.
Review Chat widget behavior for a delayed, scroll-based, manual, or suppressed reveal before assuming installation failed.

05

The public Site identifier selects configuration but is not a customer secret or rep authentication credential.
The stable snippet does not need to change when owners edit runtime Site behavior.
Removing the snippet stops future page loads from initializing Stand but does not delete the Site record or prior conversations.
Installing the snippet does not give Stand permission to bypass the website’s own authentication or read private backend data.

06

The screen below shows the feature in its normal Stand context. Labels and surrounding controls may vary with account state and plan.

07

Site management — A Site is Stand’s installation and routing boundary for one named website context. It owns the stable embed snippet, normalized domain, enablement, Site instructions, fallback language, behavior rules, coverage diagnostics, and usage scope.
Chat routing and match status — For every new website conversation, Stand builds an eligible set from the matched Site, organization capacity, Available reps, and enabled AI Stand-ins. It routes to an Available rep first; when Stand-in coverage is active, enabled Stand-ins can cover chats when no rep is Available or every eligible rep is at capacity.
Stand JavaScript API — The public window.StandChat API lets a website reveal its own chat entry points, inspect responder availability, open Stand with page-specific context, and identify a signed-in visitor.