A chatbot that knows your business, not the internet.
A customer-facing assistant trained on your own docs, policies and product content, built to say ‘I don’t know’ honestly and hand off to a person when it should.
The problem
Generic chatbot widgets don’t know your business.
Most chatbot widgets are trained on the general internet, with your content bolted on top as a thin layer. Ask one something specific about your policies, your pricing or your product range and it will often guess, sounding entirely confident even when it is wrong, which erodes customer trust faster than having no chatbot at all.
It’s also usually the same widget every competitor in your industry is running, with a different logo pasted on top. It answers from the same shallow script, misses the details that make your business different, and quietly tells your customers that nobody actually built this for them.
We build assistants that answer only from your own content. That content is retrieved live, not memorised loosely from a training run. If a question goes past what the content covers, there’s a clear path to a human. It’s the same retrieval discipline behind our wider AI product development work, aimed here at the front door of your website.
If your site already runs on WordPress, this installs as part of the platform. It’s not a separate widget pasted into your theme. Read more on our WordPress development page.
There’s also a difference between a chatbot that answers questions and one that’s asked to do more, book a slot, run a quote, take a payment. Both are useful, but they’re not the same build. We’ll tell you plainly which one you actually need before we scope a price, rather than sell you the bigger build by default.
What you get
Built on your content, not a generic script.
Trained on your content
Docs, policies, FAQs and product pages, indexed and kept current as your content changes, rather than a one-off snapshot that quietly goes stale.
Honest ‘I don’t know’
When the answer isn’t in your content it says so and offers a next step, rather than producing a confident-sounding guess.
Human handoff
A clear trigger moves the conversation to a real person, and the full context travels with it, so nobody has to repeat themselves.
Lead capture
Names, emails and enquiry details, captured in the chat and sent straight to your inbox or CRM.
Analytics
See what people actually ask, where the chatbot falls short, and what content is worth adding next.
Installs on any site
Built for WordPress specifically, or as a standalone widget for any other platform you run.
Process
How we build one.
Content review
We go through your docs, policies and product pages, flagging gaps and agreeing what the assistant will and won’t answer, including the topics it should stay well away from.
Build and test
We build the assistant against real customer questions rather than invented examples, checking how it handles the ones it should refuse and how it behaves when somebody tries to trick it.
Human handoff setup
We connect the handoff to wherever your team already works, email, live chat or a helpdesk tool. Nothing new for your team to learn or check each morning.
Launch and tune
We watch real conversations after launch and tighten the content and rules around what customers actually ask, rather than what anybody guessed they would ask.
Why Maku
Built to be honest, not just impressive in a demo.
A chatbot that looks great in a five-minute demo and then makes something up in week three isn’t a win. We build for the second month, not the first five minutes. Our evals specifically test the failure cases most teams skip. Our AI strategy service is a good place to start if you’re not yet sure a chatbot is the right use case at all.
- Answers grounded in your content, with an honest fallback when it doesn’t know.
- Human handoff built in from the first sketch, not bolted on once customers complain.
- You own the code and the content pipeline. No lock-in to our platform.
- An engineer reads every answer path before launch, including the ones where the assistant has to refuse.
- Built by the same team behind our AI product development work, so retrieval, evals and guardrails come as standard.
Will it make things up about our business?
Every generic chatbot risks this, which is why we build ours to answer only from your own content, your docs, policies and product pages, and to say ‘I don’t know, let me connect you with someone’ rather than guess. We test this directly before launch.
Can it hand off to a real person?
Yes. You set the trigger, a question it can’t answer, a frustrated tone, a request to speak to someone, and the conversation moves to a human with the full history attached, so your customer never has to repeat themselves.
Does it learn from conversations automatically?
Not on its own, and that’s deliberate. It answers from the content you approve. We review conversation logs with you on a regular basis and update that content deliberately, so nothing changes without a person signing off.
Where does our customer data go?
Conversations are stored so you can review them and see analytics, and we set out exactly where that data sits and who can access it in the project agreement. It’s not used to train anyone’s general-purpose model.
Can it book, quote or sell, not just answer questions?
It can, once it’s connected to the right system behind the scenes, your booking calendar, your quoting tool, your payment page. That’s a bigger build than a pure answer-bot, and we’ll scope it honestly rather than promise it by default.
How does this fit with our WordPress site?
It installs directly into WordPress as part of the site, not as a bolted-on widget from a third party. See AI for WordPress for the wider set of AI features we build into the CMS itself.
What does a chatbot like this cost?
It depends on how much content it needs to work from and what it connects to beyond answering questions. Every build is scoped and quoted at a fixed price before we start, so tell us what you want it to handle and we’ll price it properly.