You asked, they said yes, and you felt the win. "Happy to give you a testimonial — send me what you need." Then you sent it, and the thread went quiet. A week passed. Two weeks. The testimonial you already mentally added to your homepage never arrived, and now you are stuck: chasing feels needy, but letting it drop means a genuine yes turned into nothing.
This is one of the most common ways testimonials die — not at the ask, but in the gap between agreement and delivery. The good news is that silence after a yes almost never means the customer changed their mind. It usually means the task you handed them was bigger than the goodwill they had in the moment. This guide covers how to diagnose the silence, follow up in a way that keeps the relationship intact, and — the part most people skip — redesign the request so the yes converts.
Why a yes goes silent
A customer who agreed to a testimonial and then disappeared is rarely avoiding you. Three things are usually happening instead, and each has a different fix.
- You asked for work, not a quote. "Send me a testimonial" is homework. The customer has to decide what to say, phrase it well, and worry it sounds fine to publish. That is a blank-page task, and blank-page tasks get postponed indefinitely by busy people who genuinely meant to help.
- It fell below the line. The customer meant it, but your request is now competing with their actual job. It is not that your testimonial lost — it never made it onto their list at all. Silence here is a priority problem, not a willingness problem.
- They are unsure what is safe to say. Some customers go quiet because they are quietly checking whether they need approval, or whether naming a result is allowed. The hesitation reads as silence but is really an unresolved question they did not voice.
Notice that none of these is "they no longer want to." That matters, because it means the follow-up should assume good faith and remove friction — not re-sell the customer on the idea.
The follow-up that does not feel like nagging
The instinct is to send "just checking in on that testimonial!" — which adds pressure without removing any of the effort that caused the stall. A better follow-up does the opposite: it acknowledges the customer is busy and shrinks the task in the same message.
Wait about a week after the original request, then send something like: "No rush at all on this — I know it dropped into a busy week. To make it easy, would it help if I drafted something based on what you told me, and you just edit or approve it? Totally fine to change anything." This does three things at once. It releases the guilt ("no rush"), it names the real cause ("a busy week"), and it replaces the blank page with a draft-and-approve task, which is far smaller. For the mechanics of that draft-and-approve move, see how to collect a testimonial without a lengthy interview.
If you get silence again after that, one more light touch is fair — then stop. Two well-designed follow-ups is persistence; a third is pressure, and pressure damages the relationship more than a missing testimonial helps your page.
Lower the effort until the yes converts
The real lesson of a silent yes is that your original request was too heavy. Fix that at the source, and future customers will not go quiet in the first place.
The most reliable conversion move is to draft the testimonial for them. You already have the raw material — a support message, a call transcript, a line from their onboarding survey, a Slack comment. Turn it into a clean, specific quote and send it back with: "Did I capture this right? Edit anything that feels off, and let me know I can use it." Now the customer's task is a thirty-second yes-or-tweak instead of an essay. Most silent yeses convert the moment you remove the blank page. If the raw material you are working from is thin or vague, how to turn a glowing but vague testimonial into specific proof walks through sharpening it before you send it back.
Two more effort-lowering tactics worth building into your default:
- Offer a menu, not a blank. Instead of "what would you say?", ask two or three specific questions: "What was the main thing this replaced for you?" and "What surprised you?" Answers to narrow questions become quotes; answers to broad ones become silence.
- Handle the permission question before it stalls them. Say up front exactly where the quote will appear and offer to show it before it goes live. Removing the unspoken "is this safe?" question keeps the hesitant customer from quietly parking the request. See what to say when a customer asks to see the testimonial before you publish it for how to make that offer without inviting endless revisions.
When to let it go — and what to do instead
If two thoughtful follow-ups and a pre-drafted quote still get silence, accept that this one is not converting right now and protect the relationship. A customer who feels chased will not become a reference later; a customer you let off gracefully might volunteer praise on their own terms next quarter.
But do not treat the silent yes as a total loss. You very likely already have usable proof from this customer that does not need their active participation — a public message they posted, a metric from your own analytics, a comment in a shared channel. The willingness was real; it was only the extra task that stalled. Harvest what already exists rather than waiting on new work, and you turn a stalled testimonial into published proof without asking the customer for anything more.
The takeaway
A yes that goes silent is not a customer who changed their mind — it is a request that was heavier than the moment of goodwill could carry. Read the silence as a priority-and-effort problem, follow up in a way that shrinks the task instead of adding pressure, and default to drafting the quote yourself so future customers never hit the blank page that caused the stall. The yes was real. Your job is to make it cheap enough to keep.