Site management | Stand Feature Reference

01

Add and identify a Site

Open Sites, enter the website domain or URL, give the Site a customer-readable name, and add it to the organization.
Stand normalizes the domain by removing protocol, path, and a leading www. for matching.
Distinct Site names allow more than one Site entry to use the same normalized domain when the organization needs separate contexts or experiments.
The created Site receives its own stable data-stand-id and installation snippet; another Site’s identifier is not interchangeable.

02

Control	Effect
Enabled	Allows the Site to participate in public matching. Disabling removes its normal visitor availability without deleting configuration.
I chat here	Lets the current member personally receive human chats for the Site; each rep controls their own coverage.
Install snippet and status	Shows the Site-specific script and whether Stand has observed it on a matched page.
Site instructions	Adds owner-managed website context between Team and Stand-in instructions.
Chat language	Sets the fallback starting language used only when visitor and page signals are insufficient.
Chat widget behavior	Controls path rules, reveal triggers, greetings, display modes, and approved advanced experiments.
Chat widget status	Shows currently eligible reps or Stand-ins and a Stand-in probability split when applicable.

03

Any active member can add a Site and set their own I chat here coverage.
Organization owners can rename, enable, disable, configure, and remove Sites and edit Site instructions and behavior.
A non-owner can inspect shared Site context and their own coverage but cannot silently change organization-wide behavior.
Removing or disabling a member affects that person’s human and Stand-in eligibility without deleting the Site itself.

04

A disabled Site is excluded from normal visitor matching even if its script remains present on the page.
An unmatched domain cannot borrow responders from a different Site record merely because the script loaded.
Removing a Site is distinct from removing its script from the website and requires confirmation because it eliminates the organization configuration boundary.
Existing completed conversations remain governed by History and retention rather than being rewritten by a later Site rename or removal.

05

Unlimited Sites are included in the current public plan presentation.
Every Site needs its own stable snippet and matching published domain.
Site name distinguishes records for customers; domain normalization determines the website match.
Site configuration does not replace Stand-in specialization, rep I chat here coverage, or organization quota checks.

06

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

07

Widget installation — Widget installation places a Site-specific deferred script on the published website. The snippet loads Stand, identifies the Site through `data-stand-id`, and lets the backend confirm that the expected domain has requested availability.
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.
Usage analytics — Usage analytics measures the path from an eligible page view to a visible Stand invitation, an activation, a started chat, and conversation time.