How to automate social proof collection: permission and accuracy

To automate social proof collection, trigger a specific request at the moments customers are happiest, and record each person's permission as structured data with its scope and date. Collecting testimonials is mostly a permissions problem, not a content problem. You need separate permission to use a person's words, name, photograph and employer logo, and a verbal yes from eighteen months ago is not something you can produce when asked.

Accuracy is the second problem. A testimonial that contains a number is a claim you make about your product, and you must substantiate it, even though the customer 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

Key takeaways

• Permission for a testimonial is specific: the quote, name, job title, photograph and employer logo each need separate, recorded approval.
• A number in a customer quote is your claim as the advertiser, so keep the evidence for it.
• Ask at moments of success, such as after a well-resolved support case, at renewal or after an unprompted compliment.
• Ask a specific question, not for "a testimonial", and capture the permission in the same step.
• Store permission as structured data and give every testimonial a review date.

Permission is specific, not general

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

Scope it explicitly: which quote, and which contexts (website, advertising, printed material, sales decks). Permission for one context is not permission for all.

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

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

Employer approval is different from personal approval. An individual saying yes does not bind their company, and some organisations require a marketing review.

Allow withdrawal. People change roles and change their minds, so the system must remove a testimonial promptly.

What you are claiming when they say it

A quoted number is your claim. In the United States, the Federal Trade Commission (FTC) holds advertisers responsible for endorsements made on their behalf (FTC Endorsement Guides FAQ, 2026). Check the rules in each market where you advertise.

Typical results matter. If you feature an exceptional outcome and cannot show most customers achieve similar results, the FTC says the ad must clearly disclose the results generally expected (FTC Endorsement Guides FAQ, 2026). "Results may vary" alone may not be enough.

Keep the evidence for any quantified claim: where the number came from, over what period, and how it was measured.

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

Incentivised endorsements need disclosure. The FTC says free products, discounts and other incentives can require a clear and conspicuous disclosure (FTC Endorsement Guides FAQ, 2026).

Employee and affiliate testimonials must disclose the relationship. People break this rule accidentally.

Logos, names and faces

A customer logo requires permission, and many companies have brand guidelines that govern how the logo may be shown.

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

Check the contract. Some enterprise agreements prohibit naming the customer publicly, and the marketing team rarely reads them.

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, so reposting needs their permission.

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

Building it with CodeWords

CodeWords connects to 3,000+ integrations (CodeWords integrations directory, 2026), 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. Pro costs $39 per month and Business costs $100 per month as usage grows (CodeWords pricing page, 2026); details are on the pricing page.

Finding the moments worth asking at

Just after a success. The product knows about it before marketing does.

After a support interaction resolved well. Teams underuse this moment, and it 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 or a community post. This is the best moment, and few teams capture it systematically.

When a champion moves company. This is both a testimonial opportunity and a sales opportunity.

Never during an escalation. The automation must know about open escalations to avoid them.

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. This raises the response rate, and it 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 effective and hard to get, so ask for it only where the relationship supports it.

Capture the permission in the same step. Going back for it later is where most requests fail.

Keeping it current

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

Check whether the person is still there. A quote attributed to a role someone left three years ago looks stale.

Check whether the company is still a customer. A quote from a former customer is a worse version of the same problem.

Re-confirm periodically for anything used prominently. A short email 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 form of social proof most teams build, and they are the least verifiable. Five other forms are stronger and easier to keep honest.

Numbers about usage, stated precisely and kept current: how many customers you have, how long the median customer has stayed, and how much the product has handled.

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

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

Independent recognition, such as an audit, a certification or a place on someone else's list. The credibility comes from the source, not 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 the reader wonders what else on the page is out of date.

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 a refusal politely 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 response rates are lower still.

Enterprise approval can take months and involves people you have never met.

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

Regulated sectors have additional restrictions, and some prohibit testimonials entirely.

Automation cannot judge whether a quote is fair to use in a given context. A person must decide.

What to build first

Build capture of unprompted compliments first. Watch support tickets, emails and community mentions for customers saying something positive, and send each one to whoever owns that relationship with a suggested follow-up. The material already exists, it is specific and credible, and few teams collect it systematically.

Two habits make the difference. Record the permission as structured data with its scope and date, because a permission you cannot produce is a permission you do not have. Ask a specific question instead of asking for a testimonial, because a specific question produces something worth publishing.

Frequently asked questions

What permission do I need to publish a testimonial?

You need written permission, recorded with the date and the exact wording approved, and scoped to specific contexts. Name, job title, photograph and employer logo are each separate permissions. An individual's yes does not bind their company, so check whether the employer needs to approve as well.

Am I responsible for a claim a customer makes?

Yes, as the advertiser you are responsible for it. In the United States, the FTC holds advertisers responsible for endorsements made on their behalf (FTC Endorsement Guides FAQ, 2026). A quoted number is therefore your claim, and you need the evidence for it: where the number came from, over what period, and how it was measured.

Do I need to disclose if a testimonial was incentivised?

Yes, disclose it. The FTC says free products, discounts and other incentives can require a clear and conspicuous disclosure (FTC Endorsement Guides FAQ, 2026). Employee and affiliate testimonials must disclose the relationship too. People break this rule accidentally, so build the disclosure into the template.

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

No, not automatically. User-generated content belongs to the person who made it, and reposting it for marketing needs their permission. Ask for permission in writing, record the scope, and keep the record with the asset so the next person knows what is approved.

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

No, being a customer is not consent to be named. Some enterprise contracts explicitly prohibit naming the customer publicly. Check the agreement before you publish a name or logo, because the marketing team rarely reads it, and ask the account owner who has.

When is the best moment to ask?

The best moments are just after a success the product records, after a well-resolved support interaction, at renewal, and immediately after an unprompted compliment. The compliment is the best moment of all, and few teams capture it systematically. Avoid asking during an open escalation.

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

Ask a specific question, such as "What were you doing before?" or "What changed?", instead of asking for a testimonial. Offering to draft the quote from something they already said, for them to edit and approve, raises the response rate. Short, specific answers beat general praise.

How long can a testimonial be used?

Give each testimonial a review date and retire it when it expires. A quote attributed to a role someone left years ago looks stale, and a quote from a company that is no longer a customer is worse. Six current, specific testimonials persuade more than fifty old ones, so retire instead of accumulating.

What is stronger than a testimonial?

Five forms of proof are stronger than a testimonial: third-party reviews you did not select, named public work the customer chose to discuss, independent certifications, precise current usage numbers, and open evidence such as a public status page or published benchmarks.

Why do stale numbers hurt?

A statistic with an old date makes the reader wonder what else on the page is out of date. An outdated proof point is worse than none. Give every number a review date, and replace or remove it when the date passes.

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

No, do not automate the ask for large accounts. For significant accounts the request should come from the person who owns the relationship. Automate the prompt to that person, with the context and a suggested message, and let them send the ask themselves.

What should happen when somebody says no?

Record the refusal, so the same customer is not approached again next quarter. An unrecorded no is a common reason a good customer gets asked three times. Store the refusal as structured data alongside permissions, and thank the customer politely.

Related reading

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