The answer you have typed forty times

There is a question your customers ask you constantly. You know the answer so well that you have stopped noticing you know it. You have typed it out, in slightly different words, maybe forty times.

It is nowhere on your website.

This is the most common gap we see, and it is not a failure of effort. It is just what happens when a business grows inside somebody's head faster than it grows onto their website.

Your best help pages are already written

Open your sent folder. Not to organise it, just to look at the last twenty replies you wrote to customers.

You will find the same handful of answers over and over, each one written a little differently depending on how tired you were that day. Somewhere in there is a good version. You wrote it on an afternoon when you had time, and it was clear and complete and kind, and then it went to exactly one person and was never read again.

That is your raw material. You are not starting a documentation project. You are collecting things you have already written and putting them somewhere they can be read more than once.

What makes an answer usable

Most help pages fail in the same five ways. Fixing them takes minutes.

Use the customer's words as the heading. "Do you ship to Canada?" is a better heading than "International logistics". People search with the words they would have used out loud.

Answer in the first sentence. Background first, answer at the bottom, is how internal documents are written. Nobody arrives at a help page wanting context. Say yes or no, then explain.

Be specific. "Usually a few days" is not an answer, it is a shrug. "Two to four working days" is an answer. Vagueness in your writing becomes vagueness in every reply that gets built on it.

Finish the thought. A page that ends with "get in touch for details" has sent the person back to where they started, which is waiting for you. If the answer genuinely depends on something, say what it depends on. "Under two kilograms it is free, above that it is calculated at checkout" is a complete answer even though it has a condition in it.

Keep one answer in one place. If your returns window says thirty days on the FAQ and fourteen days on the product page, someone is going to find the wrong one. Usually the customer. Occasionally at the worst possible moment.

A page that answers the question fully is not written for the software. It is written for the person who was going to ask you anyway.

Where it goes

You do not need a new section of your website for this. Almost every answer already has an obvious home.

If it is about one product, it belongs on that product's page. If it is about delivery or returns, it belongs on the page about delivery and returns. If it is general, the FAQ is fine. The rule is simply to put it where a person would think to look, which happens to be exactly where it gets read.

And if an answer genuinely has no home on your site, you can add it by hand in your dashboard instead. Some things are true and useful and still do not deserve a page.

Ten minutes on a Monday

The reason we keep coming back to this is that it is the only part of the whole thing that needs you.

Every Monday you get a short list of the questions customers asked that your website could not answer, ranked by how often they came up. We wrote about that report in what actually happens in your first week. Most weeks the list is short and slightly boring, which is a good sign.

Pick the top two. Write three sentences each. Put them on the page where they belong. That is the whole ritual, and it takes about ten minutes.

The next person who asks gets the answer immediately, at whatever hour they asked it. The week after, that question falls off the list, and something else takes its place. Over a couple of months the list gets shorter and stranger, until what is left is the genuinely unusual stuff that was always going to need a person.

The unglamorous truth

Writing these pages is not really an AI project. That is the part worth saying plainly.

The pages are better for the customer who reads them at eleven at night instead of writing to you. They are better for the search engine that sends you the next visitor. They are better for whoever you hire next, who currently has to ask you what the return policy is. And they are better for you, because you stop typing the same paragraph one more time.

The agent's job in all of this is small and honest. It reads what you wrote, it answers from it, and when your website has nothing to say it tells the customer so instead of inventing something. We have written about why that matters more than being clever.

Everything good it can do comes from something you took ten minutes to write down once.