Marketing agencies

Add a support bot to every client site you build

You already build and maintain the sites. Adding an assistant that answers from each client's own content is a service line, not a new product to learn.

Start free See how it works

No credit card. Live in an afternoon.

“Can I put this on a client's WordPress site?”

“Does it carry our branding or yours?”

“What does it cost per client?”

“Can you build a custom integration for a client?”

What an agency actually gets asked

Both columns matter. The right-hand one is what a reader is really checking for, so it is on the page rather than in a footnote.

Answered from your own pages

The reply is the answer, with a link to the page it came from.

“Can I put this on a client's WordPress site?”
“Does it carry our branding or yours?”
“What does it cost per client?”
“Can each client have their own login?”
“How long does setup take per site?”

Handed to a person

Declined plainly, then routed with the whole conversation attached.

“Can you build a custom integration for a client?”
“Can the client dashboard sit on our own domain?”

Each of these arrives with the whole conversation attached, so whoever picks it up starts from what the customer already said rather than from a one-line message.

A fanned row of coloured client project folders beside a closed laptop on an agency desk between projects.

Retainers need recurring value, not another one-off

Site builds end. Retainers need something that keeps producing visible value every month, and most add-ons are either invisible to the client or another subscription you have to mark up awkwardly.

Retainers are hard to justify once a build is finished
Every client tool means another subscription and another login
Clients contact vendor support directly and cut you out
Reporting value monthly means assembling it by hand

You have already written most of it

Point the crawler at these four and the assistant has what it needs. There is nothing to re-author, and nothing to keep in sync afterwards.

01
Each client's own site
The crawl is per client, so answers stay theirs.
02
Client policy pages
Shipping, terms, services — whatever they publish.
03
Uploaded client material
Anything not on the public web goes in as a document.
04
Your own service pages
So the assistant on your site explains your service line.

A service line under your own brand

The widget is white-labelled and each client gets a login scoped to their own data. On their own site the client sees your agency delivering an assistant, not a vendor they could have bought from directly.

Your brand on the widget: Logo, colours, avatars and teaser per bot, with the Powered-by badge off.
Per-client logins: Each client sees their own conversations and leads, and nothing else.
One console for you: Every tenant, source, and spend cap manageable from a single place.
Metered, not per-seat: Adding a client does not add a subscription to expense.

Monthly reporting that writes itself

Conversations handled, questions asked, leads captured, and the ranked list of content gaps. That last one is a content brief you can sell — the client's own visitors telling you which pages to write next.

Costs that cannot surprise you

Per-tenant daily caps and domain locks mean a client's traffic spike has a known ceiling. You can price a retainer confidently because the cost side has a maximum you set.

A workspace per client

Separate knowledge, separate conversations, nothing shared between them.

A monthly report that writes itself

Conversations handled and a ranked content-gap list, per client.

A ceiling per client

Hard daily caps mean one busy site cannot consume the retainer.

Deployed in an afternoon

A crawl and two lines in the theme, with no engineering per account.

Where the line is

The widget is white-labelled; the dashboard is not

Branding, per-client workspaces and the removal of the Powered-by badge are all part of the Agency plan, and they cover the part your client's customers actually see. The console is the exception: clients sign in at app.matterchat.co and it carries our name. There is no custom domain and no rebranded dashboard at any tier today.

Per-client branding on the widget, set per bot
Clients log in scoped to their own conversations and leads
Master controls and spend caps stay with you
The sign-in page is ours — say so before you promise otherwise

There is a fuller version of this on the agencies use-case page, including how the pricing works when you add a client rather than a seat.

A printed monthly report lying open on a studio table, pages tabbed with coloured flags, reading glasses folded at the edge.

What an agency asks first

Short answers. If yours is not here, the assistant on this page will try it — and tell you honestly if it cannot.

Can clients tell it is Matter Chat?

Not from the widget — branding is per bot and the Powered-by badge comes off on Agency. The dashboard is the exception: clients sign in at app.matterchat.co under our name.

How do we bill clients for it?

Pricing is metered rather than per-seat, so you buy capacity and resell at whatever markup your market supports. The per-bot caps let you bound the cost of each client you have quoted.

Does each client need their own knowledge base?

Yes, and that is the point — each bot is indexed on that client's own site and documents, so answers come from their content and are domain-locked to their site.

All solutions