How to find customers to ask for referrals
Learn how to find customers to ask for referrals, check relationship and request history, and write an introduction request that's easy to decline.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What makes a customer a good referral candidate
To find customers to ask for referrals, look for current customers who can point to a specific benefit they received and who have a relationship with someone on your team. Then decide whether the timing and the proposed introduction make sense. A customer who confirmed a successful rollout might be a fit for an introduction to a peer planning a similar rollout. The account owner still needs to check for open issues, contact restrictions and earlier requests before making the ask.
The result is a shortlist of referral candidates with the evidence, relationship owner and proposed ask for each. A warm introduction is a connection the customer chooses to make between you and someone they know. Describe whom you can help and let the customer decide whether anyone comes to mind. Where a relationship is unclear or service needs attention, give the team a specific internal action.
What it does for the business
- Give account owners a list they can act onAn owner can open the source, see what the customer achieved and judge whether a conversation fits. The team can work through the queue during account reviews and assign verification tasks to the right teammates.
- Help customers recognize a relevant introductionDescribe a specific peer and the problem you solve. If the customer makes an introduction, the recipient has enough context to decide whether to talk.
- Direct attention to accounts that need serviceA review can surface an unresolved complaint alongside strong historical feedback. Assign the service issue and confirm what the customer needs before asking for a favor.
- See where referral work actually stallsTrack requests, introductions and sales steps separately. Use that history to improve whom you ask, clarify whom you help or follow up on introductions.
How to find customers to ask for referrals, step by step
Match current customers to documented outcomes
A referral candidate needs a success the customer can recognize.
What to do
- Set a review date and define which current customer accounts are in scope. Confirm the account, contact and relationship owner against your authorized records, especially when several companies share a parent or contacts have similar names.
- Read the source behind each promising signal. Look for a dated milestone acceptance, a customer-confirmed result, a specific thank-you, renewal feedback about a benefit or documented progress against a shared success plan.
- Record exactly what the source supports and who said it. Keep a measured result, a customer's description and an internal impression distinct. Treat usage, invoice payment and tenure as background when you lack a documented outcome.
- Check that the person had a connection to the outcome and that the experience relates to the offer you want introduced. Set aside an anonymous response or a shared billing inbox until you can verify a suitable relationship.
Why
An account can have heavy usage and still struggle to get results. Matching the outcome to the recipient keeps you from opening with a claim they cannot recognize and gives the owner a source to check.
Check account health, restrictions and earlier asks
Every referral request needs a current relationship check.
What to do
- Read recent service and billing records alongside account-owner notes. Check for a material complaint, a dispute, a failed delivery or a request to pause. If the records are incomplete, assign a verification action before treating the relationship as clear.
- Check the scope of every contact restriction. A stop that covers the account still applies when a contact changes. Use the actual scope of a channel restriction when deciding whether any proposed route is appropriate.
- Read the referral ask history and any rules that govern another approach. Keep an unanswered or refused request visible, and send any genuine new evidence to the owner for reconsideration. A renewal alone gives you no basis to repeat a refused ask.
- Mark an account ready to ask only when the positive outcome, suitable relationship, approved offer and audience, current clearance and request history all support that decision. Give blocked and unclear cases one concrete internal action.
Why
Positive feedback and a current dispute can both be true. Check both before asking for a favor. The last request date also helps a teammate recognize a repeat ask when preparing a fresh list.
Build the owner queue and keep the history
A useful queue tells each owner what to do and what evidence supports it.
What to do
- Give each row stable account and contact identifiers and name the approved offer and intended audience. Record the dated outcome, relationship source, relevant restrictions and prior ask evidence so an owner can trace the decision.
- Assign one next action to each row. Ask the owner to confirm the draft, verify a contact, check whether a service issue is resolved or leave a prior request alone. Assign an owner before treating an unowned row as ready for outreach.
- Keep dated records of actual requests, refusals and replies. Enter a draft as a draft. Record an introduction only when it happens, and update an opportunity only when the relevant sales records support that event.
- Compare the proposed queue with the last relevant review. Reconsider a case when the underlying relationship, issue or customer response changes. Keep previously declined or unanswered asks visible even when a new export uses different wording.
Why
The owner needs to know what to do now. The next reviewer needs to know what already happened and what changed. Distinct records for drafts and responses keep earlier requests visible when someone rebuilds the list.
Write a specific request that is easy to decline
The customer should be able to understand the favor and decline it in one reading.
What to do
- Open with a brief reference to the documented outcome, using words the customer would recognize. Keep the wording within what the evidence supports, especially when your source is a milestone acceptance or an attributed comment.
- Describe the kind of peer or organization and the problem your approved offer solves. Ask if the customer would feel comfortable making an introduction or forwarding a note. Give them a simple way to pass without an explanation.
- Write a separate forwardable note if it saves the customer work. Describe the offer and whom it helps in language a recipient can understand. Leave the customer's private results, spend and internal details out of the forwarded text unless you have permission.
- Use incentive language only when you have approved terms and can state the actual eligibility and expiry. Have the owner read the draft for accuracy and tone before using it in a conversation or email.
Why
A broad request leaves the customer to work out whom you serve and how to explain your offer. Specific referral request emails give them a manageable choice. A separate note lets you acknowledge an experience privately and give the customer something they can share.
Review the decisions with the relationship owners
The relationship owner needs enough evidence to stand behind each request.
What to do
- Reconcile the queue to the relationships reviewed. Keep a disposition for each relationship in scope, check for duplicates and state which records and dates the review covers.
- Reopen each proposed ask beside its sources. Check the customer's identity, outcome, current relationship, restrictions and request history, then read both the ask and the forwardable note as their intended recipients would.
- Give each owner the draft and the observation that supports it. If the owner knows of a recent issue or customer reply, update the record and reconsider the request before anyone acts.
- Report when a complete review yields no suitable asks. If the review is missing current outcome, contact or blocker evidence, tell owners which sources to verify and hold the affected requests.
Why
A shortlist can conceal gaps in source coverage. Checking each row shows whether its evidence is current enough to act on. An empty result helps the team close the review when the right action is to wait or resolve an issue.
Common mistakes
- Using a high survey score as the whole caseCheck who answered, what they experienced and whether your current relationship supports a request.
- Assuming an issue is closed when it disappears from an exportConfirm resolution in a complete current source or have the owner verify it.
- Repeating an unanswered ask after a new exportKeep the previous request visible and use meaningful new evidence or the applicable contact rules to reconsider it.
- Asking for anyone the customer knowsGive the customer a recognizable type of organization and the problem your offer can address.
- Putting private results in a note meant to be forwardedKeep customer details in the private conversation and describe the offer in the shared note.
What a good result looks like
- Each reviewed relationship has a visible disposition and a clear next action.
- Each proposed ask traces to a documented outcome, a suitable contact and current clearance.
- Each row identifies the relationship owner or records that one must be assigned.
- Each draft specifies the type of introduction requested and makes it easy to decline.
- Each prior request, refusal or response remains visible when the list is refreshed.
And then what? Using the result
- Review the Ask rows with the account owners and let them check the timing and wording before making any request.
- Assign the open service and billing issues behind Resolve first rows and record how you confirm that each one is resolved.
- Give Verify rows to the person who can check the contact, source coverage or relationship, then revisit those decisions when the evidence arrives.
- Record requests, declines and introductions when they happen so the next review starts from the actual history.
- Share recurring customer outcomes with sales and customer success to help them describe the kinds of problems your offer has solved.
When to run it
- After customers confirm useful outcomesA rollout acceptance or progress review gives the owner a specific experience to mention. Check the current relationship before asking.
- When you define a new referral audienceCheck which customers have relevant experience with the approved offer and a suitable relationship. Bring earlier asks into the review.
- When several teams already make referral requestsA shared history lets account owners see earlier requests and gives them one place to record replies.
Questions people ask
How do you find customers to ask for referrals?
Start with current customers who have a documented positive outcome and a suitable relationship with your team. Check current issues, contact restrictions and previous requests. Keep the cases where you can describe a relevant introduction and identify who should review the ask.
When is the best time to ask a customer for a referral?
Ask after the customer recognizes a specific benefit and the owner confirms the relationship is clear. A service problem, dispute, pause or prior refusal can still put the request on hold.
Can you ask for a referral without a customer referral program?
Yes, you can make a personal request for a relevant introduction when the outcome, relationship and timing support it. Use an approved offer and audience, give the customer room to decline and leave out rewards unless you have approved terms.
What should referral request emails include?
Include the outcome behind the request, the kind of peer you can help, a clear favor and an easy way to decline. Keep any forwardable text separate and describe the offer without sharing the customer's private information.
Can you ask again if a customer declined or never replied?
Keep a declined or unanswered request closed unless your applicable rules and the actual relationship evidence support reconsideration. An explicit invitation to make another introduction can give an owner a reason to reopen it after current checks. Keep the original event in the history.
Does 10folds send the referral requests?
Sending stays with your team. 10folds prepares local drafts for the relationship owner and shows the source and next action for each reviewed relationship.
More jobs in Sales & outbound
Find customers to ask for referrals, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac