Buyer Questions: Build a One-Page FAQ and Three Reply Templates
About Alex: a pen name. There is no shop behind it, and no results are claimed. What follows is a method and my opinion, and I'll mark which is which.
In short
If the same few questions keep landing in your messages, I would write the answers once instead of from scratch each time. Keep a log of the questions, put the repeated ones on the product page as a short FAQ, and keep three reply templates for the messages that need a personal touch. The method is mine, not a platform rule or a benchmark.
What you get from reading it:
- A question log and FAQ worksheet you can copy
- Three reply templates in a plain, warm voice
- A way to turn one repeated question into one page change to test
A message arrives. "I paid but I can't find the file." You know the answer, and you have typed it before, so you type it again, a little differently, a little tired. The next day a different buyer asks whether the planner works on a phone. Same answer as last week. You type that too.
Each reply on its own is fine. The pattern is the interesting part. If three people ask where the file is, my reading is that the page left that question open. (A reading, not a measurement.)
So the work has two halves. On the page, answer the repeated question where the buyer can see it. For the messages that still come, keep a short, kind answer ready.
Who this is for. A seller of digital products (printables, templates, spreadsheets, presets) who gets buyer messages and sees the same questions come back. If you have no messages yet, you can still use the FAQ half with guessed questions, labelled as guesses; the log half needs real messages.
What it costs. Nothing, and no software. A notes file is enough. Allow one sitting for the log and FAQ, and a second for the templates.
What I don't know about your platform. Messaging tools, delivery and rules differ between marketplaces and websites. I have not checked any of them, so this guide states no platform facts. Where a platform matters I say "check yours".
Step 1: Start a question log
You'll end up with a list of the questions you have actually been asked, each with a category.
Open your messages: a marketplace inbox, an email address, comments or direct messages. Look back as far as is comfortable. No source says how many messages are enough; ten is a workable start in my judgement.
Copy the question, not the person. A name or an email address has no use in this log, and leaving them out keeps the file simpler to share with a helper (I have not checked privacy rules; check yours before sharing buyer messages). Cut the question down to its core: "Where do I download it?" is enough.
Then give each message one category. I would start with four, and they cover the three jobs in this guide:
- Delivery. The buyer cannot find or receive the product.
- Fit. The buyer wants to know whether it will work for them, before or after paying.
- Opening. The file is there, but it won't open, extract or display.
- Other. Anything else: custom requests, sharing, policies.
The categories are my own cut, not a standard. If your messages don't fit them, change them. What matters is that you can count.
Copy this box into a notes file or spreadsheet.
QUESTION LOG product: __________
Categories: D delivery, F fit,
O opening, X other
# date cat question (short)
1 ______ __ ___________________
2 ______ __ ___________________
3 ______ __ ___________________
4 ______ __ ___________________
5 ______ __ ___________________
6 ______ __ ___________________
7 ______ __ ___________________
8 ______ __ ___________________
Add a new line per message.
No names, no email addresses.
One honest limit. A log of your own messages shows what the people who wrote to you asked. It does not show what the people who didn't write wondered about. Visitors who leave without writing are a silent group, and I have no source for how large it is. So the log is a good place to start, not a full map.
Step 2: Tally and rank the questions
You'll end up with a ranked list that decides what goes on the page first.
Count in two ways. First, group messages that ask the same thing in different words (Ines's lines 1, 4, 8 and 12 all concern getting the file). A group of three or more is a candidate for the FAQ.
Second, count each category except Other. A category with three or more messages whose questions differ (Ines's four fit questions, or her three opening problems) is a candidate for a short FAQ section, because I suspect a buyer who hesitates over fit may not write at all.
Other is a catch-all of unlike questions, so read it line by line instead. Both thresholds are judgements, and the number is arbitrary. With a short log, two is worth a look.
- Rank candidates by count, highest first.
- If two tie, put first the one a buyer meets earlier on the way to paying: fit before delivery, delivery before opening the file. That tie-break is mine, not measured.
- A single question in a category of fewer than three messages goes in the log and stays there. One message is not yet a pattern.
If your log is small, the tally will feel flimsy, and it is. A count of 3 out of 6 tells you less than 3 out of 30.
A worked example: Ines and her garden planner (imaginary)
Ines is an imaginary seller. Her product, "Seed Row Planner", is an imaginary spreadsheet template for planning a vegetable garden. The messages, the dates and every number below are invented to show the method. They are not results from any real shop.
Ines opens her messages and copies 14 questions into her log. Her categories are D, F, O and X. She writes each question short.
IMAGINARY LOG: Seed Row Planner
1 D I paid but can't find my
download
2 F Does it work in Excel or only
Google Sheets?
3 O File won't open on my phone
4 D Where do I get the file after
paying?
5 F Is it good for a small balcony?
6 O It says the file is damaged
7 F Can I print it on A4?
8 D No email with the link came
9 X Can I share it with my garden
group?
10 F Does it work on a Mac?
11 O The zip won't extract
12 D Is the download link valid?
13 X Can you add a column for herbs?
14 X Is there a refund?
Her tally, recomputed with a short Python script:
| Category | Count |
|---|---|
| D (delivery) | 4 |
| F (fit) | 4 |
| O (opening) | 3 |
| X (other) | 3 |
Total: 14. Delivery and fit tie at four messages each, and the delivery messages are one repeated question. By the tie-break, fit goes first because a buyer meets it before paying: Ines answers her fit questions (Excel, Mac, A4, balcony) on the page first, then the delivery question. Opening also qualifies (three messages, three different problems). Ines gives it one short answer after the first five and keeps Template 3 for the rest.
The "other" row stays off the FAQ for now. A custom request (line 13) is a one-off for a reply. The refund question (line 14) needs care; see common mistakes.
Step 3: Write the one-page FAQ
You'll end up with three to eight questions and short answers, in the order a buyer meets them.
The seven-block guide asks for three to five guessed questions in block 7; this guide replaces the guesses with the questions your messages show, so use as many as the tally supports (three if three repeat).
An FAQ answers on the page what the buyer would otherwise write to ask. In my opinion, use the buyer's own words from the log, not cleaned-up versions, because a buyer is likely to scan for their own sentence.
Order the questions as a buyer meets them: fit, then what happens after paying, then what to do if something goes wrong. That mirrors the tie-break from Step 2.
Keep each answer to one to three sentences. If an answer needs more, the page itself probably needs a block.
Write only what is true of your product today. If you say "works on a Mac", you should have opened it on a Mac, or say what you did try.
Copy this worksheet.
FAQ WORKSHEET product: _________
Top questions from my tally, in the
order a buyer meets them. Use the
buyer's own words.
FIT
Q1 ______________________________
A1 ______________________________
(one to three sentences; say
what you have tried yourself)
Q2 ______________________________
A2 ______________________________
AFTER PAYING
Q3 ______________________________
A3 ______________________________
(what the buyer clicks, gets,
opens, in order)
IF SOMETHING GOES WRONG
Q4 ______________________________
A4 ______________________________
(what to try; how to reach me)
Check: could a stranger act on each
answer without asking me anything?
Ines's page FAQ, filled in. Everything about the product is imaginary, and so are the answers: they describe what her imaginary file does, and a real seller must write only what is true of theirs.
IMAGINARY FAQ: Seed Row Planner
Q: Does it work in Excel?
A: Yes, I opened it in Excel. It
also opens in Google Sheets;
the colour bars look plainer
there.
Q: Does it work on a Mac?
A: I have opened it on a Mac in
Excel. I haven't tried other
apps there, so I can't say.
Q: Can I print it on A4?
A: Yes. The print area is set for
A4 and for US Letter.
Q: Is it good for a small balcony?
A: It plans rows and sowing dates
for any size of plot. I haven't
tested it for pots, so I can't
say more.
Q: Where is my file after paying?
A: You land on a download page. A
copy of the link is also in your
order email.
Q: What if the file won't open?
A: Download it again, then write to
me and say what you see.
The Mac answer says what was tried and stops there. Naming what you did not try may read as more trustworthy than a bigger claim (my impression, not a finding).
Step 4: Write three reply templates
You'll end up with three short messages you can paste and edit in a minute.
The FAQ catches the buyers who read. The templates are for those who write anyway. I would keep three: a delivery problem, "will this fit what I need?", and a file that will not open. Each follows the same four-part shape, my own pattern:
- One warm line that thanks them or acknowledges the problem. Once is enough; a long apology costs the buyer reading time.
- The next step, in numbered form if there is more than one.
- One question for the buyer, the single detail you need to help them.
- Nothing you can't keep. No promised time, no promised result, unless you are sure.
Square brackets mark the parts to replace. Change the wording until it sounds like you.
Template 1: a delivery problem
Subject: Your file for [product]
Hi [name],
Thank you for your order, and sorry
for the trouble. Let's get the file
to you.
1. Look in [the place your setup
sends it: order email, download
page].
2. Check your spam or junk folder.
3. Still nothing? Reply with the
email you ordered with and the
date, and I'll look.
[your name]
Step 1 needs your own setup. If you don't know how your platform delivers the file, find out before you send this.
Template 2: "will this fit what I need?"
Hi [name],
Thanks for asking before you buy.
Short answer: [yes / no / it
depends].
What it does: [one line, from the
page].
What it doesn't do: [one line].
I have used it with [apps/devices
you have really tried]. I haven't
tried it with [others], so I can't
promise there.
If you tell me [one detail], I can
say more. Either way is fine.
[your name]
The line "I haven't tried it with..." is the heart of this one. It protects the buyer from a bad purchase and you from a later message that begins "you said it would work".
Template 3: a file that will not open
Hi [name],
Sorry the file won't open. Let's
sort it out.
Could you tell me what you see when
you try to open it (an error, a blank
page, nothing happens), and which
device and app you use?
Meanwhile you could try:
- [a step you know works, such as
opening it in another app]
- downloading it again from [place]
If that doesn't help, reply and
I'll [what you can honestly do].
[your name]
One question, in two parts, is enough to reproduce the problem without blaming the buyer's device. If you need the file name too, ask in your second message.
On voice: plain and warm means short sentences, the buyer's name, and no jargon they didn't use. I would drop stock phrases such as "per our policy". That is taste, and you may differ.
Step 5: Turn a repeated question into a page change
You'll end up with one change to the page, written as a test.
A reply fixes one buyer's problem. A page change fixes the question for the next buyer. So when a question reaches your threshold, ask where on the page the answer belongs, and place it there before it goes only in the FAQ.
A rough map, my own: device and app questions point to the contents block and the FAQ; size and format questions to the first image; "where is my file" to the delivery block; "won't open" to a short line near the contents.
The seven-block structure is in How to Write Your First Product Page: Seven Blocks, in Order. The scoring sheet that checks the delivery and objection questions is in Audit Your Product Page in 30 Minutes: its check 4 is delivery and its check 6 is objections, and a repeated message can be the evidence for a "no" or "partly" on either.
Pick one repeated question, not two. Write a test the way the Why Your Shop Isn't Growing guide describes: one change, a start and end date fixed in advance, and a result that would change your mind. The measure here is simple: how many times the question arrives in your messages, in a window of the same length as the one before.
Ines picks "Where do I get the file after paying?" because her tally put delivery second and the answer was missing from her page. Her imaginary test, in the same box shape:
IMAGINARY TEST (Ines)
QUESTION: Where is my file after
paying? (4 of 14 messages)
CHANGE: Add one line to the page:
what the buyer sees after paying
and where the link arrives.
MEASURE: Messages that ask it, in
the next 4 weeks, versus the 4
weeks the log covers.
START / END: ____ to ____ (set
before I edit)
WOULD CHANGE MY MIND: The count
does not fall, or other messages
rise by the same amount.
Two cautions. The count of messages is not a sales measure; it only shows whether the question kept arriving. And with small numbers, a drop from 4 to 3 is well within chance, so treat a small change as inconclusive.
Common mistakes
Some of these are mistakes in the replies, and some are mistakes in the log.
| Mistake | Why it hurts | What I would do |
|---|---|---|
| Promising a reply time you can't keep | A missed promise may cost more than a plain reply | Name a time only if you can keep it, or say "as soon as I can" |
| Over-promising in a reply: "it works on everything" | A buyer acts on it | Say only what you tried; name what you didn't |
| Promising a refund in a reply | The platform may have its own rules | Check your platform's own rules before you write any refund sentence |
| Adding every question to the FAQ | Twenty answers hide the five that matter | Take the top candidates from your tally |
| Treating the log as the whole picture | It shows only people who wrote | Read the page as a stranger too |
The refund row can cost the most. To "Is there a refund?", your first instinct may be yes to be kind, or no to be safe. Either can be a promise you did not mean to make. I state no rule here. Check your platform's own rules before you write a refund sentence in a reply. Then point to your shop's policy text rather than rewording it.
In my judgement, words like "instantly" and "works perfectly" invite a later message, and "I'll fix it today" is a promise about your day. Prefer "I'll look into it and reply" when you can't know.
Frequently asked questions
How many questions should the FAQ have? Three to eight is my starting point, chosen so a phone screen doesn't become a wall. No source gives a number. If your tally shows three repeated questions, three is the right count.
Should I send the same template to everyone? Treat it as a first draft. Change the greeting, one line of the middle and the sign-off. A reply that reads like a copy may feel cold.
What if the question is about the platform, not my product? Point the buyer to the platform's help pages and give your own contact line. I can't answer for the platform here.
Where you are now
If you did the steps, you have a log, a tally, a short FAQ and three templates. If all you did today was start the log with eight lines, that is a real start.
Your next step
None of these is required. Choose by what your tally showed.
- Fit questions lead the tally: the contents and objection answers are the likely gap. How to Write Your First Product Page: Seven Blocks, in Order covers block 3 and block 7.
- Delivery or opening questions lead: score the page with Audit Your Product Page in 30 Minutes, where check 4 is delivery.
- You have one repeated question and a written change: run it as the one-change test in Why Your Shop Isn't Growing.
- You want a regular habit for looking at messages like this: A Fifteen-Minute Weekly Review for a Small Shop is the place to fit it in.
Sources and checks
How we checked. No official platform page, marketplace policy or law was fetched or read for this guide on 2026-10-26, so it cites no sources and states no platform facts or rules. The categories, the three-or-more rule, the tie-break, the FAQ order and the template shape are my opinions. Seed Row Planner, Ines, her messages, FAQ and counts are imaginary. Nothing has been tested with real sellers or buyers.
What was run. The tally of the imaginary log (14 messages: delivery 4, fit 4, opening 3, other 3) was recomputed in Python; the saved script is in the raw notes folder for this article.
Unverified. That the categories fit real messages; that three repeats is a useful threshold; that a page answer reduces the messages that ask it; that the templates get a reply. What any platform says about saved replies or refunds is not checked.
Checks still to run. V01 to V03 in the front matter. Until real sellers have built a log and used the templates, this article stays in review.
What this guide does not claim. That any FAQ or template raises sales or cuts messages, that any buyer behaves as the imaginary ones do, that any refund or delivery wording is allowed on your platform, or that Ines or her product ever existed.