Customer advocacy

Published: 2026-09-12 · Last reviewed: 2026-09-12 · Reading edit: 2026-09-12

A customer says they would be happy to help. They might mean a private reference call, not a public case study or a stream of requests from sales. An advocacy program makes participation specific, voluntary, and easy to manage for the customer as well as your team.

Match the request to the person

Distinguish a private reference call, public quote, case study, event appearance, and peer introduction. Each requires its own scope of permission and effort. Start by asking what participation, if any, the customer would welcome.

Run a respectful program

1. Record willingness and scope. Track approved topics, formats, regions, review requirements, and availability. Include an easy way to pause or decline.
2. Match relevance. Choose advocates whose actual experience addresses the prospective buyer’s question. Do not imply they used features or achieved results outside their experience.
3. Prepare a precise brief. Explain the audience, purpose, expected time, questions, publication channels, and any compensation or benefit. Obtain necessary personal and organizational approval.
4. Preserve the customer’s voice. Fact-check names and figures, distinguish edits from rewritten claims, and give the agreed review opportunity. Never invent or materially alter a quote to strengthen the pitch.
5. Track requests and follow through. Coordinate across sales, marketing, and customer success so the same person is not repeatedly approached. Thank them and share the finished material or outcome as agreed.
6. Review continued suitability. Refresh permissions and claims when the relationship or product changes. Pause requests during unresolved service problems rather than treating advocacy as an entitlement.

Worked example

A fictional customer agrees to one private reference call about implementation. A salesperson later wants to use a sentence from the call on the website. The program owner requests separate publication approval instead of assuming the original agreement covers a public testimonial.

The customer declines publicity but remains willing to take an occasional relevant call. The system records that preference, preserving a useful relationship without turning every advocate into a public spokesperson.

Advocacy record

Field	Record
Willing participant and approved scope
Actual experience and evidence limits
Organizational approval requirements
Request history and availability
Compensation/disclosure where relevant
Review date and pause mechanism

Evaluate sustainably

Track fulfilled relevant requests, customer feedback, and contribution to buyer understanding. Do not rank advocates only by revenue influenced. Inspect concentration: if a few customers carry most requests, expand the pool carefully or reduce demand.

Try it with your own work

Ask one willing customer which topics and formats they are comfortable with. Record their preference and approval requirements before sending the next request.

Sources and scope

• FTC: endorsements, influencers, and reviews provides US guidance on honest endorsements and material connections; the participation workflow is original.

The example is fictional; any numbers illustrate the method rather than a benchmark. Adapt the worksheet to your own situation.

What to read next

Case study · Review program · Customer success

Chapter guide · All playbooks

---

Copyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms.

Canonical source: github.com/weilun88313/B2B-Playbook