Publishing testimonials with permission and context
Publish a testimonial only with appropriate permission, accurate attribution and the context needed to understand it.
AI-assisted practical guide · Editorial approach
The useful starting point
Publish a testimonial only with appropriate permission, accurate attribution and the context needed to understand it. Keep a record of the approved wording and use. A positive statement about one interaction should not become an unsupported claim about every service or customer outcome.
Understand the decision
Confirm who made the statement, their relationship to the business and which project it concerns. Avoid altering wording in a way that changes meaning. Check permissions for names, company identifiers and photographs separately where necessary. Give the record an owner and a process for withdrawal or correction. Do not add invented ratings around a genuine quote.
A practical approach
Use only evidence the business can substantiate and has permission to publish. Separate a statement about your process from a verified result for a customer. Decide who can approve public responses and which situations need private escalation. Keep sensitive customer information out of public replies. A trustworthy page explains what is known, what is still a concept and how a customer can ask for clarification.
- Record identity, relationship and scope.
- Approve exact published wording.
- Confirm permitted name and image use.
- Maintain a correction and withdrawal route.
Illustrative example
A consultancy could publish an approved client comment about the clarity of a workshop, linked to the documented scope. It would not attach a revenue-growth figure that the client never measured. The testimonial supports the experience it actually describes, not an unrelated commercial promise.
A mistake to avoid
Avoid using AI-generated customer portraits to make a quote appear to come from a real person without explaining the image's nature and relationship to the record.
What to review
Audit permissions, expired context and differences between approved testimonials and their use in pages, campaigns or proposals.
Turn the guide into a working brief
Maintain a proof register with the source, scope, consent, approved wording and review date of each claim. Remove or correct material when permission changes or the underlying facts stop being current. Treat recurring complaints as input for service improvement, not merely as a messaging problem. Measure the response process and resolved issues alongside public sentiment; visibility alone does not show that customers were helped.
Common questions
What should I prepare before asking for help?
Start with this checklist: Record identity, relationship and scope. Approve exact published wording. Confirm permitted name and image use. Maintain a correction and withdrawal route. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Audit permissions, expired context and differences between approved testimonials and their use in pages, campaigns or proposals. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- Google Search Central: helpful, reliable content
Reference for useful content, truthful authorship and evidence. The business methods and illustrative examples in this guide are original editorial material.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.