How much does [service] cost / how do I get started
Pricing and service questions generated by the new site, answered from the client's published content instantly — deflecting the launch-week spike from your phone or inbox.
AI chatbot for web design agencies
AI chatbot for web design and development agencies
Sites you build generate the same launch-week and maintenance questions across every client. GoBrise answers those from content loaded before launch, under your studio's branding, and routes anything needing real development work to your team.
- New sites spike the same questions in the first week — pricing, delivery, how to get in touch
- Maintenance-retainer clients ask what's covered on a loop
- A branded widget on the delivered site reads as part of your build, not a vendor's
- A real bug or dev request always needs your team, not a bot
Last reviewed 20 September 2026
Quick summary
Launch-week
Pricing, availability, delivery timeline and contact-routing questions that spike right after a site goes live.
White-label
Logo, colours and welcome message configured per deployment; Growth and Business remove GoBrise branding entirely.
Per client
Each client's knowledge base and conversations are kept fully separate from every other business you manage.
$0
A client can start on the Free plan with unlimited human live chat before any AI spend is committed.
What people actually ask
Real questions this page answers, drawn from the conversations teams like yours handle every day.
What's included in our maintenance retainer
Scope, response time, and what counts as an extra — answered consistently from documented retainer terms, reducing scope disputes.
Can you fix / add [feature]
Routed to your team as a real dev request — the assistant explains process if documented, but doesn't attempt to resolve technical issues itself.
How do I update content on my own site
If you've documented a CMS or self-serve editing process, answered from that; otherwise routed to your team.
Is the site down / something looks broken
Escalated immediately as a potential real issue — never met with a generic troubleshooting script.
How it works
Step 1
Build the client's knowledge base before launch
Pull service pages, FAQ, policies, and contact routes from the site you built — most of the answers already exist in the build itself.
Step 2
Write maintenance-retainer scope explicitly
What's included, response times, and what counts as a billable extra — documented clearly reduces post-launch scope disputes.
Step 3
Separate documented answers from real dev requests
Pricing and process questions are automatable; anything sounding like a bug or feature request routes straight to your team.
Step 4
Configure branding to match the delivered build
Logo, colours, and welcome text set per client so the widget reads as part of what you shipped, not a bolted-on vendor tool.
Step 5
Test with the client's real launch-week enquiries
Pull twenty to thirty genuine questions from the client's inbox and run them through it before go-live, confirming answers match their published position.
Step 6
Review on a schedule across your client portfolio
Content ages per client as sites and retainers change — a recurring review, monthly works for most, keeps it useful without becoming a burden.
Who this is — and isn't — for
An honest read on where GoBrise fits, so you can rule it out quickly if it doesn't.
A good fit if
- You deliver and maintain client websites and want a branded support channel as part of the build
- Your clients have written, accurate content that becomes the assistant's source material
- You're comfortable running one account per client with strict content separation
- You want a recurring content-review service line rather than a one-off install
- Launch-week question spikes currently land on your phone or inbox instead of the client's site
Not the right tool if
- You need multi-client management under a single login with consolidated billing — that's roadmap, not shipped
- You want an unbranded widget on the cheapest plan — white-label presentation is on Growth and Business
- Your clients expect the assistant to read their CMS, booking system, or order data without a separate integration
- You want to resell under a contract that depends on capabilities not currently available
- Your clients' site content is thin or frequently out of date
Frequently asked questions
Can I install this on every site I build?
Yes, as a separate account per client — each with its own content, branding, and conversation history kept fully apart from every other business.
Will it handle a real bug report?
No — anything that sounds like a genuine technical issue is escalated to your team rather than met with a guessed troubleshooting answer.
Can each client's widget look completely different?
Yes, branding is configured per deployment — logo, colours, and welcome message are set individually for each client's build.
How do we price this as an added service?
That's a commercial decision on your side — whether you bill the client directly, mark it up, or include it in a retainer is entirely up to your studio.
How long does a client rollout take?
Most of the work is content — pulling accurate answers from the site you already built — so a focused build can be loaded and tested within a day or two.
Can the client's own team take over conversations?
Yes, human live chat is included on every plan, so a client can bring day-to-day responses in-house while you keep responsibility for content and configuration.
What if a client outgrows what the platform does today?
Scope honestly against what exists now, and be upfront that multi-client management under one login is roadmap without a committed date.
Can I trial this on my own agency site first?
Yes — running it on your own site before a client's is a good way to judge the setup and handoff yourself.
Try it on your own content
Start free with unlimited human live chat, add your content, and judge the answers for yourself.