Website Chatbot
Answer Every Website Visitor Before They Leave
A visitor with one unanswered question is a job you never hear about. We build an AI chatbot for your website that answers what people actually ask before they buy, scoped to exactly what you want it handling and nothing you don't.
The problem
Where website enquiries go cold
Most people who land on your site leave without telling you they were there. They have one question, do you cover my area, do you take on this kind of job, how soon could you start, and the answer isn't on the page they're reading. There's a contact form, but filling one in means waiting until tomorrow for a reply, so they go back to the search results and open the next tab instead. You never see that enquiry, because it never became one. The traffic reports as a visit and nothing else.
Process
How we build an AI chatbot for your website
-
We start from your real questions
We go through what people actually ask you before they buy, and which of those answers are already somewhere on your site.
-
You decide what it handles
What it should answer, what it should never touch, and what happens when someone is ready to act. That scope is the build.
-
We build it and put it live
We handle installation. You don't need a developer, and you don't need to rebuild anything you already have.
-
We read what visitors asked and tighten it
After launch we go through how it's handling real questions and adjust the answers until the common ones are covered well.
Use cases
What we build it to do
-
Answer the questions that decide a sale
Do you cover my area, do you take on this kind of job, how soon could you start.
-
Qualify before you spend time
Ask the two or three things you need to know before a job is worth quoting.
-
Take details when someone's ready
Name, contact and what they need, passed to you however you want to receive it.
-
Point people to the right page
Send a visitor to the service, the example or the form that actually answers them.
-
Cover the hours nobody's watching
Evenings and weekends, when your site still gets traffic and nobody is at a desk.
-
Hand over when it should
Some questions shouldn't be answered by software. You decide which, and it passes those to you.
Cost
What affects the cost
Every project is priced after the discovery call. What moves it: how much it has to know before it can answer well, how many questions you want it covering, whether it only answers or also takes details and passes them on, how many languages, and whether you want us reviewing and improving it after launch.
FAQ
Frequently asked questions
We decide that with you before anything is built. It can work from what's already on your site, from a set of questions and answers we write together, or both. Settling which is part of the discovery call, because it's what determines how well it answers.
You do. We don't ship a fixed product with a feature list. You tell us what it should handle and what it should never touch, and that scope is what we build. If you want it answering questions and nothing else, that's a perfectly good build.
Yes. We build it in the languages you need rather than defaulting to English and adding the rest later. Which languages is one of the things we confirm on the discovery call, because it shapes both the build and what it takes to run.
It depends on the scope you set, which is why we don't put a timeline on it before the discovery call. A chatbot covering a handful of known questions is a much shorter build than one that has to handle a wide range and pass enquiries into your systems. We give you a date once we know which one you are asking for.
We handle installation, so this is our problem rather than yours. Tell us what your site is built on when we speak and we'll confirm it before you commit to anything.