Professional services · website AI assistant
AI chatbot for Agencies
Updated
The short version
Ship a cited AI assistant on client sites as a retained service — three bots on one plan, branding removed, one script tag per site.
Agencies get asked for chatbots constantly, and the honest answer has usually been "it's more work than it looks". Building one properly means retrieval, embeddings, a widget, and a content pipeline you'll be maintaining long after the invoice clears.
The alternative most agencies land on — a per-client SaaS seat — turns a service into a margin problem, and the branding on the widget belongs to somebody else.
MySiteGPT is deliberately narrow here: three bots on one $9.99/mo plan, branding removable, and an API plus webhooks if you want the conversations flowing into whatever the client already uses. You train each bot on that client's content, drop one script tag in their site, and the deliverable is something you can demo in the pitch rather than describe.
What agencies and freelancers get asked
Real questions, in visitors' own words. Every one of these is answerable from content you probably already publish.
- “Can I run separate assistants for separate clients on one account?”
- “Can I remove your branding from the widget?”
- “How long does it take to set one up for a new client?”
- “Can I hand the client a dashboard, or does it stay with us?”
- “Can leads captured in the widget go to the client's CRM?”
- “What do I charge for this?”
How MySiteGPT helps agencies and freelancers
Three client bots on one plan
Each bot has its own content, its own widget styling, and its own lead inbox — so one subscription covers a small portfolio rather than one logo.
A demo, not a deck
Train a bot on the prospect's public site before the pitch and let them ask it their own questions. Cited answers from their own content is a more persuasive proposal than any slide.
Your branding, or none at all
Branding is removable on the paid plan, and the widget's colors, position, and copy are yours to set — it ships looking like part of the site you built.
Wire it into what the client already runs
The API and webhooks push captured leads and conversations wherever they need to land, so the assistant becomes part of the client's stack instead of another login.
What to train it on, in order
The answers are only as good as the index behind them. Start at the top — these are ordered by how much question volume they absorb per page trained.
- 1
The client's public site, via sitemap crawl
The fastest path to a working demo. Run their sitemap through the free sitemap analyzer first to see what you're about to train on.
- 2
Their service and pricing pages
Where the pre-sales questions land. If the pricing is deliberately vague, use Q&A pairs to control exactly what the bot will and won't say.
- 3
PDFs, brochures, and onboarding packs
The content clients have but never published as web pages. Upload them and they become answerable.
- 4
The questions their sales team is tired of
Collect twenty and add them as Q&A pairs on day one. It's the cheapest quality win in the whole setup.
Not sure your pages are ready to be retrieved from? Run one through the RAG readiness checker first, or audit the whole site with the sitemap analyzer.
What to measure once it's live
We don't publish other people's numbers as if they were yours. Track these instead — they are all visible in your own dashboard within a fortnight.
- Setup time per client — this should fall sharply after the first one
- Leads captured per client site per month, as a retainer justification
- Unanswered questions you can bill to fix as content work
- Client support enquiries that never reached their inbox
AI chatbot for Agencies: frequently asked questions
Is there a white-label or reseller plan?
There's no separate reseller tier. The Pro plan removes branding and includes three bots, an API, and webhooks, which covers most small portfolios. For a larger book of clients the straightforward route is one account per client, billed through you.
Can each client see their own conversations?
The dashboard is per-account, so the usual pattern is that you hold the account and share what matters — captured leads by email alert or webhook, and a periodic report of what visitors asked.
How long does a new client bot take to set up?
Point it at their sitemap, let the crawl finish, spot-check a dozen questions in the playground, then paste the script tag. For a typical marketing site that's under an hour, most of it spent testing rather than configuring.
What if the client's content is bad?
Then the answers will be, and it's better to find that out in the playground than in production. Run key pages through the free RAG readiness checker — the gaps it flags are usually a billable content engagement in their own right.
Try it on your own content first.
The chat bubble on our homepage is the product, trained on our own site — ask it anything and watch every answer cite its source. Then train one on yours: 14 days, full features, no card.