FAQ vs knowledge base comes down to depth. An FAQ is one short page of the questions customers ask most. A knowledge base is a searchable library of structured articles with the detail and exceptions behind them. Most online stores need both: the FAQ as the quick entry point, the knowledge base as the source of the full rules.
For a store, the FAQ is the list shoppers scan before they buy or write in, and the knowledge base is what your team and your bots work from. Below we cover what each is for, where each falls short, what they cost and how to write an FAQ page that works.
What are an FAQ and a knowledge base?
An FAQ is a page, or a section of one, listing the questions customers ask most, each with a short answer. A knowledge base is a searchable library of structured articles, organised into categories and sections, that explains policies, products and processes in depth for customers, agents and AI. Knowledge base vs FAQ is a question of depth, not of format.
What is an FAQ?
An FAQ is the short list of frequent questions. The Nielsen Norman Group (NN/g) calls it a mature information format that originated in 1982, in a 2014 article. It is now also read by machines: Shopify’s free Knowledge Base app lets merchants view and customise the FAQs that AI shopping agents use to answer questions about their store. Those FAQs are not shown on the storefront. For more on that app, see our piece on AI knowledge tools.
What is a knowledge base?
A knowledge base is the organisation’s official content, kept in one searchable place. In the Zendesk help centre, for example, categories are the top-level containers, sections hold related articles and articles are the content items. It can face customers, face your own team, or both. Our guide to the knowledge base covers the types and how to build one.
FAQ vs knowledge base: what is each built for?
An FAQ is built for speed on predictable questions such as delivery times, the returns window, payment options and sizing. A knowledge base is built for depth and reuse: full policies, step-by-step guides and exceptions, read by customers searching, by agents answering tickets and by bots that quote it.
FAQ: the quick answers
NN/g notes that people often have questions before they can buy, and that answering the bulk of them systematically on the web can pay off. An FAQ gives that decision support: pre-sale reassurance plus the top post-purchase questions, without making anyone open a ticket.
Knowledge base: the single source of truth
Agents reuse knowledge base articles in their replies. Knowledge-Centered Service (KCS®) puts it as “search early, search often”, so a request already solved is not solved twice. Chatbots and AI agents retrieve from it too; our post on the knowledge base chatbot covers that. KCS® is a service mark of the Consortium for Service Innovation™.
On Shopify, store policies (returns and refunds, privacy, terms of service, shipping, legal notice, contact information and subscriptions) are automatically linked in the checkout footer once you add them. The FAQ and the knowledge base must repeat the same rule, not a different version of it.
Where does each fall short?
An FAQ falls short when it grows into a dumping ground, carries made-up questions or gives a generic answer to a question that depends on the order. A knowledge base falls short when nobody owns it, when it drifts from your store policies, or when customers cannot find the article because it uses your words, not theirs.
Where an FAQ falls short
Made-up questions are the classic failure: NN/g put them seventh on its top-10 web-design mistakes in 2002. Long FAQs also get hard to read unless they are chunked by topic. Answers are generic, so exceptions such as a late parcel, a damaged item or a different market end up as tickets anyway. The SEO payoff is smaller too: since August 2023, Google shows FAQ rich results only for well-known, authoritative government and health websites.
Where a knowledge base falls short
Upkeep is the first problem. Articles go stale unless someone owns them, and KCS® answers with “reuse is review”: whoever uses an article is responsible for it and should flag it or fix it. The second is vocabulary. NN/g notes that your vocabulary and your users’ probably talk past each other, which is why KCS® captures the requestor’s own words. The third is cost: depth takes time to write and to translate for each market.
Where both fall short
Both are static text. They can say what the returns rule is, but not whether this order is inside the window, and they cannot start the return. A shopper asking “where is my parcel?” or “can I still send this back?” needs live order data and a rule applied to it.
How do an FAQ and a knowledge base compare?
The FAQ wins on speed and simplicity. The knowledge base wins on depth, search and reuse. The table below is our own analysis of how the two differ for an online store, not a sourced statistic.
| Criterion | FAQ | Knowledge base |
|---|---|---|
| What it is | One page of top questions | A library of articles in categories and sections |
| Best for | Predictable, short answers | Detail, steps and exceptions |
| Typical length | Short answers, one screen each | As long as the topic needs |
| Who reads it | Shoppers before buying or writing in; AI shopping agents via Shopify’s Knowledge Base app | Shoppers who search, your agents, chatbots and AI agents |
| Where it lives | A page on your store | The help centre in your help desk, or a standalone tool |
| Search | Scan or browser find | Full search, related articles |
| Who maintains it | One owner, light upkeep | Owners per section, review dates, flag it or fix it |
| Risk when wrong | A generic answer creates a ticket | A wrong article is reused by agents and bots |
| Can it read the order or act? | No | No |
The two work best as a hybrid. NN/g advises that for longer FAQs a list of questions leading to answer pages works best. Our version of that: link each FAQ answer to the knowledge base article or store policy that owns the rule, so there is one source per rule. For where self-help fits in the wider mix, see self-service.
What do an FAQ and a knowledge base cost?
The software is often free or already paid for. The real cost is writing time and upkeep. An FAQ page is a page on your store. Help desks such as Zendesk and Gorgias include a help centre in their plans, so the cost that grows is ownership: reviewing, translating and keeping every article consistent with your store policies.
On tooling, Gorgias says its Help Center is “available with all Gorgias plans at no extra cost”, Zendesk lists its help centre on every Suite plan, and Shopify’s Knowledge Base app is free. We quote no prices here; check each vendor’s current plan page.
| Cost layer | FAQ | Knowledge base |
|---|---|---|
| Software | A store page or theme section | Usually included in your help desk; standalone tools exist |
| First write | Small: one page of top questions | Large: an article per topic |
| Structure | One list, grouped by topic | Categories, sections, templates |
| Upkeep | Re-check when a policy changes | Owners, review dates, flag it or fix it |
| Languages and markets | One page per language | Every article per language |
| Hidden cost | Tickets from generic answers | Stale articles reused by agents and bots |
To see whether either is cutting tickets, track the right support metrics. KCS® measures link rate and link accuracy, and recommends link rates above 60% and link accuracy above 90%.
Which should you choose?
Start with an FAQ if you are a small store with a handful of repeat questions. Add a knowledge base once your policies have exceptions, you sell in several markets, or a team and a chatbot need one source. Most growing stores run both, with the FAQ linking into the knowledge base.
Choose an FAQ if: you have a small catalogue, a few predictable questions, one market and one person answering email.
Choose a knowledge base if: you have several agents, several markets or languages, policies with exceptions, or a chatbot or AI agent that needs a source.
| Situation (examples) | Start with | Why |
|---|---|---|
| New store, about 20 questions a week | FAQ | A few repeat questions need a quick answer, not a library |
| Two markets, several agents | Both | Agents need one source, shoppers need a fast entry point |
| Chatbot on the site | Knowledge base | It is the source the bot quotes |
| A question about one order | Neither | It needs live data and a rule applied to it |
That last row is the limit described above: order tracking and returns depend on the order and need an action, not an explanation.
How do you write a customer FAQ page?
Build a customer FAQ from your tickets, not from guesses. Take the questions customers ask most, write each in their words, answer in the first sentence, link to the policy or article that owns the detail, group by topic, and give the page an owner who re-checks it whenever a policy changes.
- Pull the questions from real tickets and chats. KCS® says knowledge is a by-product of interaction, and NN/g says questions should echo the real concerns people contact you about.
- Write each question the way customers say it. Use their vocabulary and phrasing, as NN/g and KCS® both advise.
- Answer first, keep it short, then link. Point to the full article or Shopify store policy so there is one source per rule.
- Group by topic: orders, delivery, returns, payment, product care. Readers can then rule out whole sections quickly.
- Give it an owner. Re-check the page when a policy changes, and flag it or fix it.
- Add the same answers to Shopify’s Knowledge Base app, so AI shopping agents have your answers to work from.
Here are six FAQ questions for an online store, written in customers’ words:
- When will my order arrive?
- Can I change my delivery address?
- How do I return something?
- When do I get my refund?
- Do you ship to my country?
- Which size should I take?
On structured data: FAQPage markup no longer earns a rich result for most stores, but Google says there is no need to remove it. Write the FAQ for customers, not for the rich result.
Where does Engaige fit?
Engaige (that’s us) isn’t an FAQ or a knowledge base. It is the e-commerce-native AI support agent that plugs into the help desk you already run, and it works alongside both. It reads your storefront and any docs you add, combines them with live Shopify data and follows policies set up with Engaige AI. At Otrium, Engaige resolves 60% of 120,000 annual tickets end to end.
The angle that matters is policies, not static text. An FAQ says what the returns rule is. A policy tells the agent how to reason about this order, what process to follow and when it may act. The policy in the screenshot checks stock, creates a free reshipment and leaves a note for the warehouse.
Engaige AI drafts your first policies from the integrations you enable, so you do not start from a blank page, shows which policies it used and lets you test every policy before launch. No decision trees, no prompt engineers.
Engaige is a flat monthly fee tied to a ticket volume, predictable as you scale, so you know its cost per ticket in advance and can set it against what a person costs per ticket on the questions your FAQ does not settle; our ROI guide shows the sum.
You decide, step by step, what the agent may do on its own and where a person checks first. That is policy-governed control over how it reasons, what process it follows and when it may act.
Scenario
The customer asks about a delivery address.
Instructions
Read the order with Get order , then take the branch that matches.
Get order Scenario
The order has not been picked yet.
Instructions
Move it with Change picqer shipping address .
Change picqer shipping address Scenario
The parcel has already left the warehouse.
Instructions
Say it cannot be redirected, then offer Process refund .
Otrium’s Head of Operations puts the control point this way.
Engaige offered control, flexibility, and the ability to really incorporate AI in a more human way.
You can go live in Agent Assist in hours, where Engaige drafts replies and suggested actions inside your help desk and nothing closes without a human. Every reply your team sends becomes training data, and Engaige AI proposes policy changes that you approve. At HelloPrint, 80% of tickets are automated, with a 90% faster first response.
Engaige proved to be invaluable. Their hands-on support during the implementation phase resulted in significant improvements to our automated resolution rate and CSAT.
Then flip ticket types to autonomous one at a time. Brands that move quickly reach autonomy in about a week, and Engaige automates up to 90% of supported tickets. Autonomous from day one is also supported. Keep your helpdesk. Replace the AI. The full picture is in the guide to running an e-commerce support team; to see it on your own policies, book a demo.
Frequently asked questions
What is the difference between an FAQ and a knowledge base?
An FAQ answers the most common questions in a line or two on one page. A knowledge base is a searchable library of structured articles with the detail and exceptions.
Do I need both an FAQ and a knowledge base?
Most growing stores do. The FAQ is the quick entry point, and each answer links to the article or store policy that owns the rule.
Is an FAQ page part of a knowledge base?
It can be. Many help centres open with an FAQ-style list of top questions that link into full articles.
How many questions should a customer FAQ have?
As many as your tickets show are asked often, grouped by topic. Do not invent questions to fill the page.
Does an FAQ page still help SEO?
FAQ rich results have been limited to authoritative government and health sites since August 2023. The page still answers shoppers and AI shopping agents, and Google says there is no need to remove FAQPage markup.
How do you keep a knowledge base up to date?
Give every article an owner, re-check it when a policy changes, and have agents flag or fix what they reuse. KCS® calls this “reuse is review”.
Can an AI agent replace my FAQ and knowledge base?
No. An AI support agent like Engaige reads them as sources, alongside live order data. Engaige is built for resolution: it applies your policies to the order in front of it.
How is a policy different from a knowledge base article?
An article explains the rule to a person. A policy in Engaige tells the agent how to reason, what process to follow and when it may act on an order, and you can test it before launch.
