Consent-Based Referrals: Ask for an Introduction Without Damaging Trust

Referrals are powerful for a small company because they transfer part of an existing relationship's trust. A vague or automated request can instead turn a satisfied customer into an address book. Consent-based referral protects the customer, the referred person and the company.

Choose the right moment

Ask after observable value, not immediately after signup. The trigger might be a measured outcome, fast resolution, voluntary renewal or spontaneous positive feedback.

Respect the current relationship. A customer managing an incident should not contribute to acquisition even if generally satisfied.

Make a precise request

A useful request states:

• who may benefit;
• the concrete problem addressed;
• why that profile comes to mind;
• that there is no obligation;
• a ready-to-forward message;
• what happens after the introduction.

Avoid “do you know anyone?” It creates too much cognitive load and offers no targeting help.

Two layers of consent

The customer first agrees to forward a message or check interest. The referred person then chooses whether to engage. Do not automatically place their contact details in a CRM without an appropriate basis and notice.

The customer should not make promises on your behalf. Give them an accurate sentence that is easy to edit.

The seven-step workflow

1. Detect an outcome or satisfaction signal.
2. Confirm that no incident or sensitive matter is open.
3. Identify a precise profile, not necessarily a name.
4. Ask permission without disproportionate incentive.
5. Provide a short forwardable message.
6. Let the recipient choose the next step.
7. Thank the customer, provide a restrained update and do not chase through them.

A forwardable message

“We used [solution] for [specific problem] and achieved [verifiable outcome]. I thought the topic might be relevant to you. I can introduce you if useful; no problem if not.”

The text hides neither the commercial relationship nor uncertainty about fit.

Measure quality

Track requests made after an outcome, customer acceptance, genuinely consented introductions, replies, qualified conversations, conversion and referred-person satisfaction.

Do not reward volume alone. It can encourage weak or unwanted introductions. If an incentive exists, make it transparent.

Automate carefully

The product can detect a moment, draft a message and remind a user. It should not automatically message the customer's network. Keep explicit review and let the customer choose the person and channel.

The CRM should distinguish suggested, authorized, forwarded and accepted referrals. “Lead created” is not consent.

Fact, inference and hypothesis

Direct fact: an introduction puts the referrer's reputation at stake.

Inference: asking after proven value and providing a precise message reduces effort and improves relevance.

Hypothesis to test: fewer, better-contextualized requests create more qualified conversations than broad referral campaigns.

FAQ

Is a reward required?

No. If one exists, disclose it and avoid incentives that encourage irrelevant introductions.

Can the introduction email be automated?

Draft it, but let the referrer review it, choose the recipient and send it.

When should a referral not be requested?

During an incident, before an outcome, in a sensitive relationship or after the customer has declined.

Next step

Write one consent-based referral workflow from a real customer outcome. To design the messages and tracking without spam, email contact@yumea.fr with the subject “REFERRAL.”