E-commerce
June 26, 2026
An e-commerce FAQ page can become one of a store's best self-service tools. But only if it answers real customer questions, in the right place, with responses clear enough to avoid a support ticket.
The problem is well-known: many FAQs are written from the brand's perspective. They talk about values, vague policies, and internal procedures, while the customer wants to know how long a refund takes, where to find their tracking, or what to do if the package is stuck.
This article #21 does not replace the Qstomy FAQ page. It provides a writing and optimization method to create an e-commerce FAQ oriented toward support, measurable, and connectable to an AI chatbot.
Summary
Why does an FAQ reduce tickets?
A good FAQ reduces tickets because it intercepts repetitive requests before the contact form: delivery, return, refund, order tracking, payment, client account, invoice.
The right objective
Do not try to explain everything. Seek to reduce the 5 to 8 reasons that saturate support. Shopify points out that a FAQ is a self-service hub where visitors find product and policy information without contacting support (Shopify, FAQ page guide).
The page should therefore be treated as a support tool, not as a decorative page in the footer.
How do I choose which questions to include?
An effective FAQ comes from tickets, not from a marketing brainstorming session.
Export 90 days of tickets, chats, and emails
Group by reason: WISMO, return, delivery, payment, product
Count frequency, handling time, and irritation level
First, keep the questions that are repeated at least three times
Write using the exact words of your customers
Example: if your customers write "when am I refunded?", do not headline it "terms of financial restitution". Write: "When will I receive my refund?"
Add an "action possible without human intervention" column. If the answer only requires a tracking link, a return policy, or an invoice download, it is perfect for the FAQ. If it requires negotiation, a commercial exception, or a fraud check, keep an entry instead that explains when to contact support.
The sorting then becomes very concrete: a frequent and simple question goes to priority FAQ; a rare but costly question becomes an internal support answer; a frequent but sensitive question becomes a short FAQ with guided escalation.
Which categories should be created first?
Delivery: times, fees, carriers, countries, delays
Order tracking: tracking link, blocked status, partial package
Returns: time frame, conditions, fees, portal, exchange
Refund: timing, payment method, exceptions
Payment: failure, invoice, BNPL, declined card
Account: login, password, history
Product: warranty, authenticity, general maintenance
Contact: when to write to support and with what information
Keep product details on product pages or in a dedicated product FAQ. The global FAQ page must remain legible.
How to write a response that avoids a ticket?
Each answer must start with the direct answer, then provide the conditions and the next step.
Simple structure
Short answer in the very first sentence
Timeframe, amount or numerical condition
Link to the action: return portal, tracking, account, contact
Main exception if it avoids a support ticket
Clear escalation if the FAQ is not enough
Example
Instead of "we process returns quickly", write: "You can return your order within 14 days of receipt. Start the request from your customer account. The refund will be processed within 5 to 7 business days after the package is inspected."
Reusable template
For each answer, use this formula: "Yes/no or precise timeframe. Here is the condition. Here is the link or action. If your case is different, contact us with your order number." It forces you to remove branding phrases that do not help the customer move forward.
Keep legal answers in the policy pages, but translate them into customer-friendly language in the FAQ. The FAQ explains what to do; the official policy confirms the full framework.
What UX structure should be used?
An FAQ that reduces tickets must be scannable in a matter of seconds.
Accordions: one question per line, with a short answer underneath
Quick links: the 5 most frequent questions at the top
Search: essential once there are 15 to 20 questions
Categories: delivery, returns, payment, account, contact
Mobile: short accordions and easily clickable buttons
Talk Shop recommends starting from real questions and using an accordion design, with search as soon as the page becomes dense (Talk Shop, Shopify FAQ).
Where should the FAQ be placed in the user journey?
A FAQ hidden in the footer is not enough. It must appear before the ticket is created.
Contact page: frequently asked questions before the form
Order email: direct link to tracking and modification
Return page: terms and steps before requesting
Account space: invoice, tracking, history
Product page: link to delivery and returns
Chatbot: answer from the same database
Example: on the contact page, place the five most viewed questions above the form. Many requests disappear before they are even sent.
On Shopify, also think about system pages: order confirmation, customer account, order status page, and policy pages. A FAQ entry like "can I change my address?" must be visible before shipping, not after the first email reminder.
During peak periods, create temporary blocks. Before Christmas or Black Friday, highlight realistic deadlines, delivery cut-off dates, and extended return policies. These are often preventable seasonal tickets.
How to connect a FAQ and an AI chatbot?
The FAQ must become a source of truth for the chatbot, not a separate content.
Recommended workflow
Draft the FAQ from tickets
Publish validated answers
Connect these contents to the chatbot
Identify unanswered chatbot questions
Update the FAQ and bot weekly at launch
Gorgias indicates that its Help Center and self-service tools can help deflect repetitive tickets, notably WISMO and returns, while feeding the AI with consistent answers (Gorgias Help Center).
What to do for SEO and AI search engines?
The FAQ can be useful for support and visible in search engines, but do not write it solely for SEO.
FAQPage in 2026
Since May 2026, Google no longer shows FAQ rich results in standard results, but FAQPage remains valid markup. You can keep it if it corresponds to visible and useful content.
Good Practice
Mark official questions that are visible on the page with short, factual answers. Avoid fake SEO questions that do not correspond to any customer ticket.
Which KPIs should be monitored?
FAQ Views: by category and by question
Contact after FAQ: reading then ticket on the same subject
Tickets by reason: before and after publication
Search with no results: missing questions
Useful clicks: return portal, tracking, customer account
Feedback: helpful or not helpful on each response
Shopify advises tracking tickets received on the same questions after going live and calculating the cost per ticket to estimate self-service savings.
Simple reading of the figures
If an answer is viewed a lot but followed by many tickets, it is visible but insufficient. If a question continues to arise without any FAQ views, it is poorly placed or poorly named. If internal searches yield no results for "invoice", create an entry with that exact word, even if your team refers to it as "proof of purchase".
Measure by reason, not just in overall volume. A 30% drop in return tickets can be masked by a temporary increase in carrier delays.
Which errors are preventing the FAQ from working?
Jargon: questions formulated like the team, not like the customer
Vague answers: no timeframe, no link, no next step
Hidden page: FAQ accessible only from the footer
Obsolete content: old return policy timeframe or deleted carrier
Too many questions: 50 unprioritized entries right from the start
Divergent sources: FAQ, macros, and chatbot say different things
The simplest fix: reread the last ten tickets on a topic, then check if the FAQ answer would have really been enough to avoid them.
How does Qstomy complement an e-commerce FAQ?
Qstomy does not replace the creation of a good FAQ. It makes this database more accessible in conversation, at the exact moment the customer asks the question.
DTC accessories scenario
Shopify store, 900 tickets/month. The V1 FAQ covers delivery, returns, tracking, invoices, and compatibility. Qstomy uses these answers on the site and adds the Shopify context once the customer is identified. Pilot hypothesis: 320 FAQ questions handled in conversation, 46% of WISMO resolved without human intervention, 120 clicks to the return portal, 24% decrease in delivery tickets in 30 days.
The benefit is twofold: fewer repetitive tickets and better detection of questions missing from the FAQ.
See AI customer support, reduce support tickets, Shopify integration, and request a demo.
Which playbooks should be applied this week?
Playbook 1: Tickets to FAQ
Take the last 50 tickets. Group them into 8 patterns. Write a FAQ entry for each pattern that appears at least three times.
Do not aim for the perfect design from the start. Publish a short version with the answers that are most costly in support time, then improve the titles based on searches and the remaining tickets.
Playbook 2: Contact Page
Add the five most useful answers before the form. Measure how many visitors still click through to the contact page.
Playbook 3: One-sentence answer
For each entry, check that the first sentence actually answers the question. If it only introduces the topic, rewrite it.
Playbook 4: FAQ + Bot
Connect the FAQ to the chatbot, then take note of every uncovered question for two weeks.
Useful Linking
Tickets: reducing support tickets
Product: automated product FAQ
Support: Qstomy AI customer support
Enzo
June 26, 2026
