Somebody called this morning to ask whether you service past the county line. Somebody else asked the same thing yesterday, and your newest hire asked a version of it last week. Each time, the answer came out of your head and left nothing behind.
A repeated question is a missing document
Every question asked more than a handful of times is evidence of the same underlying fact: the answer exists in one person's head and nowhere else. That carries two costs. The obvious one is interruption — three minutes per answer, plus the cost of dropping whatever the answerer was doing, forty times over. The quieter one is fragility. An answer that lives in a person leaves with the person. The tech who knows which warranty covers what, the office manager who knows how returns actually run, the owner who knows exactly why the price differs north of the loop — all of it walks out the door on their last day, or just on their day off.
The fortieth answering produces nothing the thirty-ninth didn't. That is the tell: repetition without accumulation.
Start with a log, not with software
Before anything gets built, run a two-week experiment that costs nothing. Everyone who answers questions — front desk, dispatcher, foreman, you — keeps a tally. A shared note, a whiteboard by the phone, a legal pad. Each question asked gets a mark; a new question gets a new line. Two weeks later you have a ranked list of what people actually ask, and it will not match what you would have guessed. Owners are reliably wrong about their own top ten, because the questions that annoy them most are not the ones asked most often.
That list — the top-questions log — is the artifact everything else on this page depends on. It decides what gets written, in what order, and what should never be automated at all.
Answer once, with a citation
Take the top question and write the answer once, properly. Not a chatty FAQ line — the real thing: the coverage map with the boundary actually drawn on it, the warranty table with the model years, the enrollment checklist with the prerequisites listed, the returns procedure as it really runs. Put it at a stable address, on your site or in the internal handbook.
The fortieth phone explanation now becomes a sentence and a link: "Short answer for your address is yes — here's the coverage map." The link does what a spoken answer cannot. It is identical every time, and it survives the call — the customer can forward it to a spouse or a business partner without translating it. The spoken version varies with who answers and how their day is going; the written version is the one you actually approved. Deep-link to the exact section, not the homepage. A link that makes someone hunt is a question generator, not an answer.
The triage line
The log sorts into two piles, and the sorting is the judgment call worth getting right. Page-worthy questions are factual, stable, and identical for every asker: hours, coverage area, warranty terms, what a service includes, lead times, prerequisites, what to bring on the first day. Human-worthy questions are anything involving negotiation, judgment, or an objection dressed as a question. "How much for a roof?" is not a FAQ — it is the opening of a sale, and a page that tries to settle it with a number does damage a person would never do. The working rule: if the correct answer depends on who is asking, it goes to a human; if it is the same for everyone, it goes on a page. One more line worth drawing: an upset customer is never page-worthy, whatever they asked.
If you put an assistant in front of the answers
Once the answers exist as real documents, you can put retrieval in front of them — a site search that understands "do y'all come out to Shallowater" should surface the coverage page, or an assistant that composes its answer from your documents. The requirement that matters is the citation: the system should show which page, and which section, it answered from. An answer with a citation can be checked and corrected, and trust accumulates. An answer produced from a model's general knowledge is a guess wearing confidence, and one confidently wrong warranty answer costs more than the forty phone calls ever did. If a system cannot point to the paragraph it drew from, it should not be talking to your customers. The documents also have to be worth pointing at — a price book that exists as a photo of a coffee-stained printout needs fixing before any software touches it.
What a written answer can't do
A page goes stale the moment the thing it describes changes, and a stale page is worse than none — it answers wrongly, with authority. Every page needs an owner and a review date, or the system rots quietly. Written answers also do not help the caller who wants to be heard rather than informed; that is a conversation, and it should stay one. And documentation is not training. A tech who looks up the same torque spec every week has a learning gap the document is papering over — the page removes the interruption, not the need to know the trade.
The log outlives the launch
After the pages exist, keep logging — specifically, whatever the search or assistant failed to answer. Those misses are the writing queue, already ranked by demand. The system becomes self-directing: what customers and staff actually ask determines what gets written next, instead of someone guessing at an FAQ page in one afternoon three years ago and never opening the file again.
Where to start
Put a tally sheet next to every phone and keep it for ten working days. Rank the results. The top three questions usually cover half the marks. Write those three pages first — properly, with the map and the table — and watch what happens to the phone.