Set a cooldown for referral requests. Cap customer-level asks at one or two asks per customer per quarter, and hold quarterly conversations with referral sources to generate regular, reliable referrals.1, 2 Track those two cadences separately. A calendar can set the review point. Check the customer's readiness and history of prior asks before sending anything.
Set the rule
Put the rule where you can check it before writing the next request. This keeps decisions consistent while leaving room for a new customer signal.
Make a new referral request only when necessary.3 Use the customer cap as a hard stop, and track it separately from the referral-source cadence. A referral program should determine when and how often to ask for referrals.4
Keep a per-customer record of the last request, its outcome, and whether an introduction is still pending. That history helps distinguish a new opportunity from repeated pressure.
Run the check
Before each ask, check these in order. Stop at the first failed check and leave the request closed until a new reason appears.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Readiness | whether the customer's recent experience gives you a reason to ask | "What has been most useful so far?" |
| Moment | whether this is a receptive point for a referral request | "Would this be a good time to ask about someone else who might benefit?" |
| History | whether the cooldown allows another request | "When did we last ask you for a referral?" |
| Pending | whether an earlier request needs a review instead of a new ask | "Should I follow up on the introduction, and when?" |
Use the result to choose the next action: wait on a weak readiness signal, hold a request at a poor moment, stop at the cap, or schedule a review for a pending request instead of creating a fresh ask.
Choose the moment
A frequency rule needs a trigger. Use a customer event or a clear sign of positive sentiment to decide when the next eligible request should happen.
Ask customers immediately after purchase whether anyone else can benefit from their decision.5 Businesses should not wait after a B2B software purchase decision.6 This gives you an entry point for the initial request; the cap controls later requests.
For later requests, look for moments when positive sentiment and willingness to refer are likely to be high.7 Check whether the audience is receptive to a message and likely to act on a referral call to action.8, 9 Excellent customer experience is a prerequisite for positive sentiment toward a brand.10
Use a post-purchase survey to screen for readiness. Ask only customers who give a positive experience rating to refer others.11 That keeps the request tied to the customer's experience instead of sending it to everyone on the same schedule.
Manage pending requests
A pending request needs its own review point. Follow-up timing should protect the cooldown and give the customer room to respond.
Set a reminder interval for pending requests.12 Use it to check the request status, the last ask, and whether a new reason exists. Following up too soon can make the referral experience feel transactional.13
If the request is still pending when the reminder arrives, review the record before contacting the customer. The reminder marks when to inspect the request. Check the record for a new reason before making another ask.
What not to do
These mistakes turn a useful cadence into repeated pressure.
- Keep requests to the same person infrequent.14
- Wait when a reminder fires but the request is still too recent. Following up too soon can make the referral experience feel transactional.13
- Filter the survey by positive experience rating before asking for a referral.11
- Make new requests only when necessary.3