Testimonial: collecting proof that reads as real

A testimonial is a short statement from a customer saying something useful about working with you. Its only job is to be believed, and the main obstacle to that is how much testimonials resemble each other: the same enthusiasm, the same cadence, the same absence of anything a disappointed person could have written.

What a testimonial needs to be believable

• A full name, role and organisation. An initial and a first name reads as invented, because it frequently is.
• A photograph where the person agrees, which raises credibility more than the wording does.
• Specifics: what they used it for, what changed, what they were doing before.
• Their own phrasing, including the awkward bits — edited testimonials all converge on the same voice.
• Something slightly qualified, since unqualified praise is read as selected rather than typical.
• Nothing that reads as a product description, because that is the giveaway of a testimonial written by the vendor.

When to ask

Immediately after something went well, and specifically after the customer says so unprompted — a thank-you email, a comment in a meeting, a renewal with a remark attached. That moment passes within days. Asking at renewal time is tempting and worse, because the request arrives alongside a commercial conversation and the answer gets tangled in it. The second-best moment is right after a support interaction that was resolved properly, which is when people are most conscious of the thing being handled rather than of the price.

Ask for permission in the same message as the request, and state exactly where it will appear. The common failure is a warm reply that cannot be used because nobody established whether it could be published with a name attached, and going back to ask a second time has a much lower success rate.

Making it easy to give

1. Offer to draft it from what they already said, then ask them to correct it — this triples response rates and the corrections are what make it real.
2. Ask two or three specific questions rather than «would you write something», because a blank page is why most requests go unanswered.
3. Keep it short; three sentences used in full beats a paragraph that gets trimmed into blandness.
4. Say where it will appear and for how long, which makes approval a smaller decision.
5. Go back a year later to check it is still accurate, especially if their role changed.
6. Record who gave permission and when, since the person who agreed will eventually leave.

Ettex Forms is enough for the collection itself — the same two or three questions, the permission captured with the answer — so nothing depends on finding an old email thread. Where the story is longer than three sentences, it stops being a testimonial and becomes a case study, which is a different format with a different purpose.