Writing the knowledge your agent answers from

The instinct is to hand over the website and consider the job done. It is the wrong starting point, because a website is written for somebody browsing and a caller is not browsing. The person who rings has one question, they have usually already looked at the site, and they are calling precisely because the site did not answer it.

Start instead from a list of what people actually ask on the phone. Get whoever answers to write down every question for a week, verbatim, in the caller’s own words. That list is the specification. Everything below is about turning it into material.

One warning about verbatim: keep the caller’s phrasing, not your industry’s. People do not ring a dental practice and ask about a prophylaxis, they ask how much a cleaning is. An agent that only knows the professional term will not recognise the question it is being asked.

The single most common defect in this material is a page that describes a subject rather than answering a question. A paragraph headed Insurance that explains your philosophy about insurance is useless. The sentence "We take Delta Dental and Cigna. We do not take Aetna, and we can give you a receipt to submit yourself" is the whole job.

The format that works is a question in the caller’s words, then the shortest true answer, then the exception if there is one. Nothing else. Aim for three sentences per item and treat a fourth as a sign that you are answering two questions and should split them.

Every small business has rules with exceptions, and exceptions are where an agent gets you into trouble. The trap is writing the rule and leaving the exception in somebody’s head, because then the agent states the rule confidently to a caller for whom it is wrong.

Write the exception into the same item as the rule, and write the boundary as a condition the agent can actually check with the caller. "Cancellations need twenty four hours notice, and we waive that if you are ill" is not checkable and will be applied inconsistently. "Cancellations need twenty four hours notice. If it is less than that, take their name and number and tell them the studio will call back to sort it out" is checkable, and it routes the judgement to a person, which is where judgement belongs.

That pattern, an explicit rule plus an explicit escalation, is the one to use everywhere you find yourself wanting to write "it depends".

This list matters more than the answers do. For a clinical business it includes anything that could be read as advice or a diagnosis, and usually anything about what a treatment will cost before somebody has been seen. For a law firm it includes anything that could be construed as advice about a specific matter. For most businesses it includes discounts, exceptions to payment terms, and anything about a named individual.

Write these as instructions to refuse and to route, with the words to use. "If someone describes pain or an injury, do not assess it. Say that the practice will need to speak to them, take their name and number, and mark it urgent." An agent given that is safer than one given nothing, because the default when nothing is written is to be helpful, and helpful is the wrong instinct at exactly these moments.

Hours, prices, term dates and staff names change, and a paragraph with a date buried in it is a paragraph that will be wrong in three months and will keep being confidently repeated. Keep anything time-bound in a short, obviously dated block at the top of the material so that the person doing the update can find every stale item in one place.

Better still, connect anything that lives in a system to that system rather than copying it. A schedule that is read live is never stale. A schedule that was pasted in during setup is stale the first time somebody moves a class.

Put a review date in the material itself and treat it as a real task. Ten minutes a month is enough, and the month you skip is the month somebody is told the wrong opening time on a public holiday.

Once it is written, read the list of verbatim questions back at the agent, in the caller’s own words, out loud on the phone rather than typed. Reading them typed hides the two failures that matter, which are mishearing and answering a slightly different question than the one asked.

Mark each one as answered, refused correctly, or wrong. Only the third category needs work. A refusal is a pass, and a page of refusals tells you exactly which material to write next, which is the fastest way to improve the thing that exists.

Then have somebody who does not work for you make five calls. They will ask in words you would never have thought of, which is the entire point.

The first pass is two to three hours for most small businesses, and it is the highest leverage work in the whole project. The week of collecting questions beforehand is passive. After that it is ten minutes a month, plus a proper revisit whenever something structural changes, like a new service or a new location.

A vendor who tells you none of this is required is telling you their product will guess. Guessing is the failure mode that costs a customer rather than a call.