Turn your FAQs into a chatbot that answers in plain words
Written by the Allinaa team · Updated
Most websites already have an FAQ page. Few visitors read it. They type their question into a search box, or into a chat, in their own words. An FAQ chatbot takes the answers you already wrote and gives them back in conversation: one question, one short answer, with a clarifying question when the request is vague.
Static FAQ page vs. conversational answers
| FAQ page | Conversational answers | |
|---|---|---|
| How visitors find the answer | Scroll and scan your wording | Ask in their own words |
| Questions that combine two facts | The visitor has to put them together | The assistant combines them, for example delivery area and delivery days |
| Vague questions | No help | One short clarifying question |
| Questions you never wrote down | Silent | Says it doesn't know and offers to pass the question on |
Keep your FAQ page anyway. It helps search engines and people who prefer to read, and the assistant can draw on it.
Finding your real FAQs: inbox, phone notes, reviews
The questions on most FAQ pages were written by the business. The questions customers actually ask are often different. Spend a week collecting them:
- Your email inbox. Search for question marks in messages from new customers, and note the questions that keep coming back.
- Phone notes. Keep a tally sheet next to the phone. After a few days, the top ten are obvious.
- Reviews and complaints. Misunderstandings in reviews ("I didn't know parking was extra") are questions nobody answered in time.
- Staff. Ask whoever answers the phone which question they are tired of hearing.
Write each answer the way you'd say it on the phone. Then add the exception, because that is where chat answers go wrong: "We deliver Monday to Saturday. No Sunday deliveries, including holiday weekends."
Approved information only
The Allinaa assistant answers only from the business information you approve. The setup wizard can draft that information from up to 10 pages of your website, including an existing FAQ page. The draft uses only facts found on those pages and includes no prices that aren't written there. It is a draft: nothing is used until you have read it, edited it and pressed "Use this". The AI can still get a fact wrong, so read the draft carefully.
A few writing habits make answers more reliable:
- One fact per sentence, without marketing language.
- Names, prices and phone numbers written exactly as they should be quoted.
- Explicit "we don't" statements, which prevent confident guesses.
For a full method, see Writing chatbot knowledge.
When the answer isn't there: saying so and offering a form
When a question isn't covered, the assistant is instructed to say so naturally rather than guess, to offer to pass the question to your team, and to mark it as unanswered. The visitor can then send the question through the request form, with consent and a contact method, and it lands in your inquiry inbox. Each month, the performance report lists the questions the assistant couldn't answer. That list is a ready-made to-do list for your next knowledge update.
Correcting a wrong answer
AI answers can be wrong even with good knowledge, so a wrong answer is fixed through a correction request that a person reviews; nothing is applied automatically, and past conversations are never rewritten. The full workflow is in chatbot accuracy.
Illustrative example
A bakery's knowledge contains: "Gluten-free cakes are available to order with 5 days' notice. They are made in a kitchen that also handles wheat, so they are not suitable for people with celiac disease." The conversation goes like this:
Illustrative example, not a real customer conversation.
Visitor: do u do gluten free birthday cakes
Assistant: Yes, gluten-free cakes can be ordered with 5 days' notice. Please note they're made in a kitchen that also handles wheat, so they aren't suitable for people with celiac disease.
Visitor: ok and are they nut free too?
Assistant: I don't have confirmed information about nuts, so I don't want to guess. I can pass your question to the team. Would you like to send it with the request form?
The second answer is the important one. A missing allergen fact becomes a question for a person, and the next knowledge update can close the gap. If your FAQs reach into support topics, see Support for existing customers. Price questions need extra care; see Answering price questions.
Questions and answers
How many FAQs do I need before going live?
There is no fixed number. Start with the questions you hear every week and the facts behind them, such as hours, area, services and policies, then add to them from the unanswered-questions list each month.
Can I reuse my existing FAQ page?
Yes. The setup wizard can read it along with other pages of your website and draft the knowledge from it. You review and edit the draft before it is used.
Does the assistant learn from conversations by itself?
No. The knowledge changes only when a new version is approved. Conversations show you what to add, but nothing is learned or applied automatically.
What if my FAQ page and my policy page disagree?
Fix the source first. The assistant can only be as consistent as the information you approve, so remove the outdated version from both your site and the knowledge.