How to automate social proof collection: permission and accuracy

Collecting testimonials looks like a content problem and is mostly a permissions problem. Somebody's words, their name, their photograph and their employer's logo are all things you need permission to use, that permission is specific rather than general, and the version somebody gave you verbally eighteen months ago is not something you can produce when asked.

The second problem is accuracy. A testimonial containing a number is a claim you are making about your product, and it is your responsibility to substantiate it — not the customer's, even though they are the one who said it.

What we'll cover

• Permission is specific, not general
• What you are claiming when they say it
• Logos, names and faces
• Building it with CodeWords
• Finding the moments worth asking at
• Getting something usable
• Keeping it current
• The kinds of proof that are not testimonials
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

Permission is specific, not general

Written, and recorded, with the date and the exact wording they approved.

Scope it explicitly: which quote, which contexts — website, advertising, printed material, sales decks — since permission for one is not permission for all.

Name and job title separately, because people frequently agree to be quoted without their title or their employer attached.

Photograph is a separate permission again, and one people decline more often than any other.

Employer approval is different from personal approval. An individual saying yes does not bind their company, and many organisations have a policy requiring a marketing review.

Allow withdrawal. People change roles and change their minds, and a system that cannot remove a testimonial promptly will eventually be awkward.

What you are claiming when they say it

A quoted number is your claim. Advertising rules in most markets treat a testimonial as a representation by the advertiser.

Typical results matter. Publishing an exceptional outcome without qualifying it is the classic problem, and "results may vary" is not always sufficient.

Keep the evidence for any quantified claim — where the number came from, over what period, measured how.

Say if it is not typical, prominently, where that is the case.

Incentivised endorsements need disclosure in most markets, including discounts, free service, or anything else of value.

Employee and affiliate testimonials must disclose the relationship, which is a rule people break accidentally rather than deliberately.

Logos, names and faces

A customer logo requires permission, and most companies have brand guidelines governing how it may be shown.

Being a customer is not consent to be named, and for some organisations the relationship itself is confidential.

Check the contract. Several enterprise agreements explicitly prohibit naming the customer publicly, and the marketing team is rarely the team that read it.

Photographs of individuals carry personal data obligations in several jurisdictions on top of the usage permission.

User-generated content is not free to use. A customer's social post about you belongs to them, and reposting is a permission question rather than a courtesy.

Keep the permission with the asset, so the person assembling a page can tell what may be used where without asking.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, so the product events, the CRM, the survey tool and your asset store can meet in one automation.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which moments trigger a request, what is collected, and how permission is recorded.
3. Authorize the connections — the product or CRM source, the collection form, and wherever approved assets are stored.
4. Describe the exceptions: an account under contract restrictions, an open escalation, somebody asked recently.
5. Run it against the last quarter and check which customers it would have approached.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Finding the moments worth asking at

Just after a success, which the product usually knows about before anybody in marketing does.

After a support interaction resolved well, which is a consistently underused moment and produces specific, credible material.

At renewal, where the decision to continue has just been made explicitly.

After an unprompted compliment — in a ticket, an email, a community post — which is the best possible moment and is almost never captured systematically.

When a champion moves company, which is both a testimonial opportunity and a sales one.

Not during an escalation, obviously, and the automation needs to know about escalations to avoid it.

Getting something usable

Ask a specific question, not for a testimonial. "What were you doing before" and "what changed" produce usable answers; "would you write us a testimonial" produces silence.

Offer to draft it from something they already said, for them to edit, which raises the response rate substantially and is legitimate as long as they approve the final wording.

Short is better. Two sentences that say something specific beat a paragraph of general praise.

Specifics beat superlatives. A named problem and a described outcome persuade; "great product, great team" does not.

Video is disproportionately effective and disproportionately hard to get, so ask for it only where the relationship supports it.

Capture the permission in the same step, since going back for it later is where most of these fall over.

Keeping it current

Add a review date to every testimonial when it is collected.

Check whether the person is still there, since a quote attributed to a role somebody left three years ago is noticeably stale.

Check whether the company is still a customer, which is the more embarrassing version of the same problem.

Re-confirm periodically for anything used prominently, which is a short email and avoids a difficult conversation later.

Retire rather than accumulate. A wall of fifty testimonials persuades less than six current, specific ones.

