Designing a Measurable Referral Programme Across Branches

The operating problem

Referral programmes can reward loyal customers, but unclear rules create disputes over who referred whom, whether a lead already existed and which branch receives credit. A chain-wide programme should protect the customer experience while making reward eligibility and cost understandable to central marketing and local teams.

Build the location-level control

Define the qualifying event—completed first purchase, attended appointment or activated service—plus eligibility, self-referral exclusions, reward timing, cancellation treatment and caps. Use a referral identifier through enquiry, booking and transaction. Decide in advance whether credit follows the referring branch, fulfilling branch or central programme; each rule answers a different question.

Field scenario

A fitness chain rewards members whose friends join. A prospect attends a trial at one club and purchases at another after moving city. Without a shared identifier, both clubs claim the conversion. The company establishes one programme record, a published credit rule and a cancellation window before calculating rewards.

Measure what changes

Monitor referral-to-qualification rate, duplicate flags, reward reversals, dispute resolution time, cost per qualifying customer and repeat purchase. A high referral count can mask low-quality leads or reward leakage; pair volume with conversion and contribution.

Questions to settle before rollout

Should the first branch always receive credit? Not necessarily; define whether credit follows origin, fulfilment or programme rules. Should a flagged referral be rejected automatically? No; review evidence and apply published terms consistently.

Topic-specific operating note

Explain eligibility before a customer shares a referral code. If a reward is delayed, provide status and a route to query it. Avoid disclosing another customer’s transaction while investigating duplicates. Consistent rules are more sustainable than ad hoc exceptions offered to the loudest complainant, and a clear dispute process reduces branch workload.

Branch-side reference notes

Control record: Define the qualifying event—completed first purchase, attended appointment or activated service—plus eligibility, self-referral exclusions, reward timing, cancellation treatment and caps. Use a referral identifier through enquiry, booking and transaction. Decide in advance whether credit follows the referring branch, fulfilling branch or central programme; each rule answers a different question.

Example to test: A fitness chain rewards members whose friends join. A prospect attends a trial at one club and purchases at another after moving city. Without a shared identifier, both clubs claim the conversion. The company establishes one programme record, a published credit rule and a cancellation window before calculating rewards.

Performance evidence: Monitor referral-to-qualification rate, duplicate flags, reward reversals, dispute resolution time, cost per qualifying customer and repeat purchase. A high referral count can mask low-quality leads or reward leakage; pair volume with conversion and contribution.

Decision question: Should the first branch always receive credit? Not necessarily; define whether credit follows origin, fulfilment or programme rules. Should a flagged referral be rejected automatically? No; review evidence and apply published terms consistently.

Field checklist for branch owners

Problem to recognise

• Check: Referral programmes can reward loyal customers, but unclear rules create disputes over who referred whom, whether a lead already existed and which branch receives credit.
• Check: A chain-wide programme should protect the customer experience while making reward eligibility and cost understandable to central marketing and local teams.

Control to apply

• Check: Define the qualifying event—completed first purchase, attended appointment or activated service—plus eligibility, self-referral exclusions, reward timing, cancellation treatment and caps.
• Check: Use a referral identifier through enquiry, booking and transaction.
• Check: Decide in advance whether credit follows the referring branch, fulfilling branch or central programme; each rule answers a different question.

Scenario to test

• Check: A fitness chain rewards members whose friends join.
• Check: A prospect attends a trial at one club and purchases at another after moving city.
• Check: Without a shared identifier, both clubs claim the conversion.
• Check: The company establishes one programme record, a published credit rule and a cancellation window before calculating rewards.

Evidence to review

• Check: Monitor referral-to-qualification rate, duplicate flags, reward reversals, dispute resolution time, cost per qualifying customer and repeat purchase.
• Check: A high referral count can mask low-quality leads or reward leakage; pair volume with conversion and contribution.

Question to resolve

• Check: Should the first branch always receive credit?
• Check: Not necessarily; define whether credit follows origin, fulfilment or programme rules.
• Check: Should a flagged referral be rejected automatically?
• Check: No; review evidence and apply published terms consistently.

Local operating note

• Check: Explain eligibility before a customer shares a referral code.
• Check: If a reward is delayed, provide status and a route to query it.
• Check: Avoid disclosing another customer’s transaction while investigating duplicates.
• Check: Consistent rules are more sustainable than ad hoc exceptions offered to the loudest complainant, and a clear dispute process reduces branch workload.

Extra branch checks

• Check: Define the qualifying event—completed first purchase, attended appointment or activated service—plus eligibility, self-referral exclusions, reward timing, cancellation treatment and caps.
• Check: Use a referral identifier through enquiry, booking and transaction.
• Check: Decide in advance whether credit follows the referring branch, fulfilling branch or central programme; each rule answers a different question.

Signals to inspect

• Check: Monitor referral-to-qualification rate, duplicate flags, reward reversals, dispute resolution time, cost per qualifying customer and repeat purchase.
• Check: A high referral count can mask low-quality leads or reward leakage; pair volume with conversion and contribution.