You just got a perfect quote. On a call, in an email, in a survey response, a customer said exactly the thing that would convince your next ten prospects. You are thrilled. And then it sits — for weeks, sometimes forever — because between "the customer said it" and "we are allowed to publish it" lies a swamp of approvals, legal reviews, and forgotten threads.
This gap is where most testimonials die. The enthusiasm was real, the words were great, and none of it ever reached a landing page because the approval process was slow, unclear, or never started. This guide is about building a quote approval workflow that closes the gap in days rather than months, while protecting the relationship you just strengthened.
Why approval kills more testimonials than rejection
Customers rarely refuse outright. What actually happens is that the request to publish gets routed to someone who was not on the original call, lands in a legal queue with no deadline, or waits on a "let me check internally" that never resolves. The quote does not get rejected — it gets stranded.
The cost is invisible, which is why it persists. You never see the published testimonial that did not happen. But the math is real: every quote that dies in approval is proof you paid to collect — in relationship capital and team time — and then threw away. Fixing approval throughput is often higher-leverage than collecting more quotes, because you are already sitting on a backlog of approved-in-spirit, unpublished praise.
The four points where approval stalls
Before designing the workflow, name the four failure points it has to survive:
- The speaker is not the approver. The person who praised you may need their manager, legal, or comms team to sign off — and those people have no emotional investment in the quote.
- The ask is vague. "Can we use your feedback?" leaves the customer unsure what they are approving, so they stall rather than risk agreeing to something open-ended.
- There is no deadline. With no date attached, the request drops to the bottom of every inbox it touches.
- The thread goes cold. One unanswered email becomes silence, and nobody follows up because following up feels pushy.
A good workflow neutralizes all four. Here is one that does.
A five-step quote approval workflow
Step 1 — Capture consent at the moment of praise
The best time to start approval is the instant the customer says the great thing. On a call, the moment someone gives you a quotable line, ask right then: "That is exactly the kind of thing prospects ask us about — would you be open to us quoting that publicly?" Verbal yes in the moment makes the formal sign-off a confirmation rather than a cold request. This is why asking for a testimonial on a customer call is so much more effective than chasing it afterward — approval starts before the enthusiasm cools.
Step 2 — Send the exact text you want to publish
Never ask for open-ended permission. Send the customer the precise quote, attribution, and placement: "Here is what we would like to publish, with your name and title, on our homepage: '[exact quote].' Does this look right to you?" Approving a specific, finished artifact is a small, low-risk decision. Approving "the concept of being quoted" is a large, scary one. Show the finished thing.
Step 3 — Do the editing for them, and flag it honestly
Spoken quotes need light cleanup — removing filler, fixing a false start. Do that work yourself and present the polished version, but never change the meaning. If you tightened the wording, say so: "I cleaned up the phrasing slightly for readability — let me know if it still reflects what you meant." This makes the customer's job a yes-or-no check instead of an editing assignment, which is the difference between a same-day reply and a two-week delay.
Step 4 — Attach a soft deadline and a default
Give the request a date and a low-friction default: "We are updating the page on Friday — if this looks good, a quick 'approved' is all we need, and feel free to tweak anything that feels off." The deadline creates urgency; the "quick approved" lowers the cost of saying yes. For customers who need to route it internally, ask who else needs to see it so you can address the real approver directly instead of relaying through the speaker.
Step 5 — Run a defined follow-up sequence, then stop
If you do not hear back, follow up — but on a defined cadence, not by random guilt-driven pings. A short, friendly reminder a few days after the deadline recovers a large share of stalled approvals, because most non-responses are forgotten emails, not refusals. Use the same structured approach as the follow-up and reminder sequence after no response, and define a clear stopping point so a non-answer becomes a clean "not now" rather than an awkward open loop.
Build it as a system, not a favor each time
The reason approval stays slow at most companies is that it is improvised every time — a fresh email written from scratch, a fresh decision about whether to follow up. Turn it into a system: a saved template for the exact-text request, a standard soft-deadline line, a default follow-up cadence, and a tracker that shows which quotes are awaiting sign-off and for how long. When approval is a repeatable workflow instead of a one-off favor you nervously ask for, throughput climbs and far fewer great quotes die in the gap.
The takeaway
Most testimonials are not lost to rejection — they are lost to a slow, vague, deadline-free approval process that lets enthusiasm cool and threads go cold. Capture consent at the moment of praise, send the exact text you want to publish, do the editing yourself, attach a soft deadline with an easy default, and follow up on a defined cadence. Run that as a repeatable system and the distance from "the customer said it" to "it is live on our site" shrinks from months to days.