Skip to content

Run client support without mixing client knowledge, brands, or Conversations.

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 credits

One-time $1 activation · 100 credits included · No automatic subscription

A website chat preview updates and confirms the saved appearance.

How it works

Give every client a support system with clear boundaries.

Client work stays easier to operate when brand, knowledge, ownership, and reporting share one boundary.

  1. 1

    01 · Separate

    Create one Workspace for each client

    Keep Agents, sources, credits, Members, and Conversations inside the correct client boundary.

    Client Workspaces

    Separated

    Northstar

    2 Agents

    Harbor

    1 Agent

    Juniper

    3 Agents

  2. 2

    02 · Match

    Configure the support experience for that brand

    Choose the Widget appearance, customer copy, Agent voice, and trusted sources for the client.

    Client brand

    Saved

    Appearance

    Matched

    Agent voice

    Approved

    Knowledge

    Connected

  3. 3

    03 · Operate

    Route client Conversations to the right people

    Assign agency teammates and client Members without exposing unrelated Workspaces.

    Client Inbox

    Assigned

    Conversation

    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

Client separation without a different tool for every account.

The operating model stays consistent while the brand, content, permissions, and Conversations remain client specific.

01

Client boundaries stay explicit

Knowledge, customer history, credits, and team access belong to one Workspace.

02

Each customer surface looks intentional

Appearance and Agent voice can match the client instead of the agency tool behind it.

03

The right people see the right Inbox

Agency teammates and client Members can collaborate without opening unrelated accounts.

The Agent answers first, then Priya joins the same Conversation.

Designed for the edge cases

An agency operating model that remains understandable.

Use the same setup pattern for every client while preserving the separation each relationship requires.

Workspace isolation

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.

Client specific Widget

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.

Scoped Member access

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.

Per client reporting

Review questions, answer gaps, and workload inside the relevant Workspace.

You stop dealing with: rebuilding client reports from blended exports.

Separation clients can trust

One repeatable system. Clear ownership for every client.

The agency can standardize the work without blending the data, brand, or customer experience.

Boundary

One client belongs to one Workspace

Knowledge, Conversations, Members, and billing remain scoped together.

Brand

The customer sees the client experience

Widget appearance and Agent voice match the business receiving the support.

Access

Collaboration stays intentional

Agency and client Members receive only the Workspace access they need.

Choose the agency operating model

Client Workspaces instead of a blended support account.

Compare how each approach handles separation, brand, access, and reporting.

Client data boundary

CommunicatePer Workspace
One shared botTags and folders
Separate toolsSeparate accounts

Client branding

CommunicatePer Widget
One shared botShared template
Separate toolsTool dependent

Member access

CommunicateWorkspace scoped
One shared botBroad account access
Separate toolsDifferent systems

Operating consistency

CommunicateOne workflow
One shared botOne account
Separate toolsTool by tool

Questions before you start

Questions agencies ask about client setup.

How separation, branding, access, and ownership work.

Give every client a support system with a clear boundary.

Connect the client knowledge, match the Widget, and invite only the people who should handle that account.

Start with 100 credits

One-time $1 activation · Grounded answers · Human takeover · Cancel anytime