Every support email is a page you never wrote
Customers ask the same questions in emails that they would ask on your site, if your site said it somewhere. The inbox keeps answering the same six questions while the website stays silent, and the pattern is invisible until you stop and count. One quiet hour turns a month of replies into a help section that answers people while you sleep. Here is the method, and none of it requires a plugin.
Step 1: Pull three months of email and count what repeats
Open your mail, search the last ninety days of customer messages, and skim subjects only. Every question that shows up more than three times goes on a list, written the way the customer actually words it, not the way you would. That wording matters later, because the help section should use the customer’s language, not your internal shorthand.
Step 2: Group the list into six buckets
Cluster the repeats into themes: order status, shipping times, returns, sizing, product use, account or payment. Nearly every store lands under six. The clusters are also your page headings, and the biggest cluster gets the answer placed highest.
Step 3: Write each answer in under sixty words
The best help answers read like a calm reply, not documentation. Each one says the direct answer first, then a single supporting detail. Where to say it depends on the question: returns policy belongs on or linked from every product page, shipping times belong in the footer of the checkout, sizing belongs beside the size selector, product-use questions belong on the product page itself under a short “good to know” line. A single help hub page still helps, but answers placed at the moment of decision beat answers behind a menu.
<h3>When will my order arrive?</h3>
<p>Orders leave us within 1 business day and arrive in [X-Y]
business days. Express arrives next day to major centres.</p>Step 4: Ship it on your site this afternoon
If you run WordPress, this is just a page or a few product-page text blocks; no new app required. Shopify stores use the built-in pages and product description fields the same way. Publish the six answers today in whatever form your platform allows, even imperfect, because a plain answer published now outscores a polished one in three weeks. Keep the replies you already send as the source text; customer emails are often better written than anything drafted from scratch.
Step 5: Point every future reply at the page
From tomorrow, when one of the six questions arrives again, send a two-line reply: the direct answer, plus a link to the fuller published version. Copy-paste-ready:
Hi [first_name],
Short answer: [one sentence].
I wrote it up in a bit more detail here: [link]
If that does not cover it, reply to this email.The link does two things. It teaches the customer where to look next time, and it tells Google your site answers these questions, which is how the page starts appearing for the same searches other customers were making before they emailed.
Step 6: Rerun the count in ninety days
Put a calendar note for one quarter out. Count last month’s inbound emails against the original list. The questions that dropped are your savings, made visible. The ones that persist are either not answered clearly enough, written in the wrong spot, or genuinely new, which means the next hour of work has already picked its subject for you.
What the hour buys
Every answer that used to live only in your replies now works on the site, continuously, in your customer’s own words. Writing six honest answers takes roughly an hour, and unlike the inbox, the page never gets tired of the same question.
Want more like this? Join MOKU Club for free. Weekly resources, early access to new guides, and occasional templates you can actually use. Join below.
