How to build a WhatsApp FAQ bot without coding: from a written FAQ to an assistant that answers questions in the customer's own words
A WhatsApp FAQ bot used to mean a menu: press 1 for hours, 2 for prices, 3 for a human. Customers hated it because they do not think in menus. The current version reads the question as written ("u open on sunday ah?") and answers from a FAQ you wrote. Building one needs no code; it needs a good FAQ and four rules.
Quick answer
Write your FAQ as questions in the words customers use, with short factual answers. Load it into an AI agent as knowledge, along with your website and price list. Set four rules in the instructions: answer only from the knowledge, say you are not sure when it is not there, hand over on request and for named topics, and disclose that it is an assistant. Test with twenty real questions from your inbox, then teach it weekly from the questions it could not answer. No developer, no menus, no keywords.
Menu bot or agent
| Menu or keyword bot | AI agent | |
|---|---|---|
| Input | Numbers or exact keywords | Free text, any phrasing, typos, mixed languages |
| Building | Draw a flow of every path | Write the FAQ and rules |
| Off-script question | "I did not understand" | Answers if in knowledge, else says not sure and hands over |
| Maintenance | Edit the flow | Edit a document |
| Booking | Usually a link out | In the chat |
The difference is explained in chatbot vs AI agent. For a small business the agent is simpler to build and far better to use.
Writing the FAQ
The bot is only as good as the FAQ. Use the customer's words as the question ("got parking?" not "Is parking available at our premises?"), answer in one to three sentences with the fact, and include variants for the same question in different languages. Twenty to forty entries cover most businesses. The method is in writing a business FAQ, and the retrieval reason it matters is in how retrieval works.
The four rules
- Answer only from the knowledge base.
- If it is not there, say "I am not sure, let me get someone from the team" and hand over.
- Hand over when the customer asks for a person, and for the topics you name (complaints, medical, payment disputes).
- Say it is an assistant in the first reply.
These belong in the instructions; the full pattern is in writing instructions.
Improving it
Every question the bot could not answer is logged. Once a week, answer the list; each answer becomes knowledge. After a month the not-sure rate drops sharply. That loop is the whole maintenance plan, described in the teach loop.
Frequently asked questions
Can I build a WhatsApp FAQ bot without coding?
Yes. Write the FAQ in customer language, load it as knowledge in an AI agent, set four rules, pair the number, and test.
Do I need a menu or keywords?
No. An AI agent reads the question as written, including typos and mixed languages.
How many FAQ entries do I need?
Twenty to forty cover most small businesses. Add more from the unanswered-questions list weekly.
What happens when someone asks something not in the FAQ?
The bot says it is not sure, hands over to a person, and logs the question for you to teach.
How long does it take?
About 45 minutes including writing the FAQ, then ten minutes a week.
Your FAQ, answering in any wording
Load it, set the rules, pair the number. 7-day free trial.
Sources and further reading
- WhatsApp Business Messaging Policy · opt-in, opt-out and prohibited-use rules every business must follow
- Harvard Business Review, The Short Life of Online Sales Leads (Oldroyd, McElheran, Elkington, 2011) · firms that responded within an hour were about seven times more likely to qualify the lead
ReplyKit is an independent product and is not affiliated with or endorsed by Meta or WhatsApp. This article is general guidance for running a small business, not legal, financial or regulatory advice.