Client Testimonial Permission Emails: Ask Before You Publish Proof
Ask before you publish a client testimonial. Short permission email plus what they can refuse: name, photo, metrics. Not a case-study template. Not legal advice.

A client compliment in email is not a homepage asset. Client testimonial permission emails are how you turn a private thank-you into something you can show—without guessing, stretching, or inventing a quote they never signed off on.
This page is Ask-Then-Quote. It is not Freelance Case Studies That Win Clients (story structure). It is not Portfolio Websites Freelancers Need Before the Next Pitch (site layout). It is not Freelance Contracts That Actually Protect Scope (the written fence). Those stay owners. You still need them. This URL is only the ask.
Send the exact quote, name line, photo, and metrics you want to use. Wait for a written yes—or a smaller yes. Do not publish proof they did not approve. This is not legal advice and not a fake-testimonial kit.
Disclosure: Educational process only. Not legal advice. No invented client names or results.
Table of contents
- Private praise is not a publishable endorsement
- The refusal map: name, photo, metrics
- Ask-Then-Quote
- A short permission email
- Where the yes lives after they reply
- FAQ
Private praise is not a publishable endorsement
People say kind things when a file lands. They are talking to you, not to a landing page. The moment you paste that sentence under a headshot, it reads as an endorsement: someone other than you recommending the work.
In the U.S., start with the FTC’s Advertisement Endorsements topic page and the staff FAQ FTC’s Endorsement Guides: What People Are Asking. Endorsements must be honest opinions, and you cannot use them to make a claim you could not make yourself. We are not your lawyer. Other countries have their own rules.
A portfolio clause in the contract is useful. It still may not cover a named quote, a logo, or a revenue number. Ask for the assets you will actually ship. If they ignore you, do not invent a persona named “Sarah, E-commerce Brand.”
The refusal map: name, photo, metrics
Treat permission as a checklist, not a vibe.
| Asset | If they refuse | What you can still do |
|---|---|---|
| Full name | Use first name, role, or “client in [industry]” only if they allow that fallback | Ask which label they want |
| Company / logo | Drop the brand mark | Industry + problem only |
| Headshot or team photo | Quote without a face | Skip the circle crop |
| Metrics (revenue, traffic, time saved) | Qualitative result they approve | “Cleared the backlog before launch” beats a fake 47% |
| Exact wording | Use their revised sentence | Do not “tighten” it back into hype |
A client can approve a case-study narrative and still refuse a testimonial block. Case studies are your story of the work. Testimonials are their voice. If the work is under NDA, the answer is often “nothing public.”
Ask-Then-Quote
ASK-THEN-QUOTE
1. Draft → quote + name line + photo + metrics you want
2. Email → paste all four; invite edits and nos
3. Wait → written yes / smaller yes / no
4. File → save the reply with the live copy
5. Publish → only what the reply covers
Send this near delivery, while the project is still warm. One email. If they say “sure, whatever,” reply with the pasted block anyway.
A short permission email
Subject: Permission to share a short quote about the [project name] work
Hi [Name],
Thanks again for the [project]. I would like to put a short testimonial on my site. Nothing goes live until you say so.
Here is the exact text I would use:
“[Their words, or a draft they can rewrite].”
Name line: [Full name, title, company — or tell me what to use] Photo: [none / this headshot / company logo] Metrics: [none / the number we already discussed in writing]
You can change any line, drop your name, drop the photo, drop the numbers, or say no to the whole block. If you prefer a case study with no quote, we can do that instead.
Reply with “approved as written,” your edits, or “please don’t publish.”
Thank you, [You]
That is the whole ask. They can refuse. You still have work samples if the contract allows portfolio use without a personality quote.
Where the yes lives after they reply
Save the reply next to the live copy. If you later change “saved us a week” into “3x revenue,” you need a new yes. Put the quote on the portfolio site after the page already shows what you sell. Reuse a sentence in a proposal. If they later ask you to take it down, take it down. One approved paragraph beats a carousel of fiction.
FAQ
Do I need permission before I publish a client testimonial?
Yes if you want to quote their words, name, photo, or results as their endorsement. Asking in writing is the practical default. This page is process, not legal advice. Rules differ by country, contract, and whether the quote is used as advertising.
Is this a second freelance case study template?
No. Case studies own the story structure (problem, work, result). This URL owns the ask: a short permission email and a refusal map for name, photo, and metrics. Write the case study only after the yes you actually got.
What can a client refuse?
Anything you asked for. Common refusals: full name, company name, headshot, logo, revenue numbers, traffic numbers, or a quote they never said. A yes to a paraphrased outcome is not a yes to a headshot on the homepage.
Can I invent a testimonial if they ignore the email?
No. Silence is not consent. Use a labeled sample, a public demo, or skip proof on that project. Fake quotes are a trust problem and can be a deceptive-advertising problem. The FTC’s Endorsement Guides say endorsements must be honest.
Should permission sit in the contract?
A portfolio/testimonial clause in the scope document can make the later email shorter. The contract page owns that fence. Still send the ask with the exact quote and assets you want to publish—contracts rarely list the final sentence you will paste.
Is this legal advice?
No. For advertising rules in the U.S., start with the FTC’s Endorsement Guides and the staff FAQ “What People Are Asking.” For contracts, privacy, and your jurisdiction, ask a lawyer. This article is a freelancer workflow, not a statute.
Send one permission email with the live copy attached. Publish only the yes you received. If the yes is smaller than you hoped, ship the smaller proof—never a quote nobody approved.
Keep learning
More guides in the same topic lane.
WordPress Two-Factor Login: Lock wp-admin Without Locking Yourself Out
WordPress two-factor login: Second-Factor-Then-Recovery. Use the WordPress.org Two Factor plugin, test on staging, save backup codes. Not a client vault.
WordPress Comment Spam Without Killing Real Replies
WordPress comment spam: hold then approve so real replies still land. Discussion settings plus Akismet—not a security plugin bake-off. WordPress.org docs.
Uptime Monitoring for Small Blogs: Know When the Site Is Down
Uptime monitoring for small blogs: Ping-Then-Page—HTTP 200 on home plus a money URL, then email or phone. Not a ranking factor. Host pick stays elsewhere.