Testimonial Questions That Get You Something Worth Publishing

Image URL

Do not index

AI summary

Four targeted testimonial questions—who you are and what you do, the problem you faced before the product, how the task looks now on a typical day, and the specific results or numbers gained—produce publishable sentences, while avoiding generic questions that yield empty or vague answers; also includes guidance on replacing ineffective prompts, optional additional questions for deeper insights, and tips for sending, collecting, and using testimonials effectively.

Title

Testimonial Questions That Get You Something Worth Publishing

Date

Description

Testimonial questions to ask that return a sentence you can publish — four I would send, five that return nothing, and how to rewrite them.

Status

Done

Current Column

Published ✨

Person

Writer

You asked "How was your experience?"

They wrote "Great!"

You cannot put that on a pricing page.

Send four questions, each one built to return a specific kind of sentence. That is the whole job. If you want the pipeline around the ask — when, who, what happens after — start with the whole testimonial pipeline. This page is only the questions.

The four I would actually send

Copy them. The [blanks] are yours to fill before you send; the rest is what they type.

1. Who are you, and what do you actually do day to day?

You want a name, a role, and a sentence a stranger can place. "[Name], marketing" is not enough. "[Name], the person who owns outbound at a 12-person agency" is.

2. What were you doing about [task] before [Product], and what was annoying about it?

This is the before. Without it, the rest is praise, and praise is the cheapest thing on the page. Name the task for them or they will write "things were fine."

3. What does [task] look like now, on a normal Tuesday?

Not "how has it helped." Tuesday. A workflow, a number of tabs, a meeting that disappeared. What makes a testimonial good is specificity, and this is the question that produces it.

4. What has it got you — and if you can put a number on it, do?

Time, cost, volume, errors. If they cannot share a number, a named task that stopped happening is the honest substitute. Do not invent one for them, and do not write one in after.

If the answer is going on camera rather than into a form, use the same four and scripting a video testimonial — prompts, not a paragraph to read.

The five questions that return nothing, and what to ask instead

This is the part the lists skip. They hand you thirty prompts and leave you to find out, on a live customer, which ones produce a shrug.

These five come back empty often enough that I would delete them from any form I inherited.

"How was your experience?"

What you get: "Great." "Loved it." "10/10."

There is no before, no Tuesday, no number. A stranger cannot step into it.

Ask instead:

What were you doing about [task] before [Product], and what was annoying about it?

"Would you recommend us?"

What you get: "Yes."

A yes is not a testimonial. It is a poll result.

Ask instead:

If a colleague in the same role asked whether to try this, what would you tell them
— including who it is not for?

The "not for" clause is load-bearing. A testimonial that names who should skip it reads as an opinion. Testimonial templates use the same last line for the same reason.

"Any other comments?"

What you get: a blank box, or a sentence they already typed above.

It is a survey leftover. It asks them to invent a topic.

Ask instead: nothing. If you still want overflow:

What surprised you after the first week?

Surprise is a topic. "Anything else" is not.

"How would you rate us from 1–10?"

What you get: an 8, a 9, a 10. No sentence.

Useful if you are running NPS. Useless if you need a paragraph for the site. A star rating next to "Great service" is how a testimonial page starts looking like a widget demo.

Ask instead:

What changed in [metric or task] after you started — time, cost, volume, or errors?

If they cannot share the number, they can still name the task. That is publishable. A 9 is not.

"What did you like most?"

What you get: "The team." "The product." "How easy it is."

It invites a category. Categories are not quotes.

Ask instead:

What is the one thing you do every week now that you could not do before?

A weekly action is a picture. "The team" is a compliment you already believe.

The rest of the bank, if four is not enough

I would still send four. These eight are for when the page has a specific hole — a missing before, a missing "who it's for", a customer who already answered the first set and you are going back once.

Each one is paired with the sentence it is designed to produce. If the pairing is "a mood", skip it.

Before

What had you already tried that did not fit?

Designed to return: a named alternative or a workaround, and why it broke. Useful on a comparison page. Skip it if they were your first tool in the category — you will get a shrug.

What almost stopped you buying?

Designed to return: the objection a prospect is having right now. Publish that next to the pricing button. Do not ask it on camera unless they already said it in writing; people go polite when they can see their own face.

What was the cost of leaving [task] unsolved?

Designed to return: hours, a missed launch, a hire you did not want to make. Only send this if you already know they felt a cost. Otherwise they will write "it was fine."

After

What would you miss first if [Product] disappeared on Monday?

Designed to return: one concrete dependency. Stronger than "favourite feature", which returns a menu item.

Walk me through [task] as you do it now, step by step.

Designed to return: a sequence you can put under a feature screenshot. Too long for a homepage quote; right for a customer story. Cut it down yourself — do not ask them to write the short version and the long version.

What would you tell someone who is on the fence?

Designed to return: a recommendation with a condition. Close cousin of question 2 in the four. Use one or the other, not both.

Who it is for

Who should try this, in what situation?

Designed to return: a role plus a trigger. "Any SaaS company" is a miss; "a two-person team that just hit its first ten customers" is a hit. If they give you the first, send one follow-up: "smaller than that, or more specific?"

Who should skip it?

Designed to return: the limitation. I would rather publish "skip this if you need [X]" than a third "highly recommend." Prospects already have enough of those.

Do not ask both "who should try this" and "who should skip it" in the same four. Pick one. I pick skip — it is the rarer sentence.

How many to send

Four.

A form with twelve questions is a survey. People who said yes to a testimonial did not say yes to a survey.

We already publish a long list — questions to ask has seventy-three. I would not send it to a customer. Use it as a menu when you are building the four, then close the tab.

Three is acceptable if they already told you the before in a support thread. Paste that sentence back, ask them to confirm it, and spend the remaining two questions on Tuesday and a number.

More than six, and the last ones come back as "see above."

The note you actually send

The questions do not work if the ask around them is "would you mind writing us a testimonial?" That is an open-ended assignment. How to ask for a testimonial is the social half; the wording below is just the vehicle.

Subject: four questions, whenever you have ten minutes

Hi [Name] —

[Specific moment: the launch, the ticket, the thing they said].

Would you answer four questions I can quote? No need to make them pretty.
A few sentences each is enough. Skip any you cannot share.

1. Who are you, and what do you actually do day to day?
2. What were you doing about [task] before [Product], and what was annoying about it?
3. What does [task] look like now, on a normal Tuesday?
4. What has it got you — and if you can put a number on it, do?

[Link to the form, or: just reply to this.]

If you'd rather I draft something from what you already told me and you
edit it, say so. Either works.

— [Your name]

If you want a version sorted by channel rather than by question, email templates for asking is that page. Do not paste both into the same email.

Before anything goes on the site, get permission to use their name, role, company, and — separately — their face. Those are different yeses. The legal side of testimonials is the primer; check your own jurisdiction rather than treating that page as advice.

Doing this with Testimonial

The questions above work in an email. You do not need us for that.

What a Testimonial.to collection page changes is the next step. You put the four questions on a Branded collection page, send the link, and they type or talk without creating an account. Answers land in the Smart inbox to approve, then on a Wall of Love or a widget.

Where it breaks, including for us: the builder will let you add twenty questions. I have seen people do it. Completion falls off because you turned a testimonial into homework. I would put four and stop. The product will not stop you.

On Free you get 10 text testimonials and 2 video, total, plus the public page and the widgets. Unlimited text starts at Starter. Unlimited video starts at Ultimate, and Ultimate and Ultimate + are priced per space. The plans and pricing page is the live list.

If you have ten customers and they will reply in the thread, stay in the thread. The page earns its place when you cannot remember who you have already asked.