A healthy referral channel is a customer-success system with an acquisition output. It monitors value, timing, incentive cost, handoff speed, and the quality of the accounts it creates.
Do not activate the ask for unresolved accounts, weak activation, or unclear fit.
The dashboard begins with customer health and ends with downstream economics. Select a node to inspect the live operating rule.
Trigger the referral ask only after the customer can point to a real result, milestone, or avoided problem. Satisfaction language is weaker than evidence of value.
outcome → fit → permissionReferral prompts amplify the state of the relationship. If delivery is unstable, the customer is inactive, or a support issue is unresolved, the ask converts a hidden fault into a visible trust failure.
The account paid but cannot identify a result, completed milestone, or avoided problem. Correct the value path before requesting advocacy.
The customer has not used the offer recently or deeply enough to explain its fit. Use recent value as a trigger, not a reason to send more reminders.
Payment trouble, unresolved support, refund language, or a recent delivery miss should suppress the ask until the relationship is healthy again.
Health gate: a referral-ready customer has evidence of value, a plausible recipient, a stable relationship, and enough context to share the offer accurately. “Happy” is not a binary field; it is a set of operating observations.
The customer completes the first meaningful job and can describe the change.
The customer chooses to continue with a clear reason, not merely because switching is difficult.
The customer adds scope, access, or capacity because the original system is working.
A real service recovery is recognized by the customer; never use the request to hide the problem.
Review by trigger: compare initiation, qualified conversion, reward cost, contribution, and retention by the event that generated the ask. A trigger with fewer referrals can be better if it creates healthier accounts.
A referral incentive is a margin decision and a relationship decision. It should make the recipient’s next step easier without making the advocate feel as if the recommendation was purchased.
Test whether a useful recipient benefit increases qualified conversion and reduces perceived risk.
Use a clear credit, payout, or upgrade while monitoring quality and abuse.
Both parties understand what happens, when it happens, and what event unlocks the reward.
Access, service credit, training, or contribution can fit better than cash when internal cost is controlled.
Economic rule: maximum reward equals what the channel can sustain after delivery cost, sales effort, refunds, and expected retention—not what makes the headline look generous.
Advocate, recipient, consent, source, trigger, existing-lead status, and context.
Named owner, response window, and message context that prevents the recipient from starting over.
Fit, urgency, authority, capacity, problem, and next step. A completed form is not a qualified opportunity.
Outcome, reward trigger, contribution, retention, support load, and referrer health.
Weekly dashboard: eligible accounts, asks delivered, initiation, completed introductions, response SLA, qualified opportunities, close rate, reward liability, contribution after reward, referred retention, and referrer retention. If the number cannot be traced to an owner and a state transition, it is not yet a control metric.
A referral channel breaks when the ask is detached from value, the reward is detached from margin, or the lead is detached from a clear owner. The operating system has to protect both relationships: the advocate should feel accurate and generous, while the referred prospect should receive a relevant, low-friction introduction.
Check for a realized outcome, a current usage signal, an intact payment relationship, and the absence of unresolved service failure. Do not ask an unhappy customer to become your acquisition department.
Use a first win, renewal, expansion, resolved risk, or recent intensive use as the event that makes the ask natural. Record the trigger and compare quality by trigger.
Calculate reward cost against contribution, retention, and sales effort. Test recipient benefit, sender benefit, and two-sided structures without assuming the largest reward creates the healthiest channel.
Capture source, consent, fit, response time, duplicate status, opportunity stage, reward trigger, and customer quality. A referral is not a win when it disappears inside an inbox.
Before launching, define eligible customer states, ask triggers, message variants, frequency caps, recipient benefit, reward event, duplicate rules, owner, response SLA, attribution window, and the weekly scorecard. Measure referred-customer quality and referrer health, not just referral volume.
Gate on value, trigger on a real event, design from recipient benefit, and measure the handoff to durable customer quality.