The Email Opens the Door — The Call Walks Through It
Nobody fires their accountant over a cold email. Handing a stranger your books, your payroll, and your filing history is one of the highest-trust purchases a business owner makes, and high-trust purchases close in conversation — on a call, with a voice, usually after the prospect has checked who you are. Cold email is still the cheapest way to find the owners who are quietly unhappy; it's just rarely the channel that finishes the job.
That's why Reply.io is an unusually good fit for a firm. Its sequences aren't email-only: a single flow can hold email steps, call tasks, and LinkedIn steps, with conditions that trigger the next touch off the prospect's behavior. An owner opens the email twice — a call task lands on your task list. They view your LinkedIn profile back — the follow-up email references the connection. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs Reply.io actually sends from. This guide covers how to wire the two together and run the sequence the way accountants actually get hired — email to surface the pain, a recognizable face on LinkedIn, and a phone call timed to the week a filing deadline makes the pain undeniable.
Why Run Reply.io on ColdRelay Infrastructure
Reply.io is the orchestration layer: multichannel sequences that mix email, call tasks, and LinkedIn steps in one flow, contact management to keep every touch on the record, Jason AI to draft and triage responses, and a unified inbox where replies from every channel converge. What it doesn't do is provision the domains and mailboxes the email steps send from, or build their deliverability. That's the infrastructure layer's job — and in a sequence where the email's only job is to earn the call, a spam-foldered opener doesn't just lose a reply, it strands every call task and LinkedIn step queued behind it.
ColdRelay handles that layer. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, ready in about an hour. There's no warmup period to wait out before sending — warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup) — and 95%+ inbox placement means the engagement signals your call tasks trigger off are real signals, not artifacts of half the list never seeing the email.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Reply.io is the sequencing engine on top. You keep Reply.io's multichannel steps, conditions, and unified inbox — you just point the email channel at mailboxes built to land, so the rest of the sequence has something to work with.
Visit Reply.io →Connecting ColdRelay Mailboxes to Reply.io
Provision mailboxes on ColdRelay
Pick secondary domains adjacent to your firm's name — never the primary domain that carries your client portal and IRS correspondence. Because this motion is call-constrained rather than volume-constrained (a partner can only work so many call tasks a day), most firms run a lean fleet: 15-30 mailboxes covers it, and ColdRelay supports 100-150 mailboxes per domain if the practice scales. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Connect the mailboxes as email accounts in Reply.io
Export the mailbox credentials from the ColdRelay dashboard, then in Reply.io add each mailbox under Email Accounts via SMTP/IMAP. Each ColdRelay mailbox becomes its own sending identity that Reply.io rotates sequence emails across, and every reply routes back into the unified inbox alongside call outcomes and LinkedIn activity.
Set Reply.io's per-mailbox sending limits to 2 outbound a day
Reply.io exposes per-mailbox sending limits in each account's settings — set every connected mailbox to 2 outbound emails per day. That mirrors ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup, with the warmup half running continuously on ColdRelay's side. Don't enable any additional warmup for these accounts; the budget is already allocated.
Build the multichannel sequence with a call task on the engagement trigger
In the Reply.io sequence builder, structure the flow around behavior, not just delays: a LinkedIn profile-view step the day before the first email, the opener email, then a condition — prospects who open twice or click get a call task pushed to the assigned partner's task list, while everyone else continues down the email-and-LinkedIn track. Add a LinkedIn connection request after the first email so that when the call comes, the owner has already seen the CPA's face, credential, and local firm. The call task carries the contact's full touch history from Reply.io's contact management, so the partner dials knowing exactly what the prospect has seen.
Launch, and let Jason AI hold the inbox between call blocks
Activate the sequence and let Reply.io distribute email volume across the ColdRelay fleet. Between call blocks, Jason AI drafts responses to the routine replies — 'send me more info,' 'who are you again,' scheduling back-and-forth — and flags the genuinely interested ones in the unified inbox so the partner's phone time goes to live prospects, not email administration. Review the drafts rather than fully delegating: a tax question answered sloppily by an assistant is worse than no answer.
The Accounting Firm Reply.io Playbook
Treat the second open as a raised hand
An SMB owner who opens an email about their books twice in 48 hours is doing something specific: re-reading it, maybe forwarding it to a co-owner. That's the moment Reply.io's engagement conditions exist for — fire the call task then, not at a fixed day-7 step. The prospect who gets a call while the email is still on their mind treats it as follow-through; the one who gets it three weeks later treats it as telemarketing. Tune the sequence so calls chase engagement, and accept that most contacts will never generate a call task at all — that's the filter working.
Schedule call blocks to the filing calendar, not the sales calendar
The phone half of this motion should be lumpy on purpose. The weeks around March 15 (S-corp and partnership returns), April 15, September 15, and the October 15 extension deadline are when an owner's frustration with a slow or silent accountant peaks — and when 'I'm a CPA, want me to look at this before the deadline?' is a welcome interruption rather than a nuisance. Hold the partner's call blocks for those windows and let Reply.io accumulate call tasks in the run-up; in the dead weeks between deadlines, the email and LinkedIn steps keep working the list so the next pain week starts with a queue.
Use the LinkedIn step to make the caller a known quantity
The job of the LinkedIn steps in this sequence isn't engagement for its own sake — it's making the phone call warmer before it happens. A profile view before the opener and a connection request after it mean that by the time the call task fires, the owner has twice seen a real person: name, face, CPA license, a firm twenty minutes away. Cold calls from strangers get screened; calls from 'that local CPA who emailed me' get answered. Sequence the channels so LinkedIn always precedes the dial, and put the partner's actual headshot and credential on the profile doing the visiting.
Script the call as a deadline triage, not a pitch
When the call connects, the worst move is reciting the firm's services — the owner has heard that from every accountant who ever bought a booth at a chamber event. The call that converts is a two-minute triage keyed to the deadline that triggered the block: 'Has your current accountant confirmed your extension is filed?' or 'Do you know your Q3 estimate yet, or is that still pending?' If the answer is a sigh, offer one concrete next step — a 20-minute review of where things stand before the deadline. Log the outcome in Reply.io so the contact's record shows the conversation, and let the sequence's remaining steps handle the not-yets automatically.
Typical Accounting Firm Outbound Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — the engagement triggers that fire call tasks are only as good as the emails that land |
| Call tasks generated per 100 contacts sequenced | 10-20 | Engagement-conditioned triggers (double-open or click) — the filter that keeps partner phone time on warm prospects |
| Call connect rate in deadline weeks | 1.5-2x baseline | Calls placed in the run-up to March 15, April 15, and October 15 vs. identical lists in dead weeks |
| Email-only vs. email+call+LinkedIn conversion to consultation | 2-3x | Multichannel sequences out-convert email-only flows on the same lists — the call is where switching decisions actually happen |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
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). DNS, dedicated IPs, and isolated Azure tenants are included — and because this motion is capped by partner call capacity rather than send volume, most firms run a lean 15-30 mailbox fleet and stay in a modest tier.
Reply.io is billed separately on its own subscription for multichannel sequences, call tasks, LinkedIn steps, Jason AI, contact management, and the unified inbox — priced per its current plans.
Infrastructure cost scales with mailbox count; Reply.io's cost scales with seats and features. The split is clean — ColdRelay gets the opener into the inbox, Reply.io turns the engagement into a phone conversation — and a single retained engagement closed off a deadline-week call typically covers both bills for the year.
| 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, not competitors. Reply.io handles the multichannel sequences (email, call tasks, LinkedIn steps), contact management, Jason AI, and the unified inbox. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Reply.io's email steps send from. You use them together: infrastructure below, orchestration on top.
If the close happens on a call, why does email deliverability matter so much?
Because the whole sequence runs on email engagement signals. Reply.io's call tasks fire when a prospect opens twice or clicks — and if the opener lands in spam, that prospect never generates a signal, the call task never fires, and the LinkedIn steps are visiting someone who has no idea who you are. ColdRelay's 95%+ inbox placement on dedicated IPs and isolated Azure tenants is what keeps the trigger data honest, so partner phone time goes to genuinely engaged owners.
How many mailboxes does a call-driven motion actually need?
Fewer than an email-only one. The constraint is the partner's phone time, not send volume: at 2 outbound sends/day per mailbox (of the 4/day total, 2 outbound + 2 warmup), 20 mailboxes sequences roughly 800-1,000 contacts a month — which at typical engagement rates produces more call tasks than most partners can work in deadline weeks. Start lean, and scale the fleet only when the call queue runs dry; ColdRelay supports 100-150 mailboxes per domain when it does.
Can we launch before the next filing deadline if we're starting from scratch?
Yes. ColdRelay mailboxes provision in about an hour with SPF, DKIM, and DMARC pre-configured, and there's no warmup period to wait out — warmup runs continuously as 2 of each mailbox's 4 daily sends. Connect the accounts in Reply.io, set per-mailbox limits to 2 outbound a day, and the sequence can start the same day — which matters, because the email and LinkedIn steps need a couple of weeks of runway to build the engagement queue your deadline-week call blocks will work through.