Outreach & follow-up
Draft a forwardable B2B referral introduction with AI
Give a willing customer a short introduction they can edit, without inventing praise or assuming the recipient wants outreach.
Make the introduction easy while leaving the relationship and decision with the people involved.
Editorial workflow guide · AI-assisted preparation · Not a hands-on product test. How we work
Check whether an introduction is appropriate
Start with a real relationship and a customer who has expressed willingness to help. Read the account’s current delivery status before asking for a favor. An unresolved implementation problem may need attention before a referral conversation. Do not have AI infer satisfaction from a payment, a short thank-you or an account health score.
Define the relevant business situation and the offer you can actually support. Ask for an introduction to someone dealing with that situation, rather than demanding a list of names. Keep any customer performance claim out unless the customer approved it for sharing. A referral request is different from permission to publish a testimonial or enroll the referred person in a campaign.
Sponsor
SPONSORED
AI FOR YOURSales team.Less busywork.More selling.
Your team knows sales.
We help put AI to work.
Prepare two drafts with different jobs
The first draft asks the customer whether an introduction would be comfortable. The second is a short forwardable note they can adapt if they choose. Give the AI a factual offer statement, the relevant problem, the rep’s identity and one modest next step. Tell it not to speak as though the customer has already endorsed the company.
For a fictional provider, an internal draft could offer help organizing sales follow-up and ask whether a colleague facing that problem would welcome a conversation. The forwardable note could say: I thought this might be relevant to the follow-up process you mentioned. Would you like me to introduce you? That asks first and does not claim the provider produced results for the customer.
Keep the evidence and boundaries beside the draft
Provide the reviewing rep with the actual willingness-to-introduce note and any approved customer wording. Label the forwardable text as a draft for the customer to edit. Do not insert confidential project details, commercial terms or another person’s private email address just to make the introduction look specific.
If an introduction happens, confirm what each person actually agreed to and identify the account owner before responding. A copied email thread can include people who were not intended to become sales contacts. Use existing contact preferences and your organization’s outreach process. Do not launch a sequence or send repeated reminders because the referral draft has been prepared.
Judge the handoff by relevance rather than volume
HubSpot’s sales-email guidance discusses referral timing and providing a prewritten introduction. Our two-draft workflow adds an explicit review boundary and a separate record of what the customer permitted. It is a proposed process, not a feature inside HubSpot and not a claim that referrals convert at a particular rate.
Try a small set of appropriate, owner-reviewed requests. Track whether the customer found the request easy to understand, whether the introduction was welcomed and whether the recipient’s situation fit the offer. Count declines and no responses honestly. Do not label every name mentioned as a qualified lead, or turn an informal introduction into a public endorsement without a separate agreement.
A prompt to adapt
Using the supplied relationship notes and approved offer, draft (1) a short request asking whether an introduction would be comfortable, and (2) an optional forwardable note for the customer to edit. Keep praise and results only if explicitly approved. Ask one modest next step. List missing permissions separately. Do not send, invent relationships or add recipients to outreach.
Use fictional or anonymized examples while testing. Add your approved business rules before using a draft.Source documents
Primary sources support the references above. These workflows are editorial suggestions; confirm current product availability, pricing, permissions, and integration details directly.
Questions or corrections?
See our editorial policy for how we distinguish workflow suggestions, vendor statements, and tested results.