Customer Reference Program Template
Two documents and three sheets that weight every ask by real effort and cap each advocate at six points a quarter.
Free download · No account needed
Advocate Bench · one quarter, 14 eligible advocates
A 4-point ask on 2 points of remaining capacity gets rerouted before it sends, not regretted after.
| Advocate | Points used | Remaining | Case study ask | Result |
|---|---|---|---|---|
| Corland Wire & Cable | 4 of 6 | 2 | Needs 4, over by 2 | Rerouted |
| Halvern Metal Works | 0 of 6 | 6 | Needs 4, fits easily | Assigned |
Corland and Halvern are the only two advocates in this segment on the whole bench. Across the quarter, 20 asks spent 39 points total, and only one advocate anywhere on the register, a different account entirely, ever reached the 6-point cap.
Every reference-program guide agrees on the failure mode: ask the same willing few too often and they burn out. Gainsight's own guidance is to track how often each advocate is engaged so nobody gets overused, and that is about as far as the standard advice goes anywhere else too. A raw count treats a ten-minute review and a half-day case study interview as the same one ask, and nothing tracks which of several requesting teams already asked this month.
This pack weights every ask type by what it actually costs and gives each advocate a 6-point quarterly cap instead of a headcount. Corland Wire and Cable took a 1-point review from marketing, then a 3-point reference call from sales six weeks later, reaching 4 of 6 points with neither team aware of the other's request. A 4-point case study ask next would have put Corland at 8, two over the cap. Opportunity Matching rerouted it to Halvern Metal Works, the only other advocate in the same segment, with a clean 6 points open.
Asks also open on a real signal instead of a campaign date: a 14-day window starts the day an NPS response clears 9, a QBR closes with a stated relationship score, or an expansion signs. Milberg and Clark's research on moods and compliance found people comply more with a simple request in a happy mood than a neutral one, which is the moment a signal-timed ask is built to catch. An account a health review already flags as stable is often ready for the next QBR to surface a fresh signal.
What's in the pack
Weight the Ask, Not Just the Count
The method itself: every ask type carries a real point cost against a quarterly cap, so a request that would push an advocate over gets rerouted before it sends, not regretted after.
Advocate Register sheet
Every qualified advocate with segment, health score, tenure, willingness, and points used against the quarterly cap, so remaining capacity is a column, not a guess.
Advocacy Programme doc
The qualification rules, the point cost per ask type, the quarterly cap, and what happens after a decline, all in one place a requesting team can check before asking.
Ask Templates by Activity doc
One template per ask type, each built to open with the specific signal that put the advocate inside their ask window instead of a generic line.
Opportunity Matching sheet
Open requests filtered by segment, willingness and remaining points, with the match or the skip and its reasoning written on the row.
Activity Log sheet
The dated record of every ask actually sent, which team asked, and the signal it was timed to, if it had one.
How it works
- 1
Send your signals
Health, usage and satisfaction data for as much of the customer base as you have, not a pre-picked list of known-willing names.
- 2
River qualifies the bench
Every account clearing the health, tenure and active-save checks gets a row, with points used starting at zero unless prior asks this quarter are supplied.
- 3
Match or log each ask
A live request gets filtered against segment, willingness and remaining points before anything is sent; a completed ask gets logged and the register updates itself.
- 4
Check capacity before the next one
A quick pass over the register shows who is near the cap and who has gone unused, ahead of the next request rather than after it lands.
Frequently asked questions
Is this template free?
Yes. Two Word documents and three CSV sheets, downloaded as a zip, no signup. River is the optional half: it reads your health, usage and satisfaction signals, qualifies the bench, and is ready to match the first open request or log the first ask against a real signal.
What counts as a positive signal worth timing an ask to?
Three things: an NPS response of 9 or higher, a QBR that closes with a stated relationship score of 8 or higher, or a signed expansion. Each opens a 14-day window. A window that closes with nothing sent is logged as missed, and the advocate returns to the standing queue rather than getting a generic ask anyway.
What happens when nobody in the right segment has capacity?
The request stays open rather than getting forced through on an unrelated segment or a fatigued advocate. Opportunity Matching states which filter came back empty, so the team can decide to wait for the next quarter's reset, widen the segment, or flag it as a genuine exception.
Does a declined ask count against the quarterly cap?
No. A decline spends no points at all. It opens a 30-day cooldown on that advocate instead, during which no new ask goes out to them for any reason. Willingness moves to Maybe once the cooldown lifts rather than resetting straight back to Yes.
How is this different from a health score or NPS dashboard?
A portfolio health review or an NPS tool decides eligibility. This pack starts once an account already qualifies, then decides who to ask, with what, and when, so the same handful of known-happy names stop absorbing every request that fits their segment.
Can a sales rep still ask for a reference outside a signal window?
Yes, for a named prospect who actually needs one. That request is logged as an exception rather than blocked, because the signal-timing rule exists to pick a better moment for a discretionary ask, not to make a live deal wait for one.
Weight the ask before you send it
Send your health, usage and satisfaction signals. Get a bench with real capacity per advocate, and a request that times itself to a signal instead of a calendar.
Edit with AI