How to use FAQ as self-service

How to build a FAQ from your real support data instead of imagination — and where to embed it (page, PDP, checkout) for maximum self-service.

Written By Bas den Hoed

Most plant-shop FAQ pages are written from the inside out — what the reseller assumes a customer might want to know. They read like a brochure, answer the wrong questions, and go untouched for two years. Your FAQ should be a direct mirror of the questions that actually came in this month, embedded where the question gets asked.

💡 The short version: the #1 reseller mistake is writing FAQs from imagination. A useful FAQ comes from your actual support inbox, chat logs, and on-site search no-results from the last 30 days — not from what you assume customers will ask.

Why "real questions only" is the rule

An imagined FAQ has two failure modes. It answers questions nobody asks ("What is your company mission?") and skips the ones everybody asks ("Do you ship to Belgium?"). And the language is wrong — customers ask in their own words, not your supplier-vocabulary. The result: customers don't find the answer, message you anyway, and your support load doesn't drop.

An FAQ built from real questions does the opposite. The phrasing matches what customers type. The 5–10 dominant questions are visible. Every answer is one less ticket. For a 50-msg/day plant reseller, a real FAQ typically removes 30–40% of those messages within a month.

How to collect the actual questions

Three sources, all from the last 30 days:

  • Support inbox. Tally subjects of email + contact form messages. Anything appearing 3+ times is FAQ-worthy.

  • Chat / WhatsApp logs. Same exercise. Chat surfaces different questions than email — more pre-purchase, more "is this in stock?", more sizing.

  • On-site search no-results. Pull queries that returned zero results from your search analytics. FAQs disguised as searches — "pet safe", "winterhard", "Calathea care".

Block 90 minutes once. List every recurring question on one page. You'll end up with 20–30 candidates — more than enough for a first version.

Categorise into five buckets

Five categories cover almost every plant-shop FAQ. Use these:

  • Pre-purchase — sizing, pet-safety, light requirements, included accessories, "is this real or artificial?".

  • Order & delivery status — "Where is my order?", cut-off times, delivery to BE/DE, weekend delivery.

  • Plant care — watering, light, repotting, what to do if leaves yellow.

  • Returns & complaints — damage on arrival, the EU 14-day right and the plant-perishability exception, refund timelines.

  • Payments — accepted methods (iDEAL, Bancontact, Klarna, PayPal), invoice for B2B, VAT.

Five categories means five clear sections. More than five and customers stop scanning.

Placement: page, PDP, checkout

An FAQ buried at /faq under three menu clicks barely gets used. Place answers where the question is asked:

  • Dedicated FAQ page — full set, all five categories, linked from footer and help menu. The canonical version.

  • Embedded on the PDP — plant-specific, 3–5 questions max. Calathea Orbifolia example: "Is this plant safe for cats?", "How much light does it need?", "How often do I water it?". See your PDP layout.

  • Embedded at checkout — payments only. "Can I pay later with Klarna?", "Do I get a VAT invoice?". Two or three, collapsible.

Same answer can live in multiple places. The goal is "answer at point of question", not "single source of truth".

Format that actually gets read

  • Question as H3, phrased as the customer would. "Is the Monstera Deliciosa safe for cats?" — not "Pet toxicity information for Monstera Deliciosa".

  • Answer in <80 words. One paragraph. If genuinely longer, end with a link ("Read the full Calathea care guide →").

  • One concrete fact per answer. "Yes, Monstera is mildly toxic to cats — keep out of reach." Beats a 200-word essay on toxicity degrees.

  • No marketing voice. Customers are mid-task; they want the answer.

A category list works for browsers. For typers, layer an AI search on top: customer types "kan ik met Klarna betalen?", AI returns the payments FAQ instantly. Most chat tools (Tidio, Crisp, Trengo) bundle this as part of their AI agent — see your customer service stack. No chat AI yet? Even a basic search bar on the FAQ page beats scrolling — Shopify's Search & Discovery app indexes static pages.

Maintenance: every quarter, no exceptions

An FAQ ages fast. Plant assortments rotate, payment methods change, delivery partners change, policies update. The maintenance rule: once per quarter, redo the 90-minute exercise. Read the last 90 days of support, list new recurring questions, retire FAQs that nobody asked anymore, update answers that drifted from the current policy. Put it in your calendar — March, June, September, December — and treat it as non-negotiable.

⚠️ A stale FAQ is worse than no FAQ. A customer who follows your FAQ instructions and finds them outdated (wrong return window, discontinued payment method, retired delivery promise) escalates angrier than one who messaged you first. Quarterly cleanup is cheap insurance.

Next action

This week: open your support inbox, chat logs, and search no-results report. Block 90 minutes. List every question that appears 3+ times. Group into the five categories. Draft answers in <80 words. Publish the FAQ page, embed 3–5 plant-specific Q&As on your top-10 product pages, and add 2–3 payment questions at checkout. Put a quarterly recurring task in your calendar. The FAQ that mirrors your real inbox is the fastest customer-service improvement you can ship — see how to set up your customer service stack for the channels that sit on top.