How to Write a Chatbot FAQ Page, Pricing and Policy Pages That Answer Well

An AI chatbot is only as good as the pages it reads. A clear chatbot FAQ page, a pricing page with plain numbers, and policies written in short sentences make the difference between a helpful answer and a vague one. This guide shows you how to write those pages so both visitors and your chatbot can find what they need.

Why your pages decide your answers

Talkwyn answers business questions only from your own published content. It does not make up prices or policies. When it cannot find an answer, it says so and offers to have your team follow up.

That is a good thing, but it means gaps in your pages show up as gaps in your chatbot. If your refund rules live only in your head, the chatbot cannot share them. If your prices are inside an image, it may not see them. The fix is not a smarter chatbot. It is clearer pages.

The good news: pages that work for a chatbot also work for people. Short sentences, clear headings, and one answer per question help everyone.

How to write a chatbot FAQ page

A FAQ page is often the fastest way to improve your chatbot. Here is how to build one that works:

1. Start from real questions. Go through your email, phone notes, and messages. Write down the questions people actually ask, in their words.
2. Use the question as the heading. “Do you deliver on weekends?” is better than “Delivery”. It matches how visitors type.
3. Answer in the first sentence. Start with yes, no, or the number. Add detail after.
4. Keep each answer to one topic. If an answer covers delivery and returns, split it into two questions.
5. Link to the full page. If a longer page covers the topic, link to it. The chatbot shows source links under its answers, so visitors can read more.

An example of a weak and a strong answer

Weak: “We aim to be flexible with our customers and will always try to find a solution that works.” This does not answer anything.

Strong: “Yes, you can cancel up to 24 hours before your appointment at no charge. Later cancellations are charged in full.” This is an example policy for illustration. Write your own real rules in the same direct style.

How to write a pricing page

Price questions are some of the most common questions a chatbot gets. Make them easy to answer:

• Write prices as text, not only in images or graphics.
• Say what is included and what costs extra.
• Name the currency and whether taxes are included.
• If prices vary, say what they depend on. “From $80, depending on room size” (an example) is far more useful than “Contact us for a quote”.
• Keep one price in one place. If the same price appears on several pages, make sure they all match after every change.

If you sell with WooCommerce, the scan reads product prices, stock status, and attributes directly, so keep those fields filled in. Our post on questions shoppers ask a WooCommerce chatbot covers store pages in detail.

How to write policy pages

Returns, refunds, shipping, cancellations, and booking rules are where vague answers cause the most trouble. Write them like this:

• Use one page per policy, with a clear title like “Returns and refunds”.
• Put the main rule first: the time limit, the condition, and what the customer gets.
• List exceptions as bullets so they are easy to spot.
• Use numbers and dates instead of words like “soon” or “a while”.
• Write how to start the process: who to contact and what to include.

Keep the legal wording if you need it, but add a short plain summary at the top. Visitors and chatbots both read the summary first.

Write the exceptions down

Most policy questions are really about exceptions. “Can I return a sale item?” “Do you refund custom orders?” “What if the parcel arrives damaged?” If your policy page only covers the normal case, the chatbot has nothing to say about the edge cases, and it will tell the visitor it does not know. That is honest, but it sends the question back to your inbox. List the exceptions you handle often, with the rule for each.

Structure that helps any chatbot

• Use real headings, not bold text styled to look like headings.
• Keep paragraphs short. Two to four sentences each.
• Avoid hiding key facts in tabs, sliders, or PDFs when a plain section on the page would do.
• Publish what you want answered. The scan reads published pages, posts, products, menus, custom fields, and Elementor content. It never reads drafts.
• Update the page, not the chatbot. When you edit a page, Talkwyn keeps its index up to date.

The knowledge base features page explains what the scan reads and how source links work.

Keep pages current after launch

Pages drift. A price changes, a new service is added, holiday hours come and go. Each of those is a chance for an old answer to stay on your site. A few habits help:

• When you change a price or policy, search your site for the old value and update every page that mentions it.
• Add seasonal details, like holiday hours, to a single page and remove them when the season ends.
• Put a short “last updated” line on policy pages so your team knows when they were last checked.
• Read the questions visitors ask in chat every few weeks. Repeated questions without a good answer show you which page to write next.

This is the same work you would do for visitors reading your site. The chatbot just makes the gaps easier to see.

Test your pages with real questions

Once your pages are ready, ask the chatbot the questions from your list. For each answer, check three things: Is it correct? Does the source link point to the right page? Would a customer understand it?

When an answer is wrong or missing, fix the page and ask again. Our chatbot test plan walks through this step by step.

Chatbot FAQ page questions