Customer referral ask: a simple follow-up flow that gets introductions

Ask for customer introductions with a low-pressure message, clear fit criteria, and a respectful follow-up process.

Publication history

Originally published

Updated by Socialjuice Team

Editorial standards
Customer referral ask: a simple follow-up flow that gets introductions

A referral request works best when the customer knows who would benefit and can decide whether an introduction makes sense. “Send us anyone you know” shifts too much work onto them.

Define a useful introduction

Write a short description of the person you can help, the problem you solve, and a situation where your offer would be unsuitable. Give the customer enough context to protect their own relationship with the person they might introduce.

Ask after a genuine outcome

Start by checking how the customer is getting on. If they have reported a useful result and seem comfortable discussing it, ask whether they know someone facing a similar problem. A positive testimonial does not automatically mean the customer wants to make introductions.

Try: “If you know another [type of team] dealing with [problem], would you be comfortable introducing us? No pressure if nobody comes to mind. I can send a short explanation you can forward.”

Make the handoff optional

Provide a forwardable message and let the customer choose whether to send it. Do not ask for a private contact list or assume permission to contact a third party in the customer's name. After an introduction, thank them and manage the conversation directly.

Measure fit, not just names

Keep introductions, qualified conversations, and eventual customers separate. A referral is a lead, not booked revenue. If you run a referral-reward program, explain its terms clearly and consider how the relationship should be disclosed.

Keep referral requests separate from review collection. A person can share a testimonial without agreeing to participate in another acquisition campaign.

Good social proof starts with real experiences and permission to share them. Read our editorial standards.