How to route referrals and replacements in HubSpot

The warmest intro you'll ever get, disguised as a notification

Every other reply tells you something small. A referral reply hands you something big: a named, reachable person who owns the problem you sell into, plus an internal advocate who just vouched for you. "You should talk to Dana instead — I've mentioned you might be in touch" is not a dead end. It is the best lead your sequence will ever produce.

And it is the reply most teams handle worst. It reads like a notification, so it gets starred or forwarded instead of worked. The replacement's name lives in an email thread. The referrer — who just did you a favour — stays in the sequence, getting pitched the thing they already told you they don't own. The intro that should have been worked in an hour cools for a week, and by the time someone writes to Dana, she has forgotten she was ever mentioned.

The cost is invisible because nothing breaks. No bounce, no complaint, no angry reply — just pipeline that never got created. You only see it in hindsight: the deal a competitor closed with the person your own prospect told you to call.

The by-hand routine (how teams do it today)

Teams that handle this well without tooling all do a version of the same thing. It works — the cost is six careful steps done at inbox speed:

1. Spot the referral and read it closely. Extract the three facts that matter: the replacement's name, their role or area of ownership, and their email address if it was given. Note whether the referrer offered to introduce you or merely pointed you — it changes how you open.

2. Create the replacement as a new contact in HubSpot (Contacts → Create contact), with the name, email and title you were given. If the address wasn't volunteered, find it before you write — a guess that bounces wastes the warm intro.

3. Associate the new contact to the company — and to the open deal, if there is one. Open the contact, use the associations panel, and link them. If there is no open deal, this is the moment to create one (Deals → Create deal, associated to the new contact and the company): a referral is the strongest buying signal the account has produced, and a deal is what makes the intro count in pipeline reporting. Either way, this is the step that makes the referral real in your pipeline instead of real in your inbox.

4. Credit the referrer. Add a note on the new contact ("Referred by Marcus Calloway, Sept 2026") and update the original contact's Lead Status to your hand-off value — many teams keep a "Referred Elsewhere" option for exactly this. Do not delete or unenrol the referrer: they are an ally, not a loss.

5. Send the thank-you to the referrer. Two or three lines, no pitch — they are done, and the favour deserves a clean thank-you.

6. Send the first touch to the replacement the same day, naming the referrer in the first line. The intro has a shelf life measured in days, and the referrer already told them you'd be in touch — arriving a week late makes both of you look slow.

That routine takes fifteen minutes per referral done properly. Its failure mode is not refusal — it is that step 2 through 6 happen after the quote goes out, or on Friday, or never, and the warmest intro of the quarter dies as a forwarded email.

Keep the referrer — they're an ally, not a loss

The instinct to unenrol or delete the person who redirected you is the most expensive mistake in this whole workflow. Read the reply again: "the bid admin problem is real over here, so I hope she takes a look." That person is not a dead contact — they are a champion you haven't met yet. They confirmed the pain exists inside the account, and they put their name on your intro.

So the original contact gets updated, not removed. Lead Status moves to your hand-off value, the sequence either stops (because the conversation moved) or shifts to a light nurture, and the record keeps a note of the referral they made. When the deal with Dana closes — or stalls — Marcus is the person who tells you why.

This is also the honest difference between a referral and a departure. A contact who left the company is dead weight you clean up. A contact who referred you is a live relationship you maintain — and the two need opposite handling, even though the inbox makes them look identical.

Reply to both, the same day

The thank-you and the first touch are two separate emails to two separate people, and both belong in the same day the reply arrived. The thank-you is short and contains no pitch — the referrer handed you off because they wanted out of the thread, and dragging them back into it with a sales paragraph squanders the goodwill they just gave you.

The first touch opens with the referrer's name in the first line — "Marcus Calloway suggested I reach out" — because that name is the entire difference between a warm intro and a cold email. Then the shortest possible version of your pitch, the pain the referrer confirmed, and one clear ask.

What the first touch should never be is your original sequence email forwarded with "FYI" on top. The replacement knows nothing about your campaign, the forwarded thread reads as bulk mail, and the personal hand-off you were given gets spent on the laziest possible message.

What ReplyCircuit does with a referral

ReplyCircuit reads the reply the moment it lands and classifies it as a referral — which means it treats the message as two contacts and one hand-off, not a dead end. It extracts the replacement's name, role and email address verbatim, drafts the new contact with the company association ready, and logs the referral source on both records so the intro is attributable later.

It then applies your settings: the referrer's Lead Status moves to your chosen hand-off value — never deleted, never unenrolled by default — and the replacement contact is flagged for same-day outreach while the intro is warm. The review card shows the whole hand-off in one place: who referred, who owns it now, and what changed in HubSpot.

You approve the first few cards yourself; once the accuracy earns your trust, the routine work switches to automatic. The result is that the warmest reply you get all month stops depending on someone having fifteen careful minutes free at inbox speed.

What to expect afterwards

The first change is speed. Referrals that used to cool in a flagged folder get worked the day they arrive, and the replacement hears from you while they still remember being told to expect it. Warm intros convert on warmth — the same email sent five days later is just a cold email with a name attached.

The second change is the trail. Six months later, when the deal with Dana closes, the record shows where it came from — Marcus's name is on both contacts, and the referral is a reportable fact instead of something someone half-remembers. That is what turns "we sometimes get referred" into a channel you can actually count.