Customer advocacy consent works when the customer can see exactly what they are agreeing to and can change that decision without reopening a vague promise. Treat each use of a customer's identity, words, time, and contact details as a separate permission with its own owner and record. One enthusiastic yes does not approve every use. Permission for a quote does not establish whether the customer accepts a public name, a prospect call, or continued use after circumstances change.
Start with the use
Write down the intended use before asking for consent. A customer can approve one activity and still need a separate decision for another.
Separate the permission paths by intended use:
- naming the customer in public
- quoting the customer
- introducing the customer to a prospect
- featuring the customer in a public story or event
- keeping feedback confidential
Access paths can have different identities, approval methods, scopes, time limits, records, and revocation methods.1 Give each use its own line in the permission record. A broad request such as "Can we use your story?" leaves too much for both sides to interpret later.
Ask for each yes
Make the request easy to approve or decline. Say what will happen, who will see it, and what the customer needs to do.
Use a separate question for each permission:
- May we use your company name in a public customer story?
- May we publish this quote with your name and company?
- May a prospective customer contact you directly?
- Should we keep this feedback confidential?
- May we use this recording in public material?
When the conversation moves to a new step, ask for another explicit opt-in.2 A customer who agrees to share feedback has made one decision. A later request to speak with a prospect, approve a quote, or appear publicly needs its own answer.
Put important contact permission in writing. A documented authorization can show that customers agreed to be contacted.3 Record the exact activity approved. A general statement that the customer supports the company is not enough.
Capture the boundaries
Another person should be able to read the record and know what is allowed. Record the boundary while the conversation is fresh.
For every approved use, capture:
- the customer or account covered
- the approved activity
- the audience and channel
- whether the customer is named, quoted, or anonymized
- the exact wording or asset approved
- the person who owns the decision
- the review date or event that should trigger a fresh request
- the method for stopping future use
Each permission path needs a named owner and a reproducible decision record.4 The owner should be able to answer what was approved, when it was approved, and whether the current use still matches that approval.
Requested feedback can remain confidential or be published as anonymized guidance to the public.5 Record which option the customer chose. Do not let a later editor turn anonymized guidance into an attributed quote without returning to the customer.
For a quote, keep the approved wording with the consent record. If the final version changes the meaning, adds a claim, or changes the audience, pause publication and ask again. The customer should approve the version that will be used, not an earlier conversation about what it might become.
Handle prospect introductions
A prospect introduction gives another person a route to the customer, so it carries more exposure than a public mention. Treat the handoff as a separate permission event.
Ask whether the customer wants a direct introduction, a forwarded message, or no contact handoff. Record the route they chose and the context the prospect may receive. Share only the approved contact route, and tell the prospect what the customer agreed to before the introduction happens.
A signed contact authorization supports the decision to allow contact.3 It does not settle permission for public naming, quoting, recording, or future introductions. Keep those uses separate in the record so a later request does not inherit more access than the customer granted.
After the customer accepts an introduction, confirm the next step with them before sending details. If the prospect asks for a broader conversation, return to the customer for a fresh decision. The next request should be specific enough for the customer to accept, limit, or decline.
Keep consent live
Consent belongs to a particular use at a particular point in time. Review it when the channel, audience, wording, or customer circumstances change.
Set a review trigger for each permission. A new public campaign, a revised quote, a different prospect audience, or a new type of recording should prompt a check against the original approval. If the use no longer matches the record, stop and ask for permission again.
Make withdrawal practical. When a customer changes their mind, record the decision, tell the people who use the material, remove it from future work, and check active public placements. The record should show what was stopped and who completed the change.
What not to do
- Do not make a customer obligation to provide a case study do the work of consent; contract language requiring a case study has no teeth.6
- Do not publish feedback as an attributed customer statement when the agreed outcome was confidentiality or anonymized public guidance.5
- Do not treat an initial expression of enthusiasm as approval for the next advocacy step; get another explicit opt-in.2
- Do not pass along customer contact details until the record shows that the customer agreed to be contacted.3
- Do not let one approval line cover naming, quoting, prospect contact, and public featuring when those uses have different audiences or withdrawal needs.1