PRODUCT MODEL

One organization, focused product-demo surfaces

A surface is one configured buyer experience with its own publishable key, domains, behavior, and visitor activity.

Install your first surface
MENTAL MODEL

Keep each experience focused

Acme organization
├── Marketing product demo  → acme.com
├── In-product SDK demo     → app.acme.com
└── Expert video call       → optional human escalation

The organization groups team access. Each surface remains independently configurable so website visitors do not inherit signed-in app context and call activity does not mix with a different demo key.

Product demo

The default website or campaign experience: approved knowledge, product guidance, qualification, and handoff.

SDK assistant

An in-product demo that receives user, tenant, page, event, software-map, and safe-action context.

Video call

An optional browser-native path for visitors who need a human expert during the product conversation.

SHARED AND ISOLATED

What belongs where

OrganizationTeam membership and the relationship among surfaces.

SurfaceWidget key, allowed domains, experience type, knowledge copy, agent configuration, sessions, and call inbox.

Visitor contextScoped to the surface and session that received it.

Private credentialsRemain server-side and are never carried by the publishable key.

MANAGE

Add and switch surfaces

Open the organization menu in the workspace.

Choose Product demo, SDK assistant, or Video call.

Give the surface a clear purpose and use its own key.

Configure the exact hostnames where that key may load.

Use a separate surface when the audience, runtime context, domains, or follow-up path materially changes. Do not reuse one key merely to bypass a configured product boundary.