hyreflow
Sign up
← all playbooks
Outreach

Build one cadence that moves between email, LinkedIn and the phone

A multichannel cadence built paused in your sequencer: emails, LinkedIn steps and call tasks in the order you chose, with each person loaded only into the steps their data supports. It runs when you start it, not before.

use when
one channel is not getting answers and you want a single cadence where a contact who ignores the email meets a LinkedIn touch and then a call
starts from
A list

The prompt

Paste it into Claude Code or the Claude desktop app with Hyreflow connected. The first line tells your agent to use Hyreflow, so it reads the play, asks before it spends anything, and hands the work back to you.

paste this into Claude
Use hyreflow and build one outreach cadence that mixes email, LinkedIn
steps and call tasks for a list I have ready.

The list is <FILE_PATH_OR_PASTED_ROWS>. These are
<CANDIDATES_OR_CLIENT_CONTACTS> and I am writing about <ROLE_OR_OFFER>.
Build it in <LEMLIST_OR_REPLY_IO>.

Before you build anything:
- Count what each row can support: email, LinkedIn URL, phone number.
- Take the channel from the row. No LinkedIn URL means no LinkedIn step for
  that person, and no phone number means no call task.
- Candidates get a personal email only, never a work address.
- Propose the order of touches and the gaps between them. I pick.

Then draft the messages in my voice: <TONE_OR_A_MESSAGE_I_SENT_BEFORE>.
The emails, a connection note with no pitch in it, a LinkedIn message, and
three talking points for each call task.

Run five first and tell me what the full run costs before you do the rest.
Stage it, do not send anything: build the cadence paused, load the people
and leave it idle. Tell me what fires on day one and how many call tasks
land on me each day. I start it myself.

Replace every <PLACEHOLDER> with your own detail. Everything else can stay as written.

What you need first

  • A qualified list, with whatever each row has: email, LinkedIn profile URL, phone number
  • A connected lemlist or Reply.io account, with your sending mailbox and LinkedIn account already set up in that tool
  • Whether these are candidates or client contacts, because that decides which email address is allowed
  • A Hyreflow workspace with credits, since drafting the messages is metered

Tools it can reach for

The agent picks per step from what your workspace has. Nothing here is required by name.

LemlistReply.iohyreflow AgentProspeoLeadMagicFullEnrichand more

What happens when you run it

Free steps are marked free. Anything that spends credits is marked, and the agent asks before the first paid run of any size.

  1. 1

    Sort the rows by what they can support

    free

    Every row is checked for an email, a LinkedIn profile URL and a phone number, and the list is split into tracks: all three channels, no LinkedIn, no email, LinkedIn only. For candidates a work address does not count as an email.

  2. 2

    Fill the gaps you choose to fill

    credits

    Optional. Missing emails go through a lookup chain that runs in a set order and stops at the first hit: work email for client contacts, personal email for candidates. Mobile numbers are separate paid lookups. The agent prices each before it runs.

    ProspeoLeadMagicFullEnrich
  3. 3

    Agree the order of touches

    free

    Two or three concrete shapes are proposed with their trade-offs, for example LinkedIn-led for candidates or email-led for client contacts, with the call placed where a person has already seen your name. You choose, and you set the gaps.

  4. 4

    Draft every message and the call notes

    credits

    The emails, a short connection note, the LinkedIn message and talking points for each call task, written so the channels read as one conversation. Five people are drafted first, then the agent prices the rest and waits.

    hyreflow Agent
  5. 5

    Build the cadence paused in lemlist

    free

    Email steps, a LinkedIn profile visit, a connection request, a LinkedIn message, call steps and manual tasks are created through the connection, with a branch on whether the request was accepted. The campaign is paused before the first step is added.

    Lemlist
  6. 6

    Or read the cadence you built in Reply.io

    free

    Through the Reply.io connection only email steps are documented, and it cannot link a LinkedIn account or manage tasks. So a mixed cadence is built in Reply.io itself, and the agent reads its steps back, checks the sequence is not running, and matches each step to the data it needs.

    Reply.io
  7. 7

    Load each person into the track their data supports

    free

    After you approve the lists, people are added with the fields each step uses. Someone with no LinkedIn URL goes into the track without LinkedIn steps, so nobody sits waiting on a step that cannot fire for them.

    LemlistReply.io
  8. 8

    Report day one and stop

    free

    You are told what fires on the first day on each channel and how many call tasks will reach you per day. The cadence is left idle. Starting it is a separate action, and it is yours.

What a run costs

Credits are spent per record the play actually works, and a lookup that finds nothing usually costs nothing. The two figures are the run where the first provider answers and the run where every lookup walks its full chain.

recordsif the first provider answersif every lookup walks the chain
25$9.898 credits$17170 credits
100$39390 credits$66660 credits
500$1951950 credits$3303300 credits
1,000$3903900 credits$6606600 credits

Free before anything is charged

  • Sort the rows by what they can support
  • Agree the order of touches
  • Build the cadence paused in lemlist
  • Or read the cadence you built in Reply.io
  • Load each person into the track their data supports
  • Report day one and stop

