Support as a retained service line
Add a chat channel to a build or care plan without staffing a support desk. The client's own content answers the repeatable questions, and a named person on their side handles the rest in the same inbox.
An AI chatbot for agencies has a different brief than one for a single business. You are deploying on sites you do not own, for clients with different content and tone, and the branding on the widget reflects on your studio rather than on a vendor. GoBrise supports that with white-label presentation and strict separation between each business you run — with one honest caveat about multi-client management, below.
Last reviewed 17 September 2026
Per client
Data separation
Each client's knowledge base, conversations and team are kept separate from every other business on the platform.
Growth+
White-label presentation
Growth and Business remove GoBrise branding; Free and Starter show the published branding treatment.
$0
Client entry point
A client can start on the Free plan with unlimited human live chat before any AI spend is committed.
Roadmap
Multi-client console
A dedicated agency tier with multi-client management under one login is planned, without a committed date.
Five ways studios put a support widget to work across a client portfolio, and where the current product genuinely fits.
Add a chat channel to a build or care plan without staffing a support desk. The client's own content answers the repeatable questions, and a named person on their side handles the rest in the same inbox.
New sites generate a spike of the same questions: pricing, availability, delivery, how to get in touch. Loading the client's published answers before launch keeps that spike off their phone line and out of your inbox.
For clients whose site is mainly a shop window, a widget that answers service and pricing questions and passes qualified conversations to a person is a measurable addition to a project you already delivered.
Logo, colours and welcome message are configured per deployment, and white-label plans remove GoBrise branding so the chat experience reads as part of what your studio shipped.
Because human live chat is included on every plan, a client can take day-to-day conversations in-house while you keep responsibility for the content and configuration.
Treat each client as its own deployment with its own content and its own account. The pattern that works is to standardise your process — discovery questions, content template, test set, handover doc — rather than trying to share one configuration across businesses with different answers.
Step 1
The clients who benefit are the ones fielding repeat questions with written answers: service scope, pricing, availability, delivery, opening hours, policies. Clients whose enquiries are all bespoke quotes or account-specific lookups will get less value and more escalations. Say that during scoping rather than after launch — a short qualification conversation protects the retainer and sets a fit expectation you can be held to.
Step 2
Write down what you are selling: install and branding, an initial knowledge base built from the client's existing pages, a test pass against real questions, and an agreed content-review cadence. Decide who pays for the plan — the client directly, or you, rebilled — and who owns the account if the relationship ends. Clarity here matters more than the technology, because support content ages and someone has to own it.
Step 3
Create the client's own account so their knowledge base, conversations and team access stay distinct from every other business you manage. Install the snippet on their site, then configure the logo, colours and welcome text to match the build you delivered. Confirm which plan they are on before promising an unbranded widget: white-label presentation is on Growth and Business, while Free and Starter show the published GoBrise branding treatment.
Step 4
Most of the answers are on the site you built: service pages, pricing, FAQ, policies, contact routes. Turn those into clear, non-contradictory source content, and interview the client for the questions they answer by phone that never made it onto a page. Remove outdated promotions and duplicated policies. On Growth and higher, website crawling and automatic updates reduce the ongoing maintenance; on lower tiers, plan for manual edits.
Step 5
Pull twenty to thirty genuine enquiries from the client's inbox and run them through. Check that the answers match their published position, that anything needing a quote or a decision escalates, and that the client's team receives the handover. Then do a short handover session: how to read the inbox, how to reply, how to take over a conversation, and how to tell you when an answer is wrong.
Step 6
Set a recurring review — monthly works for most — where you look at escalation patterns per client and turn repeated gaps into content updates. This is what makes the service worth a retainer rather than a one-off install. Until a dedicated agency console exists, that review means moving between client accounts, so keep the process light and documented so anyone in the studio can run it.
This page is more useful to you as a scoping tool than as a pitch. The current product suits a certain kind of agency deployment well and a certain kind badly.
You can deploy a white-labelled widget on client sites today: Growth and Business remove GoBrise branding, and the logo, colours and welcome message are configured per deployment. What does not exist yet is a formal reseller programme with multi-client management under one login and reseller pricing. That is on the roadmap without a committed date. If a client contract depends on it, talk to us about where it stands rather than writing it into a proposal.
Each client runs as its own account, which keeps knowledge bases, conversations and team access completely separate. The trade-off is administrative: you move between accounts rather than seeing a single portfolio view. Agencies handle this by standardising the process — the same content template, the same test set, the same monthly review — so switching context is quick. If you manage a large portfolio, weigh that overhead honestly before committing to a fixed-fee support service.
Decide it in writing at the start, because it is awkward later. Many studios put the account in the client's name and take administrative access, which means the client keeps their data and history if the relationship ends. Others hold the account and rebill, which is simpler operationally but needs a clear exit clause. Either can work; what causes disputes is leaving ownership, billing and data portability unstated until someone asks to leave.
Yes. Branding is configured per deployment, so logo, colours and welcome message follow the site you built rather than a shared studio look. On Growth and Business, GoBrise branding is removed entirely. Free and Starter deployments keep the published branding treatment, so if an unbranded experience is part of what you sold, make sure the client is on a plan that includes it before launch.
Yes. Each business on the platform has its own knowledge base, conversations and team, and content from one client is not used to answer another client's visitors. This is a core part of the design rather than a configuration option. If you have a client with specific contractual requirements about data handling, review those requirements with us directly instead of assuming a general statement on a marketing page covers them.
We will not invent a number for you, but the shape most agencies use is a setup fee for install, content build and testing, plus a monthly retainer covering the plan cost, content maintenance and a review. The retainer is justified by the ongoing work: support content drifts as the client changes services, prices and policies, and an assistant answering from stale content is worse than no assistant. Price the review, not just the install.
The installation itself is quick — a snippet on the site and a branding configuration. The realistic timeline is set by content: gathering the client's answers, resolving contradictions between pages, and testing against real enquiries. For a client with a well-maintained site, a focused week is achievable. For a client whose policies live in staff members' heads, budget longer and treat the content interview as part of the deliverable.
Yes, and usually they should. Unlimited human live chat is included on every plan, including Free, so the client's team can take conversations directly. When a person replies or takes over, the AI stops speaking in that conversation, which avoids the client's staff and an automated reply contradicting each other while a customer is watching.
Be upfront about the boundary. GoBrise focuses on website chat with grounded AI answers and clean human handover. A client who needs outbound campaigns, a large integration marketplace or deep CRM-driven workflows may be better served elsewhere, and telling them that protects your credibility. Our comparison page sets out where GoBrise differs from a broader suite, which is a useful reference during a client conversation.
That is the approach we would recommend. Install it on your studio site, load your own service and process content, and run your real enquiries through it. You learn where the content work is, how escalation behaves and what the handover feels like — before any of it happens in front of a client. It also gives you an honest reference point when a prospect asks what it is actually like to run.
Where the agency offering stands today, including the roadmap caveat.
What the branded widget includes, and on which plans.
A factual comparison to use when scoping with a client.
How we compare with a URL-first AI agent builder.
How we compare with a live-chat-first platform.
Plan tiers, AI conversation allowances and white-label availability.
Start free with unlimited human live chat, load your studio's content, and judge the handover for yourself.