Watch someone decide to book almost anything and there is a step before the booking: a question. Do you work on this make of boiler. Is the Saturday class all right for a complete beginner. Can I bring the dog. The booking form is the last step. The question is the one that decides whether they ever reach it.
Most small business sites handle that question with a contact form and a promise to reply within one business day. The customer asked in the moment they were ready. The reply arrives when they are not — or after a competitor who answered on the page has already taken the booking.
Why is the question the real bottleneck?
Because intent is perishable and the question is blocking. It is usually small — a yes or a no, a price, a time — but until it is answered the customer cannot commit, and the longer it waits the more likely they are to answer it somewhere else. A contact form takes an instant question and turns it into a correspondence. Every step of a correspondence is another chance for the customer to wander off.
The encouraging part is how repetitive these questions are. Ask anyone who answers the phone at a small business and they will list the same dozen within a minute. That repetition is what makes the problem solvable: you are not trying to answer everything, only the handful of things nearly everyone needs to know before they book.
“A contact form turns an instant question into a correspondence, and every reply is another chance for the customer to wander off.”
Answer the common questions on the page first
Before any tool, the cheapest assistant is a page that already answers. Each service page should say plainly what is included, who it is for and who it is not for, what it costs or at least what it starts from, and how soon you can do it. Most customers will never need to ask anything if those four things are on the screen in front of them.
This is unglamorous work and it is almost always skipped, because the answers feel too obvious to write down. They are obvious to you. To someone deciding at nine at night whether to book, they are the only thing on the page that matters.
What a site assistant is actually for
Pages handle the common questions. An assistant handles the long tail and the evening — the less frequent question, asked at the moment nobody is there to answer it. That is the job we built Haswell Chat to do. It answers from the business’s own content: its services, its team, its policies. When the customer is ready, it books the appointment without leaving the conversation, through Haswell Book.
When it cannot help, it says so and hands over to a person by phone or WhatsApp, rather than bluffing. The point is not to replace the conversation with a person. It is to make sure the customer who has a question at eleven at night gets an answer at eleven at night.
Why we built ours without a per-message bill
Assistants built on a paid AI model carry a running cost that rises with every conversation. For a small business that is an awkward shape: the busier the site gets, the bigger the bill, and a quiet month and a busy month cost very different amounts for the same feature. Haswell Chat has no AI subscription behind it, so it costs the same whether ten people use it or a thousand.
There is a second reason, and it matters as much as the cost. An assistant that answers only from what you have told it will not improvise a price, invent a policy or promise an appointment slot that does not exist. The trade-off is honest and worth stating: it will not hold an open-ended conversation about anything at all. It answers your questions, from your content, and passes the rest to you.
How to tell whether it is working
Read what people ask it. The transcript of a site assistant is the most direct record you will ever get of what your website failed to answer on its own. Every question that comes up repeatedly is a sentence missing from a service page, and folding those answers back into the pages makes the whole site better, not just the chat.
Measure it by questions that turned into bookings, not by how many conversations it had. A busy assistant on a site that answers nothing is a symptom, not a success. The goal is fewer questions needing to be asked at all, and a fast, honest answer to the ones that remain.
ANCHOR CASE STUDY Keystone Tutoring — moving the whole decision onto the page