Run a support agent for each client’s site

One workspace, one agent per client: each answers from that client’s own pages and wears that client’s look.

Support Agent · 6 steps

What you will have at the end.

One workspace with a Support Agent for each client site, each learning only from that client’s pages, each wearing that client’s brand, with every handover in one Inbox your team reads and replies to.

Built from

  • Each client’s own site
  • Client PDFs and FAQ pages
  • Files (PDF, Markdown, text)

What it produces

  • One agent per client site
  • A look per client
  • A shared Inbox for your team

Who it is for

Web agencies and freelancers who build and look after client sites and want an honest chat on each one without running a separate account per client.

Overview

An agency’s problem is repetition across sites: the same chat, set up again for each client, each with different pages and a different look. Doing that by hand is a half-day per client.

In hiy each client gets an agent of their own, inside your workspace. It learns from that client’s pages alone, so one client’s answers never touch another’s.

Why one agent per client, not one agent for all of them

An agent answers from the material it was given. Give one agent two clients’ pages and it can quote one client to the other’s customer. Separate agents make that mistake impossible.

A workspace keeps the work in one place. You invite your team once, and they read and reply to every client’s handovers in the same Inbox.

A brand keeps the look consistent. A brand is a look with a name and logo, made from the client’s site, and each form picks it in Look from.

Step by step

  1. Create an agent for the client

    Open the agent switcher and choose New Support Agent. Give it the client’s business name and a handle, and paste the client’s site address so Setup reads its pages.

    Repeat for each client. How many agents a workspace holds depends on the plan; the pricing page lists it.

    The switcher is where each new agent starts. Every client gets their own.
  2. Keep each client’s pages to themselves

    Add only that client’s material to that client’s agent: their site, their FAQ, their price list. Add any page Setup missed by its address.

    If a client has an answer only the owner knows, write it into Knowledge as a page, so the agent can cite it.

    One agent per client site, each reading its own client’s pages.
  3. Test each one before the client sees it

    Use the Test chat on each agent. Ask it three things the client’s pages answer and three they do not. The first three should cite a page, and the other three should say so plainly.

    The answer is built from the client’s own pages and carries its source.
    1. A questionThe agent checks your material.
    2. Material foundAnswer with a citation that opens the passage.
    3. Material missingAdmit the gap and add it to your queue.
    What happens at the edge of the material
  4. Give each client their look

    In Channels, Templates, make a brand for the client: a look with a name and logo, made from their site’s address. Each form then picks it in Look from.

    Only an owner or admin can change a brand, so a client’s look stays the one you set.

  5. Install on the client’s site

    Open Channels, choose Chat widget, and press Install on the client’s agent. Where to paste shows the steps for the client’s builder, such as WordPress, Webflow, Squarespace, Wix or Framer.

    List the client’s site under Allowed websites, choose Anyone on your sites, and paste the line it shows.

  6. Share the Inbox, then work the gaps

    Invite your team to the workspace. They read and reply to handovers in the same Inbox, whichever client’s site the question came from.

    Check Unanswered per client each week. A gap is a page the client has not written, which is a conversation you can have with them.

What this will not do

Every playbook carries this section, because a recipe that only lists what works is marketing.

  • The agents live in your workspace, not in a workspace of the client’s, and your team manages them there.
  • Anyone on your sites can open each agent, so tell clients to treat what it knows as public.
  • Each plan has a limit on how many agents a workspace holds. The pricing page lists it.
  • It adds one line you paste into the client’s site. It does not change the client’s pages.

Questions people ask first.

How many client agents can one workspace hold?

It depends on the plan. The pricing page lists every plan’s limits.

Can each client have their own look?

Yes. Under Channels, Templates, each client can have a brand: a look with a name and logo, made from their site’s address. A form picks it in Look from.

Can my team share the Inbox?

Yes. Invite teammates to your workspace and they read and reply to handovers in the same Inbox.

Which site builders does it install on?

There is an install guide for each of the common builders, including WordPress, Webflow, Squarespace, Wix and Framer. The install guides list every one.

Take it further.

The mechanisms behind these steps are written up on the blog: Support Agents posts

Build it, and test the edge first. Start free; the paid plan is free for 14 days.

Start free
  • 14-day free trial
  • No card needed
  • Paste a URL to start

Visitors always chat free. The private sandbox lets you break it before anyone else can — which is the step worth not skipping.

See the live demo