What moves the number

  • The channel. This play buys personal email, because these are candidates, and a work inbox is the wrong place to approach one. A personal address costs more to find than a work one.
  • Coverage on personal email. The chain stops at the first provider that answers, and only that provider bills.
  • How many records survive the free filters. Everything dropped before the paid steps costs nothing.
  • The scoring and drafting steps run on the metered agent, charged on what they read and write rather than per record, so they sit outside this table.
  • Providers you connect with your own key. Those calls bill your account, not your credits.

An estimate, not a quote, priced at the volume credit rate. Your agent sizes the run against your own workspace and tells you what it will cost before it spends anything.

The second channel reaches the people the first one missed

An unanswered email rarely means no. It usually means unread. People live in different inboxes: one never opens recruiter email and answers a LinkedIn message the same day, another has not logged in to LinkedIn since spring and picks up the phone on the second ring. A single-channel sequence keeps knocking on the same door. A mixed cadence tries the next one.

The catch is the data. A cadence drawn on a whiteboard assumes everyone has an email, a profile and a number. A real list does not. Put forty people with no LinkedIn URL into a cadence that opens with a profile visit, and what happens next depends on the tool: some skip the step, some stall. Either way the cadence you designed is not the one those people get.

So this play takes the channel from the row. It counts what each person can be reached on, builds the cadence you chose, and gives each person the version of it that their data can carry.

What you get back

A count of the list by track: all three channels, no LinkedIn, no email, LinkedIn only. The messages for every step, with talking points for each call. The cadence built in your sequencer and paused, one track per campaign, people loaded. And a plain description of day one: what goes out on each channel, and how many call tasks a day will land on your desk once it runs.

Variations worth knowing

LinkedIn-led for candidates. Visit, connection request, a message once they accept, then a personal email, then a call. LinkedIn is usually already on the row, and it is where a candidate expects the approach.

Email-led for client contacts. Work email first, a LinkedIn touch between the emails, and the call after they have seen your name twice.

Missing numbers. Find mobile numbers for a shortlist fills them before the build, so more people qualify for the call step.

Email or LinkedIn only. Build an outreach sequence covers the single-channel shapes and any other sequencer.

Where this goes wrong

More call tasks than you can make. Two hundred people reaching the call step in one week is two hundred tasks. Load in batches sized to the calls you will really make.

A work email on a candidate row. It is the wrong channel for someone you are asking to leave that employer. Those rows go to the LinkedIn track.

One message pasted into three channels. The email, the LinkedIn message and the call should each move the conversation on, not repeat it.

Stop on reply. Check in your sequencer that an answer on any channel stops the rest. The play does not change campaign settings.

LinkedIn limits. Daily limits on the connected LinkedIn account are set in the sequencer, not by this play.

Questions

Which step types can it create through the connection?

In lemlist: email, LinkedIn profile visit, connection request with or without a note, LinkedIn message, call step, manual task, and a branch on a condition such as the request being accepted. In Reply.io the connection can create a sequence with email steps and read the steps of any sequence, but it cannot link a LinkedIn account or manage tasks, so a mixed Reply.io cadence is built in Reply.io and loaded by the agent. HeyReach is LinkedIn only. Instantly, Smartlead and SendKit are email only.

Who makes the calls?

You do. A call step is a task that appears in your sequencer on the day it falls due. Nothing dials for you and nothing is said on your behalf. What the play adds is the talking points, written from what that person has already been sent.

What happens to someone with no LinkedIn profile or no phone number?

They get the version of the cadence their data supports. No profile URL means the email and call track, no number means no call task, and neither is guessed. If you would rather fill the gap first, the agent prices the lookup and you decide.

Does building it send anything?

No. lemlist hands back a freshly created campaign in a running state, so the agent pauses it first and confirms it is paused before a single step or person is added. In Reply.io it checks the sequence is not active before it enrols anyone. Starting is a separate action that only you take.

What does it cost?

lemlist and Reply.io run on your own accounts and use no Hyreflow credits. Sorting, building, loading and the day one report are free. Drafting is done by the Hyreflow agent and metered by usage. Filling missing emails or mobiles is a paid lookup, and a miss usually costs nothing. You get both figures after the five-person pilot.

Read next

Outreach

Load a HeyReach campaign at a pace that keeps the LinkedIn account safe

use whenyou have a list to approach on LinkedIn through HeyReach and you do not want the sender's account restricted because of it

HeyReachhyreflow AgentAI ArkProspeoLeadMagicLemlist
starts from a list · 8 stepsget the prompt →
Outreach

Review what your campaigns are doing and what to change next

use whencampaigns are running or finished across one or more sequencers and nobody has looked at which ones earn replies and which only use up the list

InstantlyLemlistSmartLeadReply.ioSendKitHeyReachSourceWhalehyreflow Agent
starts from a list · 8 stepsget the prompt →
Outreach

Build an outreach sequence without losing control of the send

use whenyou have the list and now you need a cadence built, loaded and ready, with nothing going out until you say so

LemlistInstantlySmartLeadSendKitReply.ioHeyReachSourceWhaleEnrichley
starts from a list · 6 stepsget the prompt →