How to set up a customer referral programme

“Feel free to recommend us.” A customer likes your service but does not know what to share, with whom or for which benefit. A referral programme turns this vague invitation into a clear journey. Both the referring customer and the person invited should understand the rules without contacting your team.

Table of contents

Summarise the whole article in one click with AI:

Summarise with AI

Start with the recommendation you want to facilitate, then choose the reward, validation conditions and tracking. A gift cannot compensate for a disappointing experience or an incomprehensible scheme.

What should your referral programme achieve?

A customer recommends your business using a link, code or invitation. The referred person follows a defined journey. Depending on the programme, a reward may go to the referrer, the new customer or both.

Choose a primary goal: acquiring suitable customers, introducing a service or developing a use case. Loyalty programmes reward an existing relationship; referral programmes depend on recommending your business to someone else. They can coexist with different rules.

Reviews are different again. Someone can leave a review without referring anyone, or make a recommendation without publishing a testimonial. Satisfaction helps but does not prove customers know someone with the right need.

Choose suitable participants and timing

Invite customers who have had time to appreciate the product or service. Completing an order does not always mean a successful experience. Pending delivery or an unresolved support problem can make the invitation premature.

The right moment might follow a completed service, a useful first outcome or verified positive feedback. These are possible situations, not automatic triggers available in every tool. Validate data, communication rules and technical capabilities.

Define who may refer: individuals, companies, account holders or another specified group. For B2B recommendations, check employer policies and restrictions before offering personal benefits to employees. A business programme needs appropriate terms rather than a copy of a consumer scheme.

Choose a useful, sustainable reward

A reward might be a discount, credit, service or another genuinely available benefit. Consider its value to the customer and cost to your business. Large promotional wording cannot make an irrelevant benefit useful.

Reward the referrer

Recognise the recommendation with a clear benefit after the stated condition is met.

Benefit the new customer

Make discovery easier without hiding first-order or contract conditions.

Offer both

Create shared value while checking the combined cost and margin.

Calculate the full cost: both benefits, platform fees, administration, delivery where relevant and returns. The face value of a discount is not the entire programme cost. Check whether it attracts suitable customers or merely opportunistic transactions.

Do not copy another company’s rewards without understanding its economics. Subscriptions, bookings and physical products have different margins and repeat-purchase patterns.

What triggers the reward?

Separate an invitation, registration, first order, payment and final validation. Choose an event matching the goal and risk. Rewarding registration may suit some schemes but does not demonstrate customer acquisition.

If a confirmed first purchase is required, say so before sharing. Explain cancellations, returns, unpaid orders and validation timing. Do not introduce an undisclosed waiting period after participation.

Write conditions participants can actually understand

Compare models before choosing

Different products and goals call for different models. Compare them on paper before configuring a system. Existing and referred customers must both understand the benefits.

Possible models to adapt, without prescribed reward amounts
ContextPossible modelQuestion to resolve
Online productsBenefits after a validated first orderHow are returns and already-planned orders handled?
BookingsBenefits after the booking takes placeWhich statuses distinguish booking, completion and cancellation?
SubscriptionCredit following an explicit activation or payment conditionHow do you avoid rewarding unused accounts?
B2B servicesRecommendations reviewed as relevant opportunitiesWhich benefits are acceptable to companies and employees?

These are not ready-to-publish terms. Explain changed booking dates, partial returns or the period covered by subscription credit. Customers may compare schemes, but you do not have to copy the biggest reward. Explain your own system clearly.

Summarise key rules on the programme page and link to full conditions. Make important decisions visible before participation rather than hiding them in a long document.

  • Who may refer and who may join as a referred customer.
  • What makes someone an eligible new customer.
  • How to use the link or code.
  • Which event validates the referral.
  • Benefits, limits and delivery timing for each participant.
  • Cancellation conditions and how to challenge a decision.
  • Data use and the support contact.

Explain duration and combination restrictions. If a referral code cannot combine with a promotion, say so. Define attribution when several people refer the same customer instead of leaving support to improvise.

Do not promise an immediate reward if checks remain. Consistent terms across the page, sharing message and status information build trust.

A link or code, followed by a predictable journey

A link can open the explanatory page directly. A code may suit spoken or offline recommendations. Either way, make it easy to find the benefit and check its application.

The referring customer needs to understand the scheme, obtain the sharing element and know what follows. The invited person needs the offer, conditions and expected action. Test mobile too: a code that is hard to copy or hidden conditions create friction.

A sharing message example

The wording must reflect the person’s actual experience. Do not write a false review for them or ask them to conceal a possible reward. Recommendations should remain voluntary and transparent.

