An Assistant With
a Defined Job
A Knowledge Base Written Properly
Your services in the language customers use, coverage area including the places you do not serve, pricing guidance with the factors that move it, availability, and honest answers to your twenty most common questions. Pointing a bot at your website and hoping is how you get confident nonsense.
Qualification That Feels Like Conversation
It gathers what your team would ask anyway — what they need, where they are, when, roughly what budget — without turning into an interrogation, and it asks for contact details after it has been useful rather than before.
Live Calendar Booking
Reads your real availability and books a genuine appointment with confirmation and reminders. This is the point at which chat stops being a cost centre and becomes a channel.
Honest Handover Rules
Defined triggers for reaching a human: explicit request, repeated confusion, any sign of frustration or complaint, anything high value or sensitive. It says what happens next and then that actually happens.
Multi-Channel Deployment
The same assistant on your website, Facebook Messenger, Instagram and WhatsApp, with conversations landing in one inbox instead of four apps nobody checks consistently.
CRM Integration and Transcripts
Every conversation creates or updates a record with the full transcript attached, so whoever picks it up already knows the story. Nothing undermines a chatbot faster than a customer having to repeat everything they just typed.
How We Build a Chat Assistant
Scoped narrowly, briefed thoroughly, and improved from real transcripts every week.
Define the Job
We agree exactly what it will handle and, just as importantly, what it will not attempt. A bot asked to be a general-purpose assistant does everything badly. One with three specific jobs does them well.
Build the Knowledge
We work through your services, pricing logic, coverage, availability and common questions, and we write explicit boundaries. A bot instructed to defer will defer, and that earns more trust than one that improvises.
Design the Conversation
Opening behaviour, timing of the prompt, tone, qualification flow, booking path and handover points. It waits until the visitor has been around long enough to have a question, it says it is an assistant, and it lets people type freely.
Connect and Deploy
Wired to your calendar, CRM and messaging channels, then launched on the pages where it makes sense rather than everywhere at once.
Read Transcripts and Improve
Every week we sample conversations, especially the ones that went wrong. Each failure is a specific gap in the knowledge base, and fixing ten of them visibly improves the next hundred.
What a Well-Built
Assistant Produces
Enquiries From Hours You Do Not Work
Evenings and weekends frequently account for a third or more of conversations. Those are enquiries that previously did not exist at all, rather than ones moved from another channel.
Instant Answers to Repetitive Questions
The same six questions, answered properly every time, without taking anyone off the job. Both a service improvement and a real reduction in interruption.
Appointments Booked Without a Call
For many businesses this is the number that justifies the whole thing. A visitor who would have left with a half-formed question ends up in the calendar instead.
Visitors Who Would Have Left Silently
Most people with a question never ask it. Chat catches a portion of those, and they are leads you were never going to hear from otherwise.
Questions We Get
About AI Chatbots
They are annoyed by bad ones, and reasonably so. What causes it is predictable: popping up immediately, pretending to be human, forcing people down button paths, demanding an email before saying anything useful, and refusing to hand over. We design against all of those deliberately, and people are entirely comfortable talking to a bot that is genuinely useful.
Those were decision trees: if the visitor clicks A, show B. They broke the moment someone typed something unexpected. Current systems understand what is being asked, work from a knowledge base you control, and hold a natural conversation. The gap in quality is very large.
Yes, against your live calendar with your real availability rules, and it sends confirmation and reminders. It can also collect payment or a deposit at booking if that suits your business.
That is a briefing problem more than a technology problem, and we manage it three ways: a carefully written knowledge base, explicit instructions to defer rather than guess on anything uncertain, and weekly transcript review. An assistant that says it does not want to guess and offers a callback is more trustworthy than one that answers everything.
Yes, and it will typically detect and reply in the visitor's language. Worth setting up properly if you serve a mixed-language area, and worth turning off if you cannot support those conversations once they reach a human.
Yes. The same assistant with the same knowledge base can run across your website, Messenger, Instagram and WhatsApp, with everything landing in one place. That consolidation is often as valuable as the automation itself.
Usually two to three weeks. Most of that is the knowledge base and the conversation design, which is the part that determines whether it is good. The technical deployment is quick by comparison.
Resolution rate, conversations that produced a contactable lead, appointments booked, handover rate over time, and the share of conversations happening outside working hours. Conversation count on its own is a vanity metric.
Curious What It Could
Handle for You?
Book a free call. We will look at the questions you answer most and show you what a properly briefed assistant would take off your hands.
See What It Could Handle →