Chatbot vs FAQ page: which questions each one answers best

There is an FAQ page — and customers still write in

Almost every company's website has an FAQ page: delivery, payment, returns, warranty. And in almost every company customers still send those same questions to Instagram, WhatsApp and the call centre. Management usually reacts in one of two ways: «let's write a better FAQ» or «let's drop the FAQ and build a chatbot». Both are half-solutions.

This article sets out the chatbot vs FAQ difference in practical terms: the FAQ's strengths and weaknesses, what a conversation does differently, which question suits which format, a decision matrix and how the two work together. Why questions keep repeating is a separate diagnosis; here the subject is choosing the format.

What an FAQ does well

• The same approved text for everyone — ideal for legal and rule-based information
• Visible in search: someone searching «company X return policy» finds the answer directly
• Customers read it themselves, at their own pace — good for those who do not want to talk to anyone
• Cheap to maintain: one page, one owner
• Easy to compare: all the terms in one place

Proposals to drop the FAQ ignore these strengths — above all its visibility in search.

Where an FAQ falls short

1. 1The customer asks in different wordsThe FAQ has a heading «Delivery terms»; the customer asks «will it reach Ganja tomorrow?». The answer is on the page, but the customer does not find it.
2. 2The answer depends on context«Can I return it?» depends on the product, the purchase date, whether it was on sale. The FAQ states the general rule; the customer asks about their own case.
3. 3There is no next stepThe FAQ answers but does not act: it does not take a return request, book a visit or show an order's status.
4. 4Getting to the pageA customer writing on Instagram will not go to the website to look for the FAQ. They expect the answer where they asked.

What a conversation does differently

A chatbot uses the same information, but does three things an FAQ cannot.

• It understands the question in the customer's words and finds the matching answer
• With one clarifying question it fits the answer to the customer's case: «Was it bought on sale?»
• It takes the next step: accepts the request, collects details, hands over to an agent
• It works on the channel the customer wrote on — Instagram, WhatsApp, the website

One question, two formats

1. 1In the FAQ«Returns: unused items can be returned within 14 days with the receipt and packaging. Sale items are returned only for manufacturing defects.»
2. 2In chat — customer«The shirt I bought on sale last week is too small, can I exchange it?»
3. 3In chat — bot«Sale items are usually returned only for defects, but a size exchange is possible in store. Send your order number and I'll check whether your size is available.»

The information is the same. The difference is that the bot applied two rules to the customer's case and moved the conversation towards a solution. Note: «a size exchange is possible» must be written in the knowledge base as well — the bot must not invent it.

Which question suits which format

1. 1An FAQ is enoughThe answer is the same for everyone, customers want to read it themselves, the question is searched for: warranty terms, payment methods, privacy.
2. 2A chatbot is betterThe answer depends on the customer's situation, there is a next step, the customer writes on a messaging channel: where is my order, does this suit me, can I exchange it.
3. 3Both togetherThe rule lives in the FAQ; the chatbot explains it for the specific case and, if needed, takes the request: returns, delivery, appointments.

The joint model: FAQ as source, chatbot as interface

The model that works treats the FAQ and the chatbot not as rivals but as two layers.

• The FAQ and knowledge base are the single source of approved information
• The chatbot answers from that source and works on the customer's channel
• Questions the bot cannot answer go back into the FAQ as new entries
• When FAQ text changes, the bot changes the same day — two separate texts are not maintained

In Vexvon, the FAQ is kept in the knowledge base as its own context type — the knowledge base page shows how that is set up. Who owns the answers and how they are kept current is covered in knowledge management.

What not to lose in search

Chatbot conversations do not appear in search engines. A prospective customer searching «company X delivery time» finds the FAQ page, not the chatbot. So dropping the FAQ can be a loss both in customer service and in search.

• Keep the FAQ page and update it with real questions
• Write answers short, direct and in the customer's words
• Keep the chat widget open on the FAQ page too — so someone who reads and does not find it can write at once

How to rewrite an FAQ for chat

An existing FAQ is usually written for a page: long paragraphs, general headings, three rules in one answer. Before giving it to the bot, rework it in four steps.

1. 1One question, one answerSplit combined entries like «Delivery and payment». The bot finds short, single-topic fragments more precisely.
2. 2The customer's wordsAdd two or three question variants from real messages to each answer: «how many days to Ganja?», «do you ship to the regions?».
3. 3Exceptions on their ownSale items, special orders, the regions — do not hide an exception inside the general rule; write it as its own entry.
4. 4The next stepEnd each answer with what can be done: «For a return, send your order number» — the bot continues the conversation from there.

Common mistakes

• Building the bot and no longer updating the FAQ page — the two sources soon drift apart
• Loading the FAQ into the bot unchecked — old terms come back to life in the bot
• Writing the bot's answer differently from the FAQ — the customer sees two different rules
• Hiding the chat widget on the FAQ page

What to measure

• The bot's full-answer rate on FAQ topics
• Questions the bot could not answer that are not in the FAQ either — the list of new entries
• Visitors who open chat after viewing the FAQ page — where the FAQ is not enough
• The fall in FAQ-topic requests reaching agents

Limits

A chatbot cannot rise above the quality of the FAQ. If the rules contradict each other or are out of date, the bot will spread that faster and to more people. For legal text — contract terms, the privacy policy — the bot should not interpret; it should quote word for word and hand over to a person if the question is complex.

Conclusion: the question is not «FAQ or chatbot»

A chatbot does not replace the FAQ; it brings it to where customers write and into their words. The FAQ stays as the approved source and the page visible in search, while the chatbot applies that source to the specific case and takes the next step. When every question the bot cannot answer goes back into the FAQ, the two formats strengthen each other.

We showed how to build a support bot in stages in the customer support chatbot; the rest of the support section is in this category. To adapt your FAQ for the bot together, ask for a demo.

Frequently asked questions

1. 1Can we delete the FAQ page after building a chatbot?We do not recommend it. The FAQ is visible in search and is the approved source the bot answers from.
2. 2Which matters more for a small business?If customers mostly ask by message, the chatbot; if they read on the website, a good FAQ. In most cases, both.
3. 3Can the bot answer a question that is not in the FAQ?Only if the information is in the knowledge base. If not, it should say «I don't know» honestly, hand over to a person, and the question should be added to the FAQ.