Agency Cold Email, Sold as Multichannel Pursuit
When a prospect compares three lead gen agencies and all three are selling "X emails per month," the cheapest one wins. The way out isn't sending more emails — it's selling something the email-only shops structurally can't deliver. Reply.io lets an agency run email, LinkedIn steps, and call tasks as one orchestrated sequence per client, which means the thing on your proposal stops being a send count and becomes a pursuit: every target account touched across three channels, in a deliberate order, until a conversation starts. That offer carries a different price tag.
This guide covers how to build that offer on the right foundation. Reply.io is the orchestration layer — multichannel sequences, Jason AI for reply handling, the unified inbox, per-client contact management. ColdRelay is the layer underneath the email lane: the secondary domains, mailboxes on isolated Azure tenants with dedicated IPs, and pre-configured DNS that Reply.io's email steps actually send from. We'll walk through wiring the two together, designing sequences where the channels hand off to each other, and pitching the result so the multichannel premium shows up in your retainers.
Why a Multichannel Offer Still Lives or Dies on Email Infrastructure
It's tempting to think a multichannel sequence de-risks email — if the inbox doesn't land, LinkedIn will. In practice it's the opposite: email is the only channel in the sequence that carries the full offer, the case study link, and the calendar ask. LinkedIn touches warm the prospect up and call tasks create urgency, but the step that converts attention into a booked meeting is almost always an email — and if that email lands in spam, the LinkedIn visit and the voicemail were spent setting up a message nobody saw. The more channels you orchestrate, the more expensive each undelivered email becomes.
Reply.io doesn't solve that, and isn't supposed to. It sends email steps from whatever mailboxes you connect; provisioning domains, configuring authentication, and owning IP reputation is the infrastructure layer's job. That's where ColdRelay fits: per-client mailbox pools on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, 100-150 mailboxes per domain, live in about an hour, running at 95%+ inbox placement. There's no warmup waiting period — warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), so the email lane of a new client's pursuit can launch the day they sign, right alongside the LinkedIn and call lanes.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Reply.io is the sequencing and orchestration layer on top of it. For an agency selling multichannel pursuit at a premium, the division is easy to explain to clients — Reply.io decides what touches each account and when, ColdRelay makes sure the touches that travel by email actually arrive.
Visit Reply.io →Standing Up a Multichannel Pursuit: ColdRelay Pool to Live Reply.io Sequence
Provision the client's email lane on ColdRelay
Size the mailbox pool to the email steps only — in a multichannel pursuit, LinkedIn and call touches carry part of the cadence, so the email lane is leaner than an email-only campaign hitting the same accounts. At 2 outbound sends/day per mailbox (4/day total, split 2 outbound + 2 warmup), a client pursuing 500 accounts with 3 email steps each over a month needs roughly 25-30 mailboxes. Order secondary domains echoing the client's brand — ColdRelay supports 100-150 mailboxes per domain, so one domain usually covers it — and the pool is live on an isolated Azure tenant with dedicated IPs in about an hour, DNS (SPF, DKIM, DMARC) pre-configured.
Connect the mailboxes in Reply.io and set per-mailbox sending limits
In Reply.io, add each ColdRelay mailbox under Email accounts via SMTP/IMAP using the credentials exported from the ColdRelay dashboard. Then use Reply.io's per-mailbox sending limits to cap each account at 2 outbound emails per day, mirroring the ColdRelay budget — 4 sends/day total per mailbox, 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's side as part of that budget, so skip any additional warmup on these mailboxes and let the sequence start immediately.
Load the client's accounts into Reply.io's contact management
Import the client's target account list and segment it inside Reply.io's contact management — by persona, account tier, or territory — so the same pursuit logic can run with different copy per segment. Tag every contact with the client's code; when you're running multichannel sequences for a dozen clients at once, clean contact hygiene in one place is what keeps a call task for Client A from ever surfacing next to Client B's follow-ups.
Build the sequence so the channels hand off to each other
This is the product. In Reply.io's sequence builder, interleave the step types so each channel sets up the next: a LinkedIn profile view and connection request first, then the opening email from the ColdRelay pool a day later, then a call task for contacts who opened but didn't reply, then a LinkedIn message referencing the voicemail, then the closing email with the calendar link. Each touch raises the odds the next one gets a response — the compounding is the reason multichannel pursuit outperforms the same touches fired on separate tools by separate people.
Turn on Jason AI and staff the unified inbox by exception
Enable Jason AI to handle first-pass replies — it categorizes responses, drafts answers to common objections and scheduling back-and-forth, and flags the conversations that need a human. Replies from every channel land in Reply.io's unified inbox, so your team works one queue per client instead of toggling between a mail client, LinkedIn tabs, and a call log. The operating rule: Jason AI clears the routine, humans take anything tagged interested within business hours.
The Multichannel Pursuit Playbook: Reply.io + ColdRelay for Agencies
Put the pursuit map in the proposal, not a send count
Email-only competitors quote volume because volume is all they have to show. Your proposal should show the sequence itself: a diagram of the 8-10 touches each target account receives across email, LinkedIn, and phone, in order, over three weeks. Prospects can compare send counts on price; they can't price-shop an orchestrated pursuit they've never been offered before. Agencies that sell the map consistently close above email-only quotes for the same account list — the premium is paid for the orchestration, and Reply.io is what makes the orchestration deliverable rather than aspirational.
Use Jason AI as your reply-handling capacity, and price the humans for conversations
Multichannel pursuit generates more replies per account than email alone — that's the point — and reply handling is where agency margins usually leak. Let Jason AI absorb the categorization, the not-interested closeouts, and the scheduling ping-pong, and reserve human time for live conversations with interested prospects. That staffing model changes your unit economics: the same account manager can carry more clients because the inbox work is triaged before they see it, and the hours you do bill are spent on the part clients actually value.
Branch the sequence on cross-channel signals, not just email opens
The compounding only happens if the channels react to each other. Build Reply.io sequence branches that read signals across lanes: an accepted LinkedIn connection should pull the next email forward; a completed call task with no answer should trigger an email referencing the voicemail; a prospect who clicked but went quiet should get a LinkedIn message instead of a fourth email. A sequence where every contact gets the identical fixed cadence is just three silos running in parallel — the premium offer is the one where touch four knows what happened at touch three.
Report meetings per account pursued, and break out which channel landed them
An outcomes-priced retainer needs outcomes-shaped reporting. Track each client's pursuit as accounts entered, accounts engaged (any-channel response), and meetings booked — then attribute which channel produced the breakthrough touch. That last cut is your renewal weapon: when the report shows a third of meetings started on LinkedIn or by phone, the client sees exactly what the multichannel premium bought them over the email-only agency they almost hired, and the retainer conversation starts from value rather than from rate-card pressure.
Typical Multichannel Pursuit Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated Azure tenants carrying the email lane of each pursuit |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, with warmup running continuously |
| Meeting rate vs. email-only sequences | 1.5-2.5x | 8-10 orchestrated touches across email, LinkedIn, and phone per account; uplift varies by ICP seniority and list quality |
| Retainer premium over email-only proposals | 30-60% | Priced on the pursuit map and per-account outcomes rather than monthly send volume |
| Time to launch a new client's pursuit | Same day | ColdRelay pool provisions in ~60 minutes; sequence build and contact import in Reply.io fill the rest of the day |
What It Costs: Reply.io + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). Multichannel pursuits run leaner email lanes than email-only campaigns — LinkedIn and call touches carry part of each cadence — but every client's pool still totals into one agency bill, so a multi-client book reaches the cheaper per-mailbox tiers quickly. DNS, dedicated IPs, and isolated Azure tenants are included.
Reply.io is billed separately on its own subscription, with multichannel sequence steps, Jason AI, and the unified inbox gated by plan tier — priced per its current plans.
The two bills map to the two layers: Reply.io's cost scales with seats and orchestration features, ColdRelay's scales with the email lane's mailbox count. Because the offer is priced on multichannel outcomes while the infrastructure footprint per client stays modest, the spread between what a pursuit bills and what its stack costs is wider than anything an email-only volume retainer can produce.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Reply.io handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Reply.io?
No — they're complementary layers. Reply.io handles the orchestration: multichannel sequences combining email, LinkedIn steps, and call tasks, Jason AI for reply handling, the unified inbox, and contact management. ColdRelay provides the infrastructure underneath the email lane — the domains, mailboxes, and dedicated IPs that Reply.io's email steps send from. Agencies use them together: ColdRelay for the infrastructure, Reply.io for the multichannel sending on top.
Do LinkedIn steps and call tasks count against the per-mailbox email budget?
No. Only email steps send through the ColdRelay mailboxes, and those are governed by the per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. LinkedIn steps and call tasks run on their own channel limits inside Reply.io. That's part of the multichannel economics: a pursuit can put 8-10 touches on every target account while the email lane stays inside a modest, sustainable sending budget.
Do I need a warmup period before launching a client's first sequence?
No. ColdRelay mailboxes warm continuously as part of the per-mailbox budget — 4 sends/day total, 2 outbound + 2 warmup — so there's no waiting period before email steps can fire. Provision the pool (about an hour, with SPF, DKIM, and DMARC pre-configured), connect the mailboxes in Reply.io, cap each at 2 outbound emails per day with Reply.io's per-mailbox sending limits, and the pursuit can launch the same day the client signs.
How many mailboxes does a multichannel client actually need?
Fewer than an email-only campaign against the same list, because LinkedIn and call touches carry part of the cadence. Work backward from the email steps alone: at 2 outbound sends/day per mailbox, a client pursuing 500 accounts with 3 email steps each over a month needs roughly 25-30 mailboxes, which fits comfortably on a single domain — ColdRelay supports 100-150 mailboxes per domain. Scale the pool when the client adds accounts or email steps, not when they add channels.