Scale across sites and teams.

A site in Stand is a routing and context boundary with its own site ID and snippet. The domain is required; a second site on the same domain also needs a distinct name. Choose a separate site record when you need separate configuration or reporting, then install that record’s snippet on the intended pages.

For different behavior under one site, start with path rules or Stand-in path specialization. A separate site record is not needed just to use a different greeting on /pricing.

The organization owner opens Team → Invite a rep and sends an invitation to each colleague. After accepting, each member completes Profile, selects the sites they serve with I chat here, and turns on Available to chat while keeping the dashboard connected. Coordinate a test so another eligible teammate does not unexpectedly receive it.

Decide who owns each Stand-in and its follow-up inbox. The owner manages invitations, member access, team instructions, privacy and retention, and billing; ordinary membership does not grant these controls. Agree who reviews Team history and who follows up on requests so a larger roster does not create unowned conversations.

A generalist Stand-in can cover simple questions across eligible Sites in the organization. Its owner’s I chat here choices restrict human coverage, not the general Stand-in. Use Site and path specialization when the AI should answer only within a narrower context.

When a specialist only belongs on part of a site, open the Stand-in → Edit → Identity, select the site, and add one Path pattern. Leave it empty for the whole site, use / for the front page, use an exact path such as /pricing, or use /pricing/* for that page and child pages.

Priority is decided within each owner’s Stand-ins: a matching path specialist takes precedence over that owner’s Site-wide or general Stand-ins. It does not exclude another owner’s general Stand-in. Two matching path patterns have the same priority even if one is longer or exact. Coordinate owners and avoid overlapping specialists when a page needs one predictable answer.

The Sites page shows Chat widget status for each site. Use it to inspect coverage, then test the actual page path from a visitor browser. The panel’s probabilities are a Site-level snapshot without that page path; they do not show the exact distribution for /docs/install or /pricing. Availability, capacity, path matching, and remaining chat allowance can all affect a later visitor.

An Available human with I chat here checked, a connected dashboard, and room below their concurrent limit takes priority. When AI covers the visitor, Stand first applies specialization within each owner, then gives eligible owners equal shares and splits each owner’s share among their remaining Stand-ins. Adding more Stand-ins to one owner does not give that owner more of the total traffic.