Multiple sites, one account

How it works

Each website you connect becomes its own project inside your workspace, with a fully separate widget configuration, AI knowledge base, and set of flows — nothing bleeds between projects, so a knowledge-base file uploaded for one site never surfaces as an answer on another.

Despite that separation, everything sits under one workspace: one login, one bill, one team member list you manage once instead of duplicating across accounts. Switching between projects is a dropdown away, not a separate sign-in.

Why it matters

Running chat on more than one property usually means either paying for and logging into multiple separate tools, or forcing all sites to share one undifferentiated configuration. Project-level isolation with workspace-level billing avoids both — each site gets a tailored setup without multiplying accounts.

Example use case

An agency manages ten client websites under one workspace and one invoice. Each client's project has its own branded widget and its own knowledge base trained only on that client's content, while the agency's team members can be granted access per project as needed.