Choose a proportionate tool

A small scheme can begin with controlled tracking where volume and risk allow. A referral platform helps when attribution, rules and reward delivery exceed what the team can reliably manage. It does not decide what a valid referral means.

Check codes, statuses, exports, controls, permissions and actual integrations. Test a complete referral before launch. Verify any advertised synchronisation in your own configuration.

Protect data and handle suspicious cases fairly

The simplest route is often to let customers share a link themselves, allowing the recipient to decide whether to visit and participate. Avoid address-book imports feeding a prospecting campaign.

For operations in France, the CNIL explains restrictions on contact details provided through referrals. Using them for further messages requires express consent. Have your setup and notices checked before launch.

Define cases needing review: prohibited self-referrals, multiple accounts, codes shared outside the intended scope or cancelled orders. An unusual signal is not proof of fraud. Provide human review and a way to challenge a reward refusal.

Collect only the data needed. A referrer can know their reward status without seeing the invited person’s detailed purchases. Programme transparency is not permission to disclose personal information.

Promote the programme without exhausting customers

Provide clear access where customers look for information: a dedicated area, help page, appropriate communications or a conversation with your team. Explain the benefit and link to terms without interrupting every use.

Coordinate with other messages. Avoid renewed invitations after refusal or during an unresolved service problem. Consider total marketing pressure across channels.

The role of Web Push

Web Push can introduce subscribers to the programme page. A push notification gives a reason to read while benefits and rules remain verifiable on the destination page.

Our standard retargeting uses pages viewed or URL elements. It does not automatically know whether someone is a referrer, referred customer or reward beneficiary. When you promote a referral programme with Web Push, do not assume individual eligibility. Personal validation messages need a separate, verified setup.

Measure validated referrals, not just invitations

Assign statuses and responsibilities

Separate registrations, pending conditions, validation and benefits delivered. Assign owners for reviewing records and, where needed, accounting. Marketing explains the scheme, sales handles relevant opportunities and support clarifies progress. One person may cover these roles in a small business, but responsibility must remain clear.

Prepare response templates without exposing the invited person’s data. Customers need their participation status, not a friend’s purchase history. Document corrections and explain how technical failures are reviewed. Do not quietly change rules after participation.

Check the experience before expanding

Ask test customers to explain the benefit, find the code and describe what they would tell a friend. Check whether invited people understand the offer, eligible products and next step. Test desktop and mobile sharing without requiring an application customers do not have.

Pilot goals should be observable: understanding, completion, validation tracking and delivery of promised benefits. A small scope can reveal plenty before wider rollout.

Track exposure, participating referrers, sharing where measurable, registrations, first purchases and validated referrals. These numbers are not interchangeable. An invitation is not acquisition.

Always name the denominator of a rate: invited customers participating, registered invitees buying or records validated. Otherwise teams may use incompatible “referral rates”.

  • Active referrers and validated referrals by period.
  • New customers acquired under your rules.
  • Total reward and administration costs.
  • Revenue and margin including returns and cancellations.
  • Questions, complaints and reward delivery times.

Compare referred customers with a relevant group without assuming every coded order is incremental. Someone may already have intended to buy. Technical attribution and real contribution are different.

Run a pilot before wider promotion

Test finding the link, understanding the offer, recording the order and applying the reward. Include cancellation and support requests. Expand after fixing ambiguity. A sustainable programme depends on easy recommendations and promises kept, not message volume.

Customer referral questions

Which reward should I choose?

A useful, sustainable benefit such as a genuine discount, credit or service. Include both sides’ benefits, administration and returns in the cost. Do not copy another scheme without checking your economics.

Should the invited customer benefit too?

It may make discovery easier, but it is not a universal requirement. Choose according to goals and cost, and explain each benefit’s conditions.

When should a referral be validated?

At the event defined in your terms: registration, confirmed first purchase or another relevant condition. Separate participation from final validation and explain returns and cancellations.

How can I limit abuse?

Use explicit criteria, proportionate monitoring and review. A signal is not proof. Allow challenges and avoid collecting excessive data.

Can I ask customers for friends’ email addresses?

Do not turn referrals into address-book imports. A link shared by the customer lets recipients choose. If you collect details indirectly, have applicable rules and notices checked.

Can Web Push distribute rewards automatically?

Not through standard retargeting based on pages viewed or URLs. It can link to the programme page. Eligibility, referral tracking and reward delivery need a specific setup.

Make your referral programme easier to discover

See how Web Push helps subscribers find your programme information and participation conditions.

Request a demo
📤 Share: