Engineering the Discovery Call, Run Through Reply.io
Coaching has an unusual sales funnel: nothing is sold in writing. No coaching engagement closes over email — the email's entire job is to produce a discovery call, and the call does the selling. Which means a coach's outbound sequence shouldn't be measured in replies at all. A warm, friendly reply that never turns into time on the calendar is a near miss, not a win — and most email-only sequences are full of exactly those near misses, because once the reply arrives there's no mechanism for converting interest into a booked slot.
Reply.io is built for closing that gap. Its sequences combine email, LinkedIn steps, and call tasks in one flow — so familiarity gets built before the ask, the email makes a low-friction calendar ask, and a call task fires to pick up the prospects who engaged but never clicked the booking link. Jason AI and the unified inbox handle the scheduling back-and-forth in between. ColdRelay is the infrastructure underneath the email steps: the secondary domains, mailboxes, and dedicated IPs Reply.io actually sends from. This guide covers how to wire the two together so the path from first touch to booked call has no dead ends.
Why Run Reply.io on ColdRelay Infrastructure
Reply.io is a sending and sequencing platform — its email steps send from whatever mailboxes you connect, while its LinkedIn steps and call tasks run through your own LinkedIn account and phone. It doesn't provision domains or guarantee the deliverability of the mailboxes themselves; that's the infrastructure layer's job.
In a calendar-engineered sequence, the email step carries a unique load: it's the only step in the flow that can deliver the booking link at scale. The LinkedIn touches build recognition and the call task rescues stragglers, but the calendar ask itself travels by email — and if that email lands in spam, the funnel has a hole exactly where the conversion happens. ColdRelay mailboxes run on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC), live in about an hour, with 95%+ inbox placement — so the one step that carries the link actually reaches the inbox.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Reply.io is the sequencing layer on top. You keep Reply.io's multichannel steps, Jason AI, and unified inbox — you just give the email steps mailboxes built to land.
Visit Reply.io →Connecting ColdRelay Mailboxes to Reply.io
Provision mailboxes on ColdRelay
Pick a secondary domain adjacent to your coaching brand and provision your pool. ColdRelay supports 100-150 mailboxes per domain, but calendar-engineered coaches run lean — 10-25 mailboxes is typical, because every email step is flanked by LinkedIn touches and call tasks that take real time per prospect. Everything goes live on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Connect the mailboxes as Reply.io email accounts
In Reply.io, go to Settings → Email Accounts and connect each ColdRelay mailbox via SMTP/IMAP using the credentials from the ColdRelay dashboard export. Each mailbox connects as its own sending account, so Reply.io can rotate email steps across the pool while your LinkedIn steps and call tasks stay tied to your one identity.
Set per-mailbox sending limits to 2 outbound/day
In each email account's settings, set Reply.io's per-mailbox daily sending limit to 2 outbound emails. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's side as part of that budget, so there's no waiting period before your first sequence and nothing extra to enable in Reply.io. LinkedIn steps and call tasks don't touch this budget at all.
Build the multichannel sequence pointing at the calendar
In the Reply.io sequence builder, order the steps as a booking funnel: a LinkedIn profile view and connection request on days 1-3 to make your name familiar, the first email step on day 4-5 making a single low-friction ask — one specific question plus the booking link — then a follow-up email, and finally a call task that triggers only for prospects who engaged (replied, accepted the connection, or clicked the link) without booking. Every step exists to move the prospect one stage closer to time on your calendar.
Turn on Jason AI and import contacts
Enable Jason AI to categorize incoming replies by intent — interested, objection, scheduling question, not now — so the unified inbox sorts itself and the scheduling back-and-forth gets drafted for you. Then import your prospect list through Reply.io's contact management, map your personalization fields, attach all connected mailboxes, and launch. At 20-50 sends/day, the sequence fills your call-task list within the first two weeks.
The Calendar-Engineering Reply.io Playbook
Count booked calls per hundred prospects, not replies
Replies are an input; discovery calls are the product. Set your Reply.io dashboard ritual around one ratio — booked calls per 100 prospects sequenced — and work backwards from it: if calls are low but replies are healthy, the leak is between reply and booking (fix the ask or the call task); if replies themselves are low, the leak is upstream (fix targeting or the LinkedIn warm-up). Coaches who optimize reply rate often just get better at collecting polite near misses. The funnel metric keeps every edit honest.
Run the call task as a booking-catcher, never a cold call
A cold call from an unknown coach is a hang-up. But a five-minute call to someone who accepted your connection request, replied 'this looks interesting,' and then went quiet is a different conversation — they already know who you are, and the only agenda is putting time on the calendar. Configure the call task in Reply.io to trigger only on engagement signals without a booking, keep it to one attempt plus a voicemail that names a specific slot, and treat it as the step that converts the warm-but-unbooked middle of your funnel — typically the largest group a sequence produces.
Let Jason AI play scheduler so you can play coach
The distance between 'happy to chat' and a confirmed slot is usually three tedious emails about time zones — and every hour that thread sits idle, the prospect cools. Let Jason AI draft the scheduling replies and answer logistical questions the moment they arrive, while anything with substance — an objection, a question about your method, a story about their situation — gets routed to you in the unified inbox to answer personally. The division is clean: the machine handles the calendar mechanics fast, and the prospect's first real conversation with you happens where it should — on the discovery call.
Sequence past the booking to kill the no-show
For a coach, a no-show is worse than no booking — you've reserved the hour, prepped for the person, and lost both. So don't end the Reply.io sequence at the booked call; end it after the call happens. Add a confirmation email step that fires once a prospect books, asking one light pre-call question ('what's the one thing you'd want this call to solve?') — a prospect who answers has invested in showing up — plus a morning-of reminder touch. Two more steps in the builder, and the show-up rate moves more than any subject line ever will.
Typical Calendar-Engineered Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Discovery calls booked per 100 prospects | 3-6 | The metric that matters; multichannel sequences outbook email-only flows on the same list |
| Reply-to-booked-call conversion | 35-55% | Fast scheduling handling plus the call task catching warm-but-unbooked prospects |
| Show-up rate with confirmation steps | 75-85% | Pre-call question + morning-of reminder, versus roughly half without them |
| Mailboxes per coach | 10-25 | 20-50 outbound sends/day at 2 outbound per mailbox (4/day total, 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, IPs, and isolated Azure tenants are included — and at calendar-engineered volumes of 10-25 mailboxes, the infrastructure line stays small.
Reply.io is billed separately on its own subscription for the multichannel sequences, call tasks, Jason AI, and unified inbox — priced per its current plans.
Infrastructure cost scales with mailbox count; Reply.io's cost scales with seats and plan features. For a coach, the combined stack is the cost of a machine that turns a niche list into booked discovery calls — and since the calls are where engagements close, one client typically covers the stack many times over.
| 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 and this whole setup uses both. Reply.io is the sequencing layer: the multichannel flows, LinkedIn steps, call tasks, Jason AI, and the unified inbox. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs Reply.io's email steps actually send from. Reply.io engineers the path to the discovery call; ColdRelay makes sure the email carrying the booking link reaches the inbox.
Do Reply.io's LinkedIn steps and call tasks count against my mailbox send budget?
No. Only email steps send from ColdRelay mailboxes, within the 4 sends/day-per-mailbox budget (2 outbound + 2 warmup). LinkedIn views and connection requests run through your own LinkedIn account, and call tasks run through your phone — neither consumes a single email send. That's part of the appeal for coaches: two of the three channels in the booking funnel are effectively free of deliverability risk, and the one channel that isn't runs on infrastructure built for it.
Do I need to wait through a warmup period before launching my first Reply.io sequence?
No. ColdRelay mailboxes warm continuously as part of the standard send budget — 4 sends/day per mailbox, split 2 outbound + 2 warmup — so there's no waiting period before sending. Provision in about an hour, connect the mailboxes under Settings → Email Accounts, cap each at 2 outbound/day, and your first sequence can start the same day. Don't enable a separate warmup tool on top; warmup is already handled at the infrastructure layer.
Should the booking link go in the very first email?
In this setup, yes — because by the time the first email sends, it isn't really a first touch. The LinkedIn steps ran days earlier, so the prospect has seen your name and face before the ask arrives, and hiding the link only adds a round trip for people ready to book. The safety net for everyone else is built into the sequence: Jason AI handles the scheduling back-and-forth for repliers, and the call task picks up prospects who engaged but never clicked. The link being present costs nothing; the link being absent costs your fastest bookings.