Learn / Funnels and follow-up
The cold email follow up strategy behind 170 calls in 30 days
Over 170 calls booked in the last 30 days, and almost none of them came from sending another email. A cold email follow up strategy that works is not a longer sequence with more "just bumping this" touches. It is three channels fired in the right order once a real person raises their hand: email to get the reply, a phone call within minutes of it, then LinkedIn so you stop being a stranger.
After booking over 3,000 calls in the past year, the pattern is boring and consistent. Volume gets you the reply. The next five minutes decide whether it becomes a meeting. Most pipeline leaks right there, between interested and signed, and all anyone sees later is "the leads were bad."
This is the written version of the training below: the channel order, how we measure speed to lead, the exact call and voicemail scripts, the objection lines, and the plumbing behind all of it.
The order is the strategy
Nobody on earth books 50 calls a month from cold email alone. The fix is chaining mechanisms, each channel doing the one job it is good at. Email opens the door. The phone call books the meeting while intent is still live. LinkedIn makes sure the next unknown number that rings has a face attached to it.
Order matters more than the channels do. Calling or connecting with someone who never answered your first email is a colder version of the same work at a higher cost per touch. Every leg below is triggered by one thing: a reply tagged interested.
| Channel | Fires when | The job it does |
|---|---|---|
| The campaign runs | Opens the door and earns the reply. Short, relevant, with a real insight attached. | |
| Phone | An interested reply lands, inside 5 minutes | Books the meeting while they still remember writing back. |
| The same reply, automatically | Turns you from an unknown caller into a name they have seen. |
Speed to lead, measured in business hours
We aim to reply within 5 minutes of a lead showing interest. Not same day, not "first thing tomorrow." Five minutes, because a reply is a window rather than a lead record, and a prospect who waits hours for an answer is a cold lead who once remembered you.
Measure it honestly: the median gap between the reply landing and your first touch, counted in business hours. Business hours matter because an interested reply at 11pm on a Friday should not score as a weekend-long failure, and averages hide the one lead that sat all week. Median, business hours, per rep.
The mechanism is a webhook on the sending tool. When a contact gets tagged interested, it pushes to Clay, gets enriched, and lands in Slack as a single alert carrying the campaign name, the company, the prospect's email, website, LinkedIn profile, mobile number, and the reply itself with the threaded quoting stripped out. The rep reads the alert and calls. No CRM tab, no copy and paste, no hunting for a number.
The number arrives formatted as a link, so calling is one tap. That sounds like a detail worth skipping. It is not. Typing a number by hand on every reply is the small friction that quietly pushes your response past the 5 minutes you were aiming for.
Volume gets you the reply. Speed gets you the meeting.
The warm call, word for word
Once the call goes through there are two outcomes, and both have a script. If they do not pick up, keep the voicemail quick and make it obvious this is a reply to their reply:
Voicemail: "Hey {first name}, this is {rep name} with {company}. Saw your email just now to my boss about {the offer}. Shoot me a call back when you can, happy to give you more information."
If they answer, open with their first name as a question. It is a pattern interrupt. Every other call they take that day opens with "hi, this is so and so from," and the name-as-a-question gets a yes out of them before they have decided whether to be annoyed with you.
Live call: "{first name}?" Wait for the yes. "Hey {first name}, this is {rep name} with {company}. You answered an email from my boss about {the offer}. Does that sound familiar? Awesome. There are only a couple of slots left on his calendar this week, but would a quick intro Tuesday at 1 or Wednesday at 3 Eastern work for you?"
Two named times, not "when are you free." When they take one, run a few qualification questions before booking: "just so we can make sure the chat is efficient and relevant, mind answering a couple of questions before I put this in?" Skip them if the prospect is short on time. Otherwise the person taking the call needs that context to know whether the call is worth anyone's hour, which is the whole subject of pre-call qualification. Then the rep books them into the calendar of whoever runs the meeting.
When they say "just send me more information"
This is the objection that eats the most booked calls, and it means two completely different things. Sometimes it is a polite brush-off. Sometimes there is one specific thing they genuinely want to know. So ask.
The question: "For sure, {first name}, and was there anything specific you were looking to get more information about?"
Then play innocent on purpose. The rep gives their honest partial answer and hands the rest to whoever takes the call, because if the rep had every answer the meeting would not be necessary in the first place.
The hand-off: "Got it. I'd say {short answer}, but I imagine {founder name}would give you a better answer than I can. Instead of sending you over a generic question and answer PDF, do you have 15 minutes Tuesday? I can tell him that's what you want to focus on."
That is sales resistance removed rather than overcome. They are agreeing to 15 minutes on the one thing they already said they cared about, not to a pitch. If the answer is still no:
The deferral:"No problem, I'll send that over right after this call. One thing I like doing is throwing a short touch point on the calendar a few weeks out as a reminder to follow up. Does that work for you?"
Worst case, there is a real meeting on a real calendar. There is a chance they show, and if they do not, you have a legitimate reason to reach out again. That beats a CRM task nobody actions.
LinkedIn last, and passive on purpose
Warm calls only work when people pick up, and most people do not answer numbers they do not recognize. That is the entire reason LinkedIn is in this system. The first thing a real buyer does after replying is look you up, so give them a face to attach to the next call.
A second webhook on the same interested trigger pushes the prospect through Clay and into a HeyReachcampaign, which sends the connection request with NO message attached. Across thousands of connections sent, the bare request gets accepted most: a note on a stranger's request reads like a pitch before there is any reason to hear one. The campaign also views the profile and likes a post or two, small human-looking actions that lift acceptance.
When they accept, nothing else fires. No message sequence, no follow-up DM. Nobody likes being sold to, and the passive version works anyway: for the first couple of weeks after a connection, your content gets pushed into their feed. Familiarity builds itself, which is also why catching the anonymous site visits that follow a reply is worth wiring up next.
The plumbing that makes it automatic
None of the above runs without data, and the data is the part people skip. You cannot call without a mobile number, and you cannot send a connection request without a LinkedIn URL, which lead lists frequently do not carry. So Clay sits in the middle as the hub every interested reply passes through. Six steps, in order:
- Receive the webhook. One trigger on the sending tool, fired when a contact is marked interested. Payload: campaign name, first name, last name, full name, company, email, and the LinkedIn URL if you already hold it.
- Fill the LinkedIn gap. An AI agent takes the full name and company and searches for a URL matching the linkedin.com/in pattern. When it cannot find one, it returns no profile found instead of guessing.
- Extract the raw reply. Pull just the body text out of the email, without the headers or the previously threaded messages, so what hits Slack is clean and readable at a glance.
- Waterfall the phone number. Providers run sequentially and stop at the first hit. Order the ones you hold your own API keys for first so you spend credits last, then merge every returned mobile into one column.
- Format for one tap. A quick formula rewrites the number into a click-to-call link inside the Slack alert. This is the step that protects the 5 minutes.
- Push to LinkedIn. The same row goes back out to the HeyReach campaign with first name, last name, LinkedIn URL, company, and email attached.
Running enrichment only on interested replies, instead of on an entire prospect list, is what keeps this affordable. You are paying for data on people who already told you they want to talk, which is a very different spend from enriching a whole table of strangers and hoping. If the replies are not arriving in the first place, that is a campaign problem, and the tips that fix reply rates are upstream of every word on this page.
One honest caveat. This is the exact system we use to consistently book over 100 calls a month from cold email, and the one behind a two-person firm whose previous vendor produced nothing booking 42 qualified conversations in its first 30 days. But every platform here has a learning curve, and the automations are the easy half. The hard half is a human who actually calls within 5 minutes.
tl;dr: email earns the reply, a phone call inside 5 minutes earns the meeting, and LinkedIn makes the next call land. Automate the routing and the data, never the part where someone picks up the phone.
FAQ
How fast should you follow up on a cold email reply?
Inside 5 minutes while the prospect still has your email open. A reply is a window, not a lead record, and it closes fast. The practical way to hit that is an alert that fires the moment a reply is tagged interested, carrying the phone number and the reply text, so the rep never opens a second tool to start working it.
What do you say when you call someone who replied to a cold email?
Open with their first name as a question, then: this is me with the company, you answered an email from my boss about the offer, does that sound familiar. Confirm the email, then go straight to two specific times. Skip the introduction paragraph. They replied minutes ago, so the call needs to sound like a follow-up, not a cold pitch.
Should you send a LinkedIn connection request with a note?
No. Across thousands of connections sent, the plain request with no message gets accepted most. A note reads like a pitch before there is any reason to hear one. Send the request bare, view the profile, like a post, and let your content do the familiarity work once they accept.
How do you handle a prospect who asks you to just send more information?
Ask what specifically they wanted more information about. That one question separates a real question from a polite brush-off. Then answer partially, hand the full answer to whoever takes the call, and offer 15 minutes on that exact point instead of a generic document. If they still decline, put a short touch point on the calendar a few weeks out.
Do you need Clay and HeyReach to run multi-channel follow-up?
You need something that receives the interested webhook, finds a mobile number, and pushes the prospect into a LinkedIn queue. Clay and HeyReach are how we do it, but the work is enrichment and routing, not the logos. Start with the alert and the phone call, which need almost no tooling, and add the LinkedIn leg once the calling habit sticks.
If you would rather have the whole thing built for you, webhooks, enrichment, alerts, scripts, and a rep working the replies, that's what we do: an outbound system pointed at your ideal customer, booking calls inside 30 days. Or keep learning free. Every training, grouped by topic, sits on the trainings hub, and the full video for this one is on YouTube.
PS - most of this system runs without anyone touching it. The 5-minute call does not. If nobody is watching that Slack channel during the day, do not build any of it yet, build the habit first.