Build a Customer FAQ and Knowledge Base From Your Sent Folder
11 min read
You can build a customer FAQ with AI in about an hour, because the answers already exist in your sent folder. This lesson turns them into a public FAQ page and a private knowledge base your team can ask questions.
The cheapest support message is the one a customer didn't need to send. Every time someone finds your parking instructions, your refund window or your holiday hours on their own, that's two minutes you keep. Across a year it's days.
Most small business FAQ pages fail for one reason: the owner guessed what customers ask. You don't have to guess. Chapter 1 gave you the real top ten.
Step 1: mine the questions
If you skipped the inbox sort, do it now. If you've done it, go wider. Pull questions from everywhere customers talk to you:
- Sent email from the last three months
- WhatsApp, Instagram and Facebook messages
- What the person who answers your phone says they hear all day
- Google reviews, where a complaint often hides a question nobody answered
Strip personal details, paste the lot, and ask:
Below are real customer messages to my [TYPE OF BUSINESS].
List every distinct question customers asked, grouped by
topic. Merge questions that mean the same thing and keep the
customer's own wording for each. Count how often each came up.
Show the 20 most frequent first.Keep the customers' wording. People search and scan for the words they use, not the ones you use. If they say "do you do same-day", your heading shouldn't say "expedited service availability".
Step 2: write answers that end the conversation
A good FAQ answer does three things: answers in the first sentence, gives the one detail people ask next, and says what to do if that didn't cover it.
Here is my support brief:
[PASTE BRIEF]
Write FAQ answers for the questions below. Rules:
- First sentence answers the question directly
- 2 to 4 sentences total, plain words, our voice
- Include the follow-up detail a customer would ask next
- Use only facts from my brief and my notes. Where a fact is
missing, write [NEED: what you need] instead of guessing
Questions and my notes:
[PASTE QUESTIONS WITH A FEW WORDS OF NOTES UNDER EACH]The [NEED] markers are the point. They show you where your own policies are fuzzy. If the draft comes back with six of them, you've found six things your team has been answering differently.
For a longer help article with steps and screenshots, use the free Help Doc Writer. For the whole FAQ in one pass, the FAQ & Knowledge Base Builder prompt runs this method end to end.
Step 3: publish it where customers look
| Where | Cost | Good for |
|---|---|---|
| An FAQ page on your own website | $0 | Everyone. It also helps you show up in search |
| tawk.to knowledge base | $0 | A searchable help centre, linked from the chat widget |
| A public Google Doc or Google Sites page | $0 | No website yet, or no one to edit it |
| Pinned post or highlights on Instagram and Facebook | $0 | Businesses whose customers live in DMs |
| WhatsApp Business catalog and quick replies | $0 | Businesses whose customers live in WhatsApp |
Put it on your own site if you can. Each question is a phrase someone types into Google or asks an AI assistant, and a page that answers it plainly has a fair chance of being the result they see. The marketing course covers this in Web Pages That Answer What Customers Actually Search.
Then link the FAQ everywhere a question starts: your email signature, your auto-replies, your Google Business Profile, the top of your contact page.
Step 4: a private answer notebook for your team
Your public FAQ covers what customers ask. Your team needs more: supplier lead times, the warranty terms, what to do when the card machine fails, the exception you made last spring and why.
Gemini Notebook, the Google tool known as NotebookLM until July 2026, fits this well. You upload your documents and it answers questions using only those documents, with a citation showing where each answer came from. The free plan allows 100 notebooks with 50 sources each and around 50 questions a day, which is plenty for a small shop.
Set it up in fifteen minutes:
- Create a notebook called "Support answers"
- Add your support brief, your policies, your price list, your FAQ, and supplier or warranty PDFs
- Share it with the people who answer customers
- Ask it things the way a new hire would: "A customer wants to return a sale item after three weeks. What's our rule?"
The citation is what makes this safe. A general chatbot guesses from the whole internet. A notebook grounded in your files points to your own page, and if it can't find the answer it says so. Keep customer records out of it, per the last chapter. Policies and procedures only.
Claude Projects and ChatGPT projects can do a similar job if your team already works there.
Where this breaks
An FAQ that's wrong is worse than none, because customers quote it back to you. The day your hours, prices or policies change, the FAQ and the notebook change too. Put one person's name on it. The free Knowledge Base Copilot skill is built for that upkeep: feed it this month's questions and it tells you what to add, fix or retire.
Try it now
Publish five answers this week. Five real questions from your top-ten list, answered in your voice, on a page you can link to. Add the link to your email signature. Then count how many times next week you answer a customer with one line and that link.