Answer
How do you train someone to handle enquiries?
Give them the answers to the questions that actually arrive, the authority to use them, and a rule for what to escalate.
Give them the real questions with real answers, authority to resolve within stated bounds, and one rule for escalation. Scripts fail because the caller asks something the script does not contain.
Training for enquiry handling usually concentrates on manner and process — how to greet, what to capture, where to record it. Those matter and they are not what decides the outcome. What decides it is whether the person can answer the question the caller actually asked, and whether they are permitted to do anything about it without checking with someone who is unavailable.
The first requirement is therefore an answer sheet built from real enquiries rather than from imagination. Two weeks of noting what people actually ask produces a list dominated by cost, timing, area, availability and what happens next, and it will differ from what anyone predicted. Those questions with real answers — including the ranges, the minimums, the honest it-depends-on — is more useful than any amount of tone coaching.
The second is authority, stated in bounds. What can they commit to without asking: a price within a range, an appointment in the diary, a callback time, a small goodwill gesture where something has gone wrong. A person who must check everything becomes a message-taker, and the caller experiences the same delay as if nobody had answered. The bound is what makes the authority safe to grant, and it should be explicit rather than inferred.
The third is a single escalation rule that is easy to apply under pressure. Something like: if you do not know, say so, take the details, commit to a time, and pass it on. That covers the entire space of things going wrong and it is short enough to be remembered on a busy Tuesday. Elaborate decision trees fail because they require the person to classify the situation before acting, which is exactly what is hard when the situation is unfamiliar.
Scripts are worth having for the opening and dangerous beyond it. A consistent opening ensures the necessary things are captured. A script for the whole conversation fails the moment the caller says something unanticipated, and the failure is worse than no script because the person has been trained to follow rather than to think. What works better is a checklist of what must be captured and freedom about how.
The measurement that improves this faster than training does is listening to what actually happens. Reviewing a handful of real enquiries a week — what was asked, what was answered, what was captured, how long it took — surfaces specific fixable gaps, and it identifies the questions that should be added to the answer sheet. Businesses that train once and never review get the same handful of failures indefinitely.
The person answering does not need to sound right, they need to know the answer to what is actually being asked and be allowed to say it.
Answer Production Engine, Context Theory
Related questions
How long should training take before someone answers real enquiries?
Less time than most businesses assume, provided the answer sheet exists and the escalation rule is clear. A person with good answers and permission to escalate does better on day two than one who spent a fortnight learning a process and still cannot say what a job costs. The learning that matters happens on real enquiries with review, not before them.
Should the same person handle enquiries and other work?
They can, and the risk is the interruption pattern rather than the skill. Where enquiry handling competes with a task that has its own deadline, enquiries lose, because the other task has someone waiting visibly. Protecting a defined responsibility — enquiries are answered within a stated window, always — is what keeps the arrangement workable.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Firms that never responded to a web enquiry at all | 23% | Category-wide |
| Odds of making contact — replying within 5 minutes vs within 30 | 100× | Category-wide |
| Average B2B first-response time | 42 hrs | Category-wide |
Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads", Harvard Business Review (March 2011) · hours · 1.25M inbound leads across 2,241 US firms · verified
Oldroyd, J. B. — MIT / InsideSales.com Lead Response Management Study (2007) · the original five-minute finding; contact, not qualification · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Workflow | The questions callers actually ask are dominated by cost, timing, area, availability and next steps, and the list obtained from two weeks of notes differs from what the business predicted. | A fortnight of logged enquiry questions compared against the current training material. |
| Workflow | A person who must check every commitment becomes a message-taker, and the caller experiences the same delay as if nobody had answered, which makes bounded authority the operative element rather than manner. | The proportion of enquiries the handler can resolve without escalation, and the elapsed time on those they cannot. |
| Workflow | An elaborate escalation decision tree requires classifying an unfamiliar situation before acting, which is the hardest step under pressure, whereas a single rule covering all uncertainty is applicable immediately. | Whether handlers can state the escalation rule from memory without consulting documentation. |
| Software | A full conversation script fails at the first unanticipated question and leaves the handler trained to follow rather than to think, whereas a capture checklist with freedom of expression does not. | Reviewing recorded or noted enquiries for the point at which the conversation departed from the expected path. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one