How many testimonial questions should I ask?
One to three. A single before-and-after question is often enough, and every extra question lowers the chance of a reply. Use follow-ups by reply for detail rather than a longer form.
testimonial collection
Testimonial Questions
Good testimonial questions ask about a change the customer lived through, in words they would use with a colleague. Below are questions grouped by the kind of story you need, the follow-ups that turn a vague answer into a usable one, the questions to avoid, and a short request email you can send today.
- Question bank
- Request email template
- Works with any form
Start with before and after
Most strong testimonials have the same shape: what it was like, what changed, and what it means now. Ask one question for each part and the customer writes the structure for you.
- Before“What was difficult, slow, or uncertain before you started working with us?”
- The turning point“Was there a moment when you could tell it was working? What happened?”
- After“What is easier, faster, or clearer now?”
- The stakes“What would you have to go back to if you stopped?”
- One sentence version“If a friend asked whether we are worth it, what would you tell them?”
Questions for the story you need
Pick the one or two that match where the testimonial will appear. A quote next to the pricing table needs a different answer from a quote on a support page.
- For a product or software“What were you using before, and what made you switch?”
- For onboarding and setup“What did you expect setup to be like, and what was it actually like?”
- For a service, agency, or consultant“What did you try before working with us, and what is different now?”
- For support“What were you trying to do, and what changed once it was sorted?”
- For results“Is there a number, a deadline, or an hour of your week that changed? Roughly how much?”
- For hesitation“What almost stopped you from signing up, and how do you feel about that now?”
- For a renewal“What made you decide to keep going for another year?”
Follow-ups that turn a vague answer into a usable one
First answers are often polite and general. One gentle follow-up, sent as a reply, usually produces the sentence you will actually publish.
- “Can you give me an example?”Turns “it saves us time” into “the Friday report now takes ten minutes.”
- “What did that mean for you or your team?”Moves the answer from a feature to an outcome a reader cares about.
- “How would you put that to someone in your role?”Produces wording that sounds like a peer rather than a brochure.
- “Is it all right if we quote that part?”Confirms the exact sentence you plan to use before it goes anywhere public.
Questions to avoid
These are common, and they produce testimonials that nobody believes or that you cannot use.
- Yes-or-no questions“Did you enjoy working with us?” gets “Yes!” and nothing you can publish.
- Leading questions“How much did our amazing team help you?” puts words in their mouth, and readers can tell.
- Rating-only asks“On a scale of 1–10…” gives you a number, not a story. Pair any rating with an open question.
- Questions about everythingTen questions in one request feels like homework. Three is plenty; one good one often works best.
A request email you can send today
Short, personal, and honest about the effort. Replace the bracketed parts and send it from your own address, close to the moment that went well.
- Subject line“A quick favour — two sentences about [the result]?”
- The message“Hi [name] — thanks again for [the specific thing they said or achieved]. Would you be open to sharing a couple of sentences about it for our site? The question is simply: what was difficult before, and what is easier now? There's a short form here: [link]. It takes about two minutes, your email stays private, and nothing is published until we review it. No pressure at all if now isn't a good time.”
- One follow-up, then stopIf there is no reply after a week, send one short reminder in the same thread. After that, let it go.
- Say thank you either wayReply when the story arrives, and tell them where it appears once it is live.
What this page does not claim
Useful search results start with an accurate promise. These limits apply today, in the shipped product.
- This guide is advice. PraiseHarbor does not send request emails, schedule reminders, or track who has replied — you send the ask from your own inbox.
- In PraiseHarbor you write the heading, the prompt above the story field, and the thank-you message. The fields themselves are fixed, so a multi-question survey is not supported.
- There is no video or file upload. Every story is text plus an optional 1–5 star rating.
- There is no importer for reviews held on other platforms, and no CRM, Zapier, or webhook automation.
Common questions about asking
What is the best single question to ask for a testimonial?
“What was difficult before, and what is easier now?” It invites a short story with a clear change, which is what makes a testimonial persuasive to the next reader.
Should I send the questions in the email or link to a form?
Put the one main question in the email so the customer knows what they are agreeing to, then link to a form for the answer. Replies in an email thread tend to stay in your inbox, and the permission to publish is rarely explicit.
Do I need permission to publish the answers?
Yes. Ask for it in the same place the customer writes the story. PraiseHarbor's form requires a display-consent tick and stores the exact sentence shown: “I give permission to display this story publicly. It may be edited only for obvious spelling or length.”
Can I edit a customer's answer before publishing it?
Only lightly, and only within what they agreed to. Fixing an obvious typo or trimming length is fair; changing the meaning or adding claims is not. If you want to use a shorter excerpt, confirm it with the customer first.