AI chatbots and assistants for agencies
We build white-label AI chatbots and assistants that your agency sells as its own. Each one answers from the client's approved content, shows where the answer came from and passes the visitor to a person when it should.
- ToolingClaude API · OpenAI API · Vector search
- Best forFull-service agencies
- Scope & quoteWithin 2 business days
AI assistants & chat, run the way agencies need it run.
AI and workflow automation that takes manual hours off an account.
Send the brief and a named producer turns it into a written scope: 6 deliverables, each priced, with the assumptions and the tools listed — Claude API, OpenAI API, Vector search, Next.js, PostgreSQL. Nothing is built until you have agreed that document, and the price on it is the price you pay.
It is the brief we see most often from full-service agencies, digital marketing agencies. Everything ships under your agency's name — the staging link, the commits, the checklist and the handover — and your client never learns we were involved.
- Pillar
- Automate — AI and workflow automation that takes manual hours off an account.
- Tooling
- Claude API · OpenAI API · Vector search · Next.js · PostgreSQL
- Most often for
- Full-service agencies
- Scope & quote
- Within 2 business days — scope
AI assistants & chat: what you get.
Every item here appears in the scope document with a price against it. Nothing starts until you approve it.
- 01Knowledge base ingestion and retrieval over the client's own content
- 02Assistant with citations, tone rules and refusal behaviour
- 03Hand-off to email, WhatsApp or live chat with full context
- 04Embeddable widget or integration into an existing chat tool
- 05Evaluation set and monthly quality review
- 06Analytics on questions, gaps and outcomes
A white-label AI chatbot is an on-site or messaging assistant that we build and your agency delivers under its own brand. The client sees your agency’s work, and we never contact them.
What a white-label AI chatbot should and should not do
It should answer from the client’s own content and admit when it cannot. It should not guess a price, a policy or a delivery date.
We build it on retrieval. The client’s pages, product data, policies and help articles are indexed, and each answer is drawn from those sources with a link back.
Tone rules keep it in the client’s voice. Refusal rules cover what it must not answer, such as legal or medical advice, or a price the content does not state.
Edge cases matter more than the demo. Visitors try to make it say odd things, pages contradict each other, content goes out of date and people paste personal details into the chat. We test for each before launch and set a schedule for refreshing the index.
Our plugin or a custom build
For many WordPress clients our own plugin is the quicker route. A custom build fits when knowledge lives in several systems, the site is not WordPress, or the agent must carry only your brand today.
| Situation | Best fit | Why |
|---|---|---|
| A WordPress site selling services or WooCommerce products | The free SoftVolt AI Voice Agent plugin | Voice and text chat, bookings, hand-offs and a leads inbox already exist. Speech runs in the visitor’s browser, so voice adds no cost. |
| The agent must show only your agency’s or the client’s brand now | A custom build | White label and agency mode are planned for the plugin’s Pro add-on, which is not available yet. |
| Knowledge sits in PDFs, a help desk or several systems | A custom assistant on the Claude or OpenAI API with vector search | Retrieval works across every source, with citations, inside a widget built in Next.js. |
| The client already uses a live chat tool | An integration into that tool | Their team keeps one inbox, and the assistant hands over inside it. |
Measuring whether it works
Every assistant ships with an evaluation set: real visitor queries with the answers the client signed off. We re-run it whenever the content, prompt or model changes.
The monthly review shows what the assistant answered, what it refused and what it passed to a person. Unanswered queries become content tasks, which gives your team a list of pages worth writing.
We do not promise a deflection rate before launch. We agree what to measure at scoping and report it plainly.
Pricing, data and the wider picture
A custom assistant gets a written scope and a fixed price within two business days of the brief. Model usage is billed at cost or runs on an API account in your name or your client’s. See the current plans on our rates page.
Chat transcripts can hold personal data, so we name the model provider in the data processing agreement. For UK and EU visitors we work under the UK IDTA or EU Standard Contractual Clauses, as our security page sets out.
Assistants often sit inside a wider process, such as routing leads to a CRM. That work is covered by our white-label AI automation and workflow automation services.
AI assistants & chat: when to send it.
- Support handles the same twenty questions all day
- A client wants a chatbot that does not make things up
- Sales needs pre-qualification outside office hours
- 01
Send the brief
Reply within 1 business day
- 02
Scope & quote
Within 2 business days
- 03
Production
Timeline fixed in the scope
- 04
QA & review
Published checklist, every build
- 05
Agency delivery
Handover doc with every launch
- Claude API
- OpenAI API
- Vector search
- Next.js
- PostgreSQL
AI assistants & chat: who briefs it most.
Questions agencies ask about white-label AI chatbots
01Will the chatbot make things up?
It is built not to. It answers only from the client’s approved content, shows the source and refuses when the content does not cover the topic. No model is perfect, so we re-run the evaluation set on every change and review real conversations each month. Anything sensitive, such as a complaint or a refund request, goes to a person.
02Can the chatbot carry only our agency’s or the client’s brand?
With a custom build, yes. The widget, the name and the voice belong to the client, and nothing mentions us. Our free plugin does not offer white label mode yet, as that is planned for its Pro add-on. For an unbranded agent today, we scope a custom assistant under your brand.
03Which AI model runs it, and who pays?
Custom assistants run on the Claude API or the OpenAI API, chosen from the evaluation results for that client’s content. Usage is billed at cost or held in your or your client’s account, with no mark-up. Our plugin also works with free tiers from OpenRouter, Groq and Gemini, which suits a trial.
04Where are the conversations stored?
In a database the client owns. With our plugin that is their own WordPress database, where only administrators can see leads. Custom builds use a PostgreSQL database in the client’s hosting account. For UK and EU visitors we work under a data processing agreement, with the model provider named as a sub-processor.
05Can it book appointments or take payments?
Our plugin books services and saves each booking in WordPress, and in a WooCommerce shop it adds products to the cart for the normal checkout. Payments in the chat are planned for Pro, not available today. A custom assistant can connect to the client’s booking system where that system has an API, which we confirm at scoping.
Send the brief — get a fixed price within two business days.
Tell us what the AI assistants & chat project needs and when. Client names can wait until the NDA is signed; a named producer replies within one business day.

