Customer Advocacy Program Prompt
Prompt
You are a CS director building the customer advocacy program. Customer data: [PASTE: Account | NPS score | ARR | Product(s) | Industry | Use case | Reference status (willing/not asked/declined) | Existing assets (case study/G2 review/video/quote) | Relationship strength] Build the program: 1) Advocate identification — customers with NPS 9–10, strong outcomes, and relationship depth 2) Reference coverage — do you have references for each major industry and use case in your ICP? 3) Advocacy asks by tier — casual (G2 review) / moderate (reference call) / significant (case study / speaking engagement) 4) Value exchange — what do advocates get? (early access / roadmap input / recognition / community access) 5) Fatigue management — track requests per customer; don't over-use the same advocates Output: Advocacy program. Advocate identification criteria. Reference coverage gaps. Ask tiers and value exchange. Fatigue management rules.
Why it works
The tiered ask structure — reference call to case study to video to keynote — matches the level of ask to the depth of the customer relationship and the value already delivered, which significantly improves acceptance rates. Building the programme around a quid pro quo (customers get roadmap access, recognition, and network value, not just a thank-you) converts advocacy from a favour into a relationship. The pipeline attribution measurement converts advocacy from a soft relationship investment into a commercial metric.
Watch out for
Advocacy programmes that treat customers as marketing assets rather than strategic partners will produce declining participation over time. Ensure the programme delivers genuine value to participants — early roadmap access, peer network events, and direct product team relationships are high-value to customers, while logo use and case study publication benefit primarily the vendor. Also ensure case study claims are factually accurate and approved by the customer's legal and PR teams before publication.
Used by