01
Client boundaries stay explicit
Knowledge, customer history, credits, and team access belong to one Workspace.
Customer support for agencies
Keep each client in a separate Workspace with its own Agent, sources, Website chat, team access, and customer history.
Start with 100 creditsOne-time $1 activation · 100 credits included · No automatic subscription
How it works
Client work stays easier to operate when brand, knowledge, ownership, and reporting share one boundary.
01 · Separate
Keep Agents, sources, credits, Members, and Conversations inside the correct client boundary.
Client Workspaces
SeparatedNorthstar
2 Agents
Harbor
1 Agent
Juniper
3 Agents
02 · Match
Choose the Widget appearance, customer copy, Agent voice, and trusted sources for the client.
Client brand
SavedAppearance
Matched
Agent voice
Approved
Knowledge
Connected
03 · Operate
Assign agency teammates and client Members without exposing unrelated Workspaces.
Client Inbox
AssignedConversation
Northstar
Agency owner
Mira
Client Member
Available
Every client keeps a distinct support system. Your team keeps one clear way to operate it.
What changes
The operating model stays consistent while the brand, content, permissions, and Conversations remain client specific.
01
Knowledge, customer history, credits, and team access belong to one Workspace.
02
Appearance and Agent voice can match the client instead of the agency tool behind it.
03
Agency teammates and client Members can collaborate without opening unrelated accounts.
Designed for the edge cases
Use the same setup pattern for every client while preserving the separation each relationship requires.
Keep every client Agent, source, Conversation, credit balance, and Plan in a separate boundary.
You stop dealing with: tagging one giant account and hoping nothing crosses into the wrong client.
Match the support surface, opening copy, and placement to the client website.
You stop dealing with: shipping the same agency branded chat on every client property.
Invite agency and client people only to the Workspaces where they should work.
You stop dealing with: sharing broad credentials or exporting Conversations for review.
Review questions, answer gaps, and workload inside the relevant Workspace.
You stop dealing with: rebuilding client reports from blended exports.
Separation clients can trust
The agency can standardize the work without blending the data, brand, or customer experience.
Boundary
Knowledge, Conversations, Members, and billing remain scoped together.
Brand
Widget appearance and Agent voice match the business receiving the support.
Access
Agency and client Members receive only the Workspace access they need.
Choose the agency operating model
Compare how each approach handles separation, brand, access, and reporting.
Questions before you start
How separation, branding, access, and ownership work.
Connect the client knowledge, match the Widget, and invite only the people who should handle that account.
Start with 100 creditsOne-time $1 activation · Grounded answers · Human takeover · Cancel anytime