How to Ask for a Testimonial Without Making It Weird

Image URL

Do not index

AI summary

Four approaches to requesting testimonials are outlined, each tailored to how well you know the person—stranger, regular user, acquaintance, or enterprise contact—emphasizing specific, small asks, offering an easy out, and handling approvals; the guide also covers timing, preventing silence after a yes, dealing with refusals, securing permissions, and using tools like Testimonial.to to streamline the process.

Title

Date

Oct 14, 2024

Description

Four ways to ask for a testimonial, sorted by how well you know the person — stranger, regular, friend, enterprise contact. Plus what to do when they go quiet.

Status

Current Column

Person

Writer

You have been meaning to ask for three weeks.

The customer is happy. You know they are happy — they said so in a support thread in April.

And every time you open the draft you close it again, because it reads like begging.

That feeling is the whole problem, and it is not about wording. Here is how to get past it, sorted by how well you actually know the person.

Asking is the first of five stages, and it is the one that decides the quality of everything downstream. If you want the shape before the detail, the whole testimonial pipeline has the other four.

Why it feels weird

Two things are happening at once, and only one of them is obvious.

The obvious one: you are asking for unpaid work. Ten minutes of someone's day, for your benefit.

The one nobody names: you are asking them to go on the record. A testimonial has their name on it, usually their job title and their employer. They are lending you their professional reputation, and some part of them is working out what happens if you turn out to be bad in six months.

That second one is why "would you mind writing us a testimonial?" gets a warm yes and then silence. The yes was to being helpful. The silence is the reputation question, arriving later, with no easy way to say so.

Everything below is built to shrink both asks at once.

The two rules underneath all of it

Ask for something specific and small. "Would you write us a testimonial" is an open-ended assignment with no defined end. "What made you pick us over building it yourself?" is one question with a one-paragraph answer — and the answer is the testimonial.

Give them an out, in writing. One sentence: "No problem at all if you'd rather not." It costs you nothing, and it removes the thing that makes people go quiet instead of declining. A no you receive is worth more than a yes you never hear about again.

Four asks, sorted by who you're asking

Most guides sort by channel — email, SMS, in person, social. That is the wrong axis. The channel barely changes what you say. How well you know the person changes everything.

1. Someone you have never spoken to

A real customer, paying, using it. You have never exchanged a word.

What they are actually thinking: who is this and why are they in my inbox.

Ask for one sentence, not a testimonial. Do not use the word. Ask a question:

What made you pick us over [the obvious alternative]?

That is answerable in a line, from a phone, without opening a document. And what comes back — "honestly, because your trial didn't ask for a card" — is a better testimonial than anything they would have composed on purpose.

What not to do: do not lead with a link to a form. A cold link is a task; a question is a conversation. The link goes in your second message, after they have already answered, when it is a formality rather than an assignment.

2. The regular you have somehow never talked to

They log in every week. They have been on the plan for a year. You have never had a conversation, which makes this the highest-value ask you have and the most awkward one, because there is no relationship to draw on.

Lead with the specific thing you know they do.

You've had the weekly digest running since March — you're one of about a dozen people using it that consistently. Can I ask what it replaced?

That opening does one job: it proves this is not a mail merge. Anyone can tell the difference between "Hi [First Name], we value your feedback" and a sentence that could only have been written about them.

What not to do: do not manufacture warmth you have not earned. "Hope you're having a great week!" from a company you have never spoken to reads as a template, because it is one.

3. Someone you actually know

A former colleague, a friend of a friend, someone you have been on calls with for two years.

Here the trap runs the other way. It is so easy to ask that you ask vaguely — and vague asks from friends are the ones most likely to die. They say yes immediately because they like you, and then it sits behind everything with a deadline.

Be more specific with people you know, not less.

Could you write two or three sentences on the migration — specifically the bit where we moved the historical data? Any time before the 14th is great.

A topic, a length, and a date. Friends will hit a deadline you actually name and will quietly drop one you do not.

What not to do: do not accept "yeah, I'll send you something." That is not a commitment, it is a kind noise. Reply with a date.

4. The enterprise contact

They want to help. Their employer may not let them. Somewhere behind them is a legal team, a comms team, or a policy about naming vendors.

Ask about the approval before you ask for the testimonial.

Before I ask for anything — is there a process on your side for this kind of thing? Happy to work with whoever needs to sign it off.

That single question converts an awkward silence into a project with a route through it. It also tells them you have done this before, which is its own kind of reassurance.

Offer the smaller versions up front. Attribution by role rather than name — "VP of Engineering at a Fortune 500 logistics company" — is often approvable when a named quote is not. So is a quote with the company anonymised. Say so in the first email, because they will not think to ask.

What not to do: never suggest they skip their own approval process. You are asking someone to take a professional risk to make your marketing better, and the answer should be no.

When to ask

The honest answer is that we have not measured this, and I would rather say so than repeat the line every other guide uses.

What is defensible: ask after a moment, not on a schedule. Not thirty days after signup because a sequence fired. After they shipped the thing your product helped them ship. After a support conversation that went well. After they told you something nice, which is the easiest one and the most commonly missed — if someone says "this saved us so much time" in a Slack channel, that is the moment, and it will not come round again.

Calendar-triggered asks arrive when nothing has just happened, and nothing-has-just-happened is a bad time to ask someone to feel strongly about you.

They said yes and went quiet

This is the most common failure in the whole process, and almost nothing written about testimonials addresses it.

The reason is structural: the yes and the testimonial are two separate asks, and most people only make the first one properly. You get an enthusiastic reply, you send a link to a form, and the form is where it dies — because by the time they open it, the warm moment has passed and they are looking at an empty box.

Two fixes, in order of how well they work.

Capture it in the thread where they said yes. They are already typing. Reply immediately with the question, in the same message, and take whatever comes back as prose. You can tidy it later. What you cannot do is recover the moment.

If you do need a form, send it inside the hour. Not the next day. And put the first question in the body of the email as well as behind the link, so they can answer without clicking anything.

If it has been a week: one follow-up, short, with the out repeated. "Totally fine to say no — just closing the loop." One. Not a sequence.

They said no

Take it, immediately and warmly, and then ask the much smaller question:

Completely understood. Would you be OK with me quoting the line you wrote in the support thread in April?

Very often the testimonial already exists. It is in a support ticket, a Slack message, a renewal email, a tweet. Quoting something they already said is a far smaller ask than composing something new — they are approving a sentence rather than writing one — and it is the version most people say yes to after declining the first.

You still need permission. You are asking to move their words to a public page, which is not what they were doing when they wrote them.

Permission, and the bit people skip

Get it in writing, and be specific about where it will appear. "Can I use this?" and "can I put this in a paid ad?" are different questions and deserve to be asked separately.

Ask separately for the name, the job title, the company and the photo. Plenty of people will give you the words but not the face.

And if anything changed hands — a discount, a free month, a gift card — the connection has to be disclosed. That is a genuine legal requirement in several jurisdictions, not a nicety, and it is worth checking your own before you offer an incentive.

What to actually say

I have deliberately not put email templates on this page. The wording is a solved problem and it lives in one place: email templates for asking — fifteen of them, with the blanks left in, plus a version for a social DM.

Two others worth having open:

Questions to ask, if you are building the one-question version of the ask above.

Asking through your newsletter, if you have a list and would rather make one ask to everyone than four hundred individual ones.

And if you want to know what a usable testimonial actually needs to contain before you go asking for one, that is testimonial templates.

Doing this with Testimonial.to

This is what we build, so read this section with that in mind.

The part of the above that a tool genuinely fixes is the gap between the yes and the artifact. You send a personalised link, your customer does not create an account, and they answer your questions by typing or by speaking. Voice answers come back transcribed — which matters here more than it looks, because the questions in this post get much better answers spoken than written. People say things out loud they would never commit to a text box.

You set your questions once as a reusable set of five to ten, so the "what made you pick us" version and the "tell me about the migration" version are two saved templates rather than two emails you write from scratch. Answers land in the Smart inbox, and approved ones go onto your Wall of Love or into a widget.

On the free plan you get 10 text testimonials and 2 video, total, plus the public testimonial page and the widgets. If the job is a handful of quotes for a landing page, that is the whole job.

Where it does not fit: if your asks are conversations in a shared Slack channel with ten customers you know by name, a tool adds a step. Ask in the thread, paste the answer into your site, move on.

Wrapping up

That is four ways to ask, sorted by how well you know the person, and the three places the process usually breaks — the vague ask, the silent yes, and the no you never followed up.

Not sure which of the four your situation is? Reply to this post and tell me who you are asking and how you know them — I will tell you which version to send.

If you would rather the yes and the testimonial happen in one step, start free.