Advocacy Management

What this capability handles

How it works in detail.

Advocacy Management keeps the referenceable-customer loop running instead of letting it stall the moment things get busy. Most teams know advocacy matters, references, logos, case studies, reviews, but the work of spotting ready customers and timing the ask falls off the list, so the pipeline stays thin. This capability is for mid-market customer success teams who want a consistent advocacy motion without a dedicated program manager. The outcome is a steady flow of well-timed, well-matched advocacy asks coordinated with the CSM. Here is how it works. The capability identifies candidate customers, scores their readiness, coordinates the ask, tracks the outcome, and logs it. It runs inside your CS platform, CRM, and messaging tools, and it draws on the health score, outcome signals, prior advocacy history, and your program criteria. Per candidate it produces a readiness assessment and a proposed ask matched to the right opportunity, references, logos, case studies, or reviews, routed to the CSM so the relationship owner stays in control of the outreach. The decision logic is criteria-driven: it uses readiness signals and program rules to propose advocacy asks with CSM routing. It is careful about relationship risk. Sensitive-relationship outreach or strategic-account advocacy routes to the CSM for direct ownership, because an ask made at the wrong moment can cost more than it returns. Its handoff conditions are a strategic-account flag, a sensitivity signal, or a recent-ask conflict, so a customer is not approached twice in quick succession. Every candidate, proposed ask, and tracked outcome is logged and reviewable, which keeps the program honest about what is working. Typical fit is modest. The capability is ready when advocacy program criteria are documented and outreach templates are approved. Clear criteria are what let it judge readiness consistently rather than guessing. On impact, 5 to 10 percent of the role's impact is the referenceable-customer loop running consistently, and the expected trajectory is an advocacy pipeline rising month over month. It handles 5 to 10 percent of the role's volume, the smallest share of the role, which is exactly why it tends to lapse without a system holding it steady. The primary measure is advocacy pipeline size, tracked over time so the team can see the loop compounding rather than starting from zero each quarter.