Track where each is used, so a withdrawal can be actioned completely rather than approximately.

The kinds of proof that are not testimonials

Quotes are the version everybody builds and they are the least verifiable form of social proof. Several others are stronger and are easier to keep honest.

Numbers about usage, stated precisely and kept current — how many customers, how long the median one has been with you, how much of something the product has handled.

Named public work where the customer has already spoken about you publicly, which needs no new permission and carries more weight because they chose to say it.

Third-party reviews, which persuade more than anything on your own site precisely because you did not select them.

Independent recognition — an audit, a certification, an inclusion in someone else's list — where the credibility comes from the source rather than from you.

Open evidence: a public status page, published benchmarks, documentation good enough to evaluate without talking to anybody.

Keep every number current. A statistic with a stale date does more damage than no statistic, because it invites the reader to wonder what else has not been updated.

Making it survive

Store permission as structured data, not as an email in somebody's inbox.

Make withdrawal a single action that removes the asset everywhere it is used.

Do not automate the ask for large accounts, where it should come from the person who owns the relationship.

Handle the no gracefully and record it, so the same customer is not asked again next quarter.

Report the outcome: requests sent, responses, permissions recorded by scope, and anything approaching its review date.

Limits worth knowing about

Response rates are low, and video rates are very low, which is normal.

Enterprise approval takes months and involves people you have never met.

Advertising rules differ by market, particularly around disclosure and typical results.

Regulated sectors have additional restrictions, sometimes prohibiting testimonials entirely.

Automation cannot judge whether a quote is fair to use in a given context, which remains a human decision.

What to build first

Capture of unprompted compliments. Watch support tickets, emails and community mentions for customers saying something positive, and surface them to whoever owns that relationship with a suggested follow-up. The material is already there, it is specific and credible, and almost nobody collects it systematically.

Two habits make the difference. Record the permission as structured data with its scope and date, since a permission you cannot produce is a permission you do not have. And ask a specific question rather than asking for a testimonial, because the specific question is what produces something worth publishing.

Frequently asked questions

What permission do I need to publish a testimonial?

Written permission, recorded with the date and the exact wording approved, scoped to specific contexts. Name, job title, photograph and employer logo are each separate permissions, and an individual's yes does not bind their company.

Am I responsible for a claim a customer makes?

Yes. Advertising rules in most markets treat a testimonial as a representation by the advertiser, so a quoted number is your claim and you need the evidence for it.

Do I need to disclose if a testimonial was incentivised?

In most markets, yes — including discounts, free service or anything else of value. Employee and affiliate testimonials must disclose the relationship too, which people break accidentally rather than deliberately.

Can I repost a customer's social media post about us?

Not automatically. User-generated content belongs to the person who made it, and reposting it for marketing is a permission question rather than a courtesy.

Can I name a customer just because they are a customer?

No, and some enterprise contracts explicitly prohibit it. Check the agreement, which is rarely something the marketing team has read.

When is the best moment to ask?

Just after a success the product knows about, after a well-resolved support interaction, at renewal, and immediately after an unprompted compliment — which is the best moment of all and is almost never captured systematically.

How do I get a usable testimonial rather than generic praise?

Ask a specific question — what were you doing before, what changed — rather than asking for a testimonial. Offering to draft it from something they already said, for them to edit and approve, raises the response rate substantially.

How long can a testimonial be used?

Give each one a review date. A quote attributed to a role somebody left years ago is stale, and one from a company that is no longer a customer is worse. Six current specific testimonials persuade more than fifty old ones.

What is stronger than a testimonial?

Third-party reviews you did not select, named public work the customer chose to talk about, independent certifications, precise current usage numbers, and open evidence like a public status page or published benchmarks.

Why do stale numbers hurt?

Because a statistic with an old date invites the reader to wonder what else on the page has not been updated. An out-of-date proof point is worse than none.

Should the request for a testimonial be automated for large accounts?

No. For significant accounts it should come from the person who owns the relationship. Automate the prompt to them, not the ask itself.

What should happen when somebody says no?

Record it, so the same customer is not approached again next quarter. An unrecorded no is the most common reason a good customer gets asked three times.

Related reading

• Automating product review requests
• Automating sentiment analysis on reviews
• Automating product feedback categorisation