Short answer: Do not guess and do not stall. Tell the customer what you can answer now, explain exactly what is needed to answer the rest, capture their details, and give a specific commitment about when they will hear back. Uncertainty handled well is not a lost sale.
Every service business has questions it genuinely cannot answer on the spot. How much will it cost? Can you do it before Friday? Will it work with my setup? Is my situation covered?
The instinct is either to give a vague number that turns into a difficult conversation later, or to say "we would need to see it" and let the customer drift away. Both lose work.
Sort the questions into three buckets
Before you design a process, be clear about why you cannot answer.
Bucket one: you can answer but the information is scattered. Price ranges, service areas, opening hours, what a service includes, how long it takes. These feel unanswerable because nobody has written them down in one place, not because they are genuinely unknowable.
Bucket two: you need information from the customer. How big is the space, what model is it, how many people, what condition is it in. Answerable, but only after a couple of questions.
Bucket three: you genuinely need a human, a visit or a specialist. Anything with liability attached, anything with real variance, anything where a wrong answer costs you money.
Most businesses treat all three as bucket three. That is where the losses come from, because bucket one and two are the majority of enquiries.
Fix bucket one by writing things down
If a question comes up repeatedly, the answer belongs on your website in plain language. Ranges rather than exact figures are fine. "Most kitchen jobs land between X and Y depending on size and finish" is far more useful to a customer than silence.
This has a compounding benefit if you run an AI chat widget. Clerkzo trains by crawling your own site, so anything you publish becomes something the widget can answer at 11pm without anyone on your team being awake. If you never write it down, the widget cannot help, and neither can a new member of staff.
The corrections loop matters here too. When an answer comes out slightly wrong or out of date, you correct it once and it stays corrected.
Fix bucket two by asking, not guessing
Two or three questions usually converts an unanswerable question into an answerable one. What kind of property is it? How many rooms? Is it a repair or a replacement?
This is what a conversation does better than a form. A form has to ask everyone everything. A conversation asks what is relevant based on the last answer. Whether it is a person on the phone or an AI chat widget on your site, the pattern is the same: narrow the question until you can either answer it or explain precisely what is still missing.
Even when the answer still needs a human, you have now collected the details that make the callback fast and useful.
For bucket three, be specific about the unknown
The worst response to a genuinely open question is a vague one. "It depends" tells the customer nothing and reads as evasion.
The good version has three parts:
- What you can say now. "For a job like this we are usually in this range."
- What is missing and why. "The price depends on whether the existing wiring can be reused, which needs eyes on it."
- What happens next, with a time. "I will get Sam to call you before 11am tomorrow to book a look."
That is not a failure to answer. It is a professional answer to a question that does not have a simple one, and customers respond to it well.
Never let an unanswered question end the conversation
The unforgivable outcome is that someone asks something hard and simply leaves. Whatever the question, the exchange should end with their details captured and a next step agreed.
That is the core job of lead capture on a website. An AI chat widget should be able to say "that one needs a human, let me take your details and get someone to call you", collect them conversationally or with an in-chat form including preferred time and service type, and deliver the whole thing to your team by email, webhook or Telegram. The enquiry lands in the leads inbox and moves through New, Contacted, Qualified and Won or Lost so nothing goes quiet.
Guardrails matter more than coverage
There is a temptation to make an automated system answer everything. Resist it. An AI chat widget that confidently invents a price or promises a date you cannot meet costs you far more than one that says "I do not want to guess on that, let me get someone to confirm."
Guardrails keep the widget inside what your site actually says. Human handoff routes anything outside that to a person. Between them, you get broad coverage on the easy questions and a safe exit on the hard ones, which is exactly the shape you want.
Set a callback promise you will keep
The difference between a captured enquiry and a won job is usually the callback. Give a specific window rather than "soon", and make sure it lands with someone who will act on it.
Notifications are the plumbing here. An enquiry that arrives in an inbox nobody watches is the same as an enquiry you never received. Route them somewhere the team already looks, whether that is email, a webhook into your own tools, or Telegram.
If most of these questions arrive overnight, after-hours answering covers holding them properly until morning.
Frequently asked questions
Should I publish prices if every job is different?
Publish ranges and explain what moves the number. Silence on price does not protect you; it just sends people to a competitor who was willing to be approximate.
What if the AI gives a wrong answer?
Guardrails keep it inside your published content, and the corrections loop lets you fix a wrong answer permanently. Anything genuinely uncertain should route to a human rather than get a guess.
Is it bad to say I do not know?
Not if you follow it with what is missing and when they will hear back. Customers distrust false confidence far more than honest uncertainty.
Can a chat widget book the follow-up call itself?
Clerkzo captures the request, including the customer's preferred time, and delivers it to your team. It does not write to your calendar. Your team confirms the callback using whatever scheduler you already use.
How quickly should I follow up on a question I could not answer?
Give a specific window and beat it. Same day is the standard. The customer is comparing you to whoever replies first, not to your ideal timeline. See pricing if you are weighing what that coverage costs.