How to ask for a testimonial without being awkward.
May 2026
Asking customers for testimonials feels weird until you've done it a hundred times. The weirdness is mostly anticipation — once you have a script and a system, it's just another follow-up. What follows is the exact playbook we've watched land at indie SaaS, mid-stage startups, and agencies running multiple client products.
The single most important rule
Reference something specific the customer said or did.
That's the whole rule. Generic asks (“Hey, would you mind writing us a testimonial?”) get generic responses or none. Specific asks (“Last week you mentioned the import workflow saved you four hours — would you be open to writing two sentences about that?”) get responses about 60% of the time in our observed sample.
The specific reference does three jobs at once. It proves you were actually paying attention. It does most of their writing work for them (they just edit your prompt). And it makes the resulting quote good — because it's anchored to a real outcome instead of a vague feeling.
When to ask
Five moments that convert dramatically better than “a Tuesday afternoon when I remembered to”:
- Right after a positive support interaction. If they just thanked your team, the goodwill is at peak.
- After a renewal or upgrade. They voted with their wallet — converting that into words is the natural next step.
- After they hit a milestone in your product. 100th customer, 10K events processed, 30 days streak. You have specific receipts to reference.
- Immediately after a successful onboarding call or demo. Whatever they said on the call is the testimonial. Just ask them to repeat it in writing.
- When they engage with your content publicly. They liked, retweeted, or commented on something you published — they already think well of you in public, the testimonial is almost a formality.
What channel to use
Email beats DM beats in-app modal beats LinkedIn. But the right answer is “wherever you already have a real relationship with this customer.” If your relationship is entirely in a shared Slack, ask in Slack. If it's email-only, email. The channel matters less than feeling natural.
Two caveats: never ask in a public Twitter reply (looks like fishing), and never ask in an automated drip campaign (looks like spam). Both kill the response rate and make the customer feel like a number.
The four mistakes that kill response rates
1. Asking for too much
“Would you write us a paragraph describing your experience, your favorite features, what you'd say to a friend considering us, and your overall ROI?” — that's a 30-minute homework assignment, not a testimonial. Ask for two or three sentences. Mean it.
2. Sending a Google Doc
Google Doc edit-links are friction. Phone-unfriendly. Easy to lose in inbox triage. Easy to start, hard to finish. Worse: there's nothing handling format, so half the responses come back missing a role, a company, or a rating. Use a real form that lives somewhere stable. (Plauditly does this; so do five other tools we list on the integrations page honestly — the format matters more than the brand.)
3. Implying obligation
“As a valued customer, we'd really appreciate it if you would…” — this makes people feel taxed. Counterintuitive finding from our testing: adding an explicit out (“no worries at all if not”) raises response rate by something like 18%. We think people are more likely to agree when they feel free to refuse.
4. Not following up
The first ask gets responses from people who were going to write one anyway. The polite second nudge a week later picks up another batch — people who meant to and forgot. After two nudges, stop. Three is where it tips into nagging.
What to do after they send it
Three things, in this order:
- Reply within an hour.“Just got this — thank you. I'll publish it tomorrow with the credit you wanted. Means a lot.” That's it. The promptness signals you took it seriously.
- Publish where you said you would.Don't ask for a testimonial “for the website” and then bury it in a footer. Put it on the page that pays the bills — usually pricing or features.
- Send them the link when it's live.“Here's where it ended up” closes the loop. People share screenshots of their own testimonials being featured — free distribution.
A note on rich-result markup
If you publish testimonials on your site, emit schema.org Review and AggregateRating JSON-LD alongside them. Google reads it and may show ⭐ ratings next to your search result, which lifts organic click-through. Most testimonial tools gate this behind their highest tier. If you'd rather not buy your way into it, our free schema generator does it on a single page. (Plauditly does it by default on every embed, starting on the Starter tier — but the markup is the markup, whoever generates it.)
The shortcut
If you don't want to write your own ask from scratch, we keep a library of eight battle-tested templates — email, DM, in-app, LinkedIn — that you can copy, swap the placeholders, and send.