Engineering the Walkthrough Booking, Run Through Reply.io
For most SEO agencies, the deal isn't won in the inbox — it's won on the audit walkthrough call, the 20 minutes where a site owner watches you explain what's broken on their own site and decides you're the one to fix it. Which means the sequence has exactly one job: get that call booked. Not 'start a conversation,' not 'send the audit' — booked, on the calendar, with a show.
Reply.io is the rare sequencer built for that framing, because it treats email, LinkedIn, and phone as steps in one flow rather than three separate tools. An audit-teaser email creates the itch, a LinkedIn touch makes the sender a credible human before the ask, and a call task converts the prospect who's clearly engaged but hasn't clicked the booking link. What Reply.io doesn't provide is the sending infrastructure underneath — that's ColdRelay: the secondary domains, mailboxes, and dedicated IPs your sequences actually send from. This guide covers wiring the two together around a single conversion point: the booked walkthrough.
Why Run Reply.io on ColdRelay Infrastructure
A booking-first sequence is a chain, and the email step is its first link. The LinkedIn touch only lands if the prospect already saw the teaser; the call task only makes sense against a prospect who opened and re-opened the email. If the first email goes to spam, the entire multichannel architecture collapses into a stranger cold-calling about an audit nobody saw. Deliverability isn't one metric among many in this motion — it's the load-bearing wall.
ColdRelay is built to hold that wall. You provision mailboxes on secondary domains — never your agency's primary — hosted on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour. There's no warmup waiting period before sequences can start: warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), and placement holds at 95%+. With 100-150 mailboxes supported per domain, one order covers a multi-vertical booking motion.
The pairing is additive, not competitive: Reply.io is the sequencing layer — multichannel flows, Jason AI on replies, the unified inbox, per-mailbox sending limits. ColdRelay is the infrastructure layer those flows send from. The walkthrough call only happens if step one reaches the inbox.
Visit Reply.io →Connecting ColdRelay Mailboxes to Reply.io
Size the mailbox order backward from walkthrough targets
Start from calls, not sends. If you want 15 booked walkthroughs a month and your funnel books roughly one walkthrough per 60-80 prospects sequenced, you need about 1,000-1,200 prospects/month entering sequence — call it 2,500-3,000 email sends on a booking-focused cadence. At 2 outbound sends/day per mailbox (each mailbox's budget is 4 sends/day total, split 2 outbound + 2 warmup), that's 50-70 mailboxes. ColdRelay supports 100-150 mailboxes per domain, so one secondary domain covers it; everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Connect the mailboxes in Reply.io and cap per-mailbox sending limits
Export your mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard. In Reply.io, add each mailbox under Email Accounts via SMTP/IMAP, then use Reply.io's per-mailbox sending limits to cap each account at 2 emails per day — mirroring the ColdRelay budget of 4 sends/day total per mailbox (2 outbound + 2 warmup). Leave warmup to ColdRelay; it already runs continuously, and a second warmup layer spends sends without improving placement.
Build the multichannel sequence around the booking
In Reply.io's sequence builder, lay out the steps so each channel does one job. Step 1: the audit-teaser email — one specific finding from their site and the offer to walk through the rest live, with the booking link. Step 2: a LinkedIn profile view, then a connection request, so the name on the email becomes a person with visible client results before the follow-up. Step 3: a second email that answers the unspoken objection ('this isn't a sales call — it's the audit itself, screen-shared'). Step 4: a call task that Reply.io surfaces only for prospects showing engagement — multiple opens or a link click without a booking — so dials go to people who already know who's calling.
Put Jason AI and the unified inbox on reply duty
Replies from every mailbox land in Reply.io's unified inbox — one queue across 50-70 sending addresses. Configure Jason AI to triage them: it categorizes intent, drafts responses, and can push interested prospects toward the calendar while you sleep. Keep one rule human, though — any reply that mentions their site specifically gets a personal answer within the hour, because that prospect is already halfway to booking and a templated response can talk them back out of it.
Segment contacts by vertical and read channel analytics per segment
Use Reply.io's contact management to tag every prospect with a vertical — e-commerce, local services, B2B SaaS — and run each vertical as its own sequence copy. Reply.io's analytics then show you bookings by channel within each vertical: which segments book from the email link, which only convert after the LinkedIn touch, and which need the call task to close the booking. That report is the steering wheel for the whole motion — review it weekly and rebalance steps per vertical instead of running one universal cadence.
The SEO Agency Reply.io Playbook
Sell the walkthrough, not the audit
The most common audit-outreach mistake is attaching the deliverable: a PDF audit the prospect skims, forwards to their developer, and never replies to. The booking-first version withholds it deliberately — the teaser email shares exactly one finding ('your category pages are competing with each other for your highest-volume keyword') and makes the live walkthrough the only way to see the rest. The audit becomes the meeting agenda instead of the attachment, and the email's only CTA is the calendar link. You're not asking them to evaluate an agency; you're asking them to watch someone explain their own site for 20 minutes — a much easier yes.
Run the LinkedIn step as a credibility deposit before the second ask
Site owners don't book calls with email addresses; they book with people they've sized up. Reply.io's LinkedIn steps slot that sizing-up into the sequence: a profile view after the teaser email plants the name, and a connection request — sent from a profile whose featured section shows ranking screenshots and named client wins — lets the prospect do their due diligence in one glance. By the time the second email's booking link arrives, it's coming from someone they've already half-vetted. The step's job isn't to pitch on LinkedIn; it's to make the calendar ask land as 'that SEO person who found the cannibalization issue' rather than 'unknown sender, third email.'
Reserve the call task for prospects whose behavior says yes
Cold-calling a raw list is the worst use of an SEO founder's afternoon. A Reply.io call task fired on engagement is a different activity entirely: the prospect opened the teaser three times, clicked the booking link, and stalled at the calendar — the dial isn't a cold call, it's an assist on a booking already in motion. Keep the script to one job: 'You looked at the audit walkthrough times and something didn't fit — want me to just find a slot now?' Ten minutes of these calls a day converts the warmest sliver of the list that email alone leaves on the table, and Reply.io queues them for you so nobody has to maintain a dial list by hand.
Let per-vertical channel data redesign the sequence, not just the copy
Most agencies A/B test subject lines and never question the channel mix. Reply.io's per-vertical analytics expose the bigger lever: local-service owners (dentists, contractors, clinics) frequently never click an email link but pick up the phone — their sequence should reach the call task by step three. In-house marketing leads at B2B SaaS companies do the opposite — they book from the email link at odd hours and treat unsolicited calls as a strike, so their sequence should go email-heavy with LinkedIn as the trust layer and no dial at all. Same offer, same walkthrough, structurally different sequences — and the analytics, segmented by your contact tags, tell you which shape each vertical wants.
Typical SEO Agency Booking Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Walkthrough calls booked per 1,000 prospects sequenced | 12-25 | Audit-teaser opener with a calendar-only CTA; varies by vertical and list quality |
| Share of bookings from LinkedIn and call-task steps | 25-40% | Multichannel steps recover prospects the email link alone would have lost |
| Walkthrough show rate | 65-85% | Highest when the call is framed as the audit itself, not a sales conversation |
| 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 — so the cost-per-booked-walkthrough math has a stable infrastructure line in it.
Reply.io is billed separately on its own subscription, covering multichannel sequences, Jason AI, the unified inbox, contact management, and analytics — priced per its current plans, with seats and contact volume varying by tier.
Infrastructure cost scales with mailbox count; Reply.io's cost scales with seats and features. For a booking-first motion the useful number is blended cost per walkthrough on the calendar — both bills divide cleanly into it, and at typical booking rates the infrastructure side stays a small fraction of what one retainer client returns.
| 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 multichannel sequencing across email, LinkedIn, and call tasks, plus Jason AI, the unified inbox, and contact management. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Reply.io's email steps send from. You use them together: infrastructure below, sequencing software on top.
Should I run a warmup tool alongside ColdRelay mailboxes in Reply.io?
No. ColdRelay mailboxes warm continuously as part of their built-in budget — each mailbox sends 4 emails/day total, split 2 outbound + 2 warmup. There's no waiting period before sequences can start, and stacking another warmup layer on top spends sends without improving placement. Set Reply.io's per-mailbox sending limit to 2 outbound emails per day and let ColdRelay handle the rest.
Why gate the audit behind a live call instead of just sending it?
Because the attached audit converts the prospect into a reader, and the walkthrough converts them into a buyer. A PDF gets skimmed, forwarded, and shelved — and your best analysis just educated their current agency. On the live walkthrough, the prospect watches you find problems on their own site in real time, asks questions, and experiences what working with you feels like before any proposal exists. The teaser-finding email proves you actually looked; the call is where the trust that closes retainers gets built. Agencies that switch from audit-attached to walkthrough-gated outreach consistently trade a few easy replies for a much higher rate of real opportunities.
We're a small agency with no SDRs — are Reply.io's call tasks realistic for us?
Yes, because engagement-triggered call tasks are a fundamentally smaller job than cold calling. Reply.io only queues a dial when a prospect's behavior warrants it — repeat opens, a booking-link click without a booking — so a 50-70 mailbox motion typically surfaces a handful of call tasks a day, not a dial sheet. That's 10-15 founder-minutes daily, spent exclusively on the warmest prospects in the pipeline, with a one-line script: help them pick a slot. Many small agencies find these assisted bookings have the highest show and close rates of any channel in the sequence.