Sequencing Toward the Call, Run Through Reply.io
Agency retainers don't close in an email thread. A prospect can like your case studies and still not sign — because what they're actually buying is the working relationship, and the only place they can evaluate that is a live conversation. The real conversion event in agency outreach isn't the reply; it's the booked call. That changes what a sequence is for: every step exists to make picking up the phone feel natural rather than cold.
Reply.io is unusually well built for that job, because it treats email, LinkedIn, and calls as steps in one sequence instead of three separate tools. The stack splits into two layers: Reply.io is where the multichannel sequences, the unified inbox, and Jason AI's reply handling live. ColdRelay is the layer underneath — the secondary domains, mailboxes, and dedicated IPs the email steps actually send from. This guide covers how an agency wires the two together to run a call-first motion: email opens the door, a LinkedIn touch puts a face on the name, and a call task fires the moment a prospect shows real engagement.
Why a Call-First Motion Needs Its Own Infrastructure Layer
A multichannel sequence is a relay race, and email runs the first leg. If the opening email never reaches the inbox, the LinkedIn connect that follows arrives from a stranger and the call task dials a prospect who has never heard of you — the whole choreography collapses back into a pure cold call. Reply.io orchestrates the steps and enforces per-mailbox sending limits, but it sends from whatever mailboxes you connect; domains, DNS, and IP reputation are the infrastructure layer's job.
That's where ColdRelay fits. You provision secondary domains and mailboxes on isolated Azure tenants with dedicated IPs — SPF, DKIM, and DMARC pre-configured, ready in about an hour, sustaining 95%+ inbox placement. There's no warmup waiting period before the first sequence: warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), so the email leg of the relay is reliable from day one. And because the sequence is deliberately steering prospects toward a conversation with your founder or principal, the agency's own domain — the one carrying proposals and client threads — never touches the cold traffic.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Reply.io is the sequencing and engagement layer on top. Reply.io choreographs the path to the call; ColdRelay makes sure the first step of that path actually lands.
Visit Reply.io →Wiring ColdRelay Mailboxes Into Reply.io's Multichannel Sequences
Provision the sending pool on ColdRelay
Order secondary domains adjacent to your agency's name — never the primary domain your clients and proposals live on. ColdRelay supports 100-150 mailboxes per domain, so a call-first pool of 20-50 mailboxes fits comfortably on one domain. 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's Email Accounts settings
Export the SMTP/IMAP credentials from the ColdRelay dashboard and add each mailbox in Reply.io under Email Accounts. Once connected, Reply.io rotates sequence sends across the pool, and every reply flows into the unified inbox regardless of which mailbox the thread started from.
Set Reply.io's per-mailbox sending limits to 2 outbound/day
Use Reply.io's per-mailbox sending limits to cap each account at 2 outbound emails per day. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup, with warmup running continuously on ColdRelay's side. The email steps are the trust-building leg of a multichannel sequence; keep them on budget and let LinkedIn and call steps carry the extra touches instead of extra volume.
Build the multichannel sequence: email, LinkedIn touch, call task
In Reply.io's sequence builder, structure the steps around the call rather than the reply: step one is a short email that earns recognition, step two is a LinkedIn profile visit and connection request a day later so your face attaches to the name, step three is a follow-up email referencing the connect, and a call task triggers for prospects who have engaged — opened twice, clicked, accepted the connect, or replied. By the time the phone rings, you're a name they've seen three times in a week, not a cold caller. Keep prospect engagement history in Reply.io's contact management so whoever makes the call sees the full touch trail.
Turn on Jason AI to triage the unified inbox
Configure Jason AI to handle first-pass replies in the unified inbox: it categorizes responses, answers routine questions, handles objections and out-of-office noise, and pushes prospects toward the calendar. Set the handoff rule explicitly — anything showing genuine interest routes straight to the founder or principal who'll actually run the discovery call, same day. Jason AI clears the noise; the human takes the chemistry.
The Call-First Agency Playbook on Reply.io
Write every step as a reason to talk, not a pitch to read
If the conversion event is the call, the email's job is to make a conversation feel low-stakes and obviously useful — not to pre-sell the retainer in writing. Lead with a specific observation about their business and a question only a call can resolve: 'we noticed X about your funnel — fifteen minutes would tell you whether it's costing you pipeline.' A sequence that tries to close in text attracts prospects who want a quote by email; a sequence built around a conversation attracts prospects who want a partner. The second kind signs retainers.
Use the LinkedIn step to turn a cold call into a warm one
The difference between a cold call and a warm call is whether the prospect recognizes the name on the screen — and Reply.io's LinkedIn steps manufacture that recognition deliberately. Sequence a profile visit before the connection request: many prospects check who viewed them, so your face appears before the ask does. By the time the call task fires, the prospect has seen your email, your profile visit, and your connect note. Pickup rates and call quality both move when the first ring isn't the first touch.
Gate the call task on engagement, not on schedule
Calling everyone on day five treats your principal's hours like sequence volume — and burns them on prospects who never opened an email. Instead, let Reply.io's engagement data decide who earns a dial: trigger the call task on real signals like repeat opens, a link click, an accepted LinkedIn connect, or a reply. The math compounds with the infrastructure budget: at 2 outbound emails/day per mailbox (of the 4/day total, the other 2 being warmup), a 30-mailbox pool puts 60 emails out daily, and engagement gating distills that into a short, high-probability daily call list a founder can actually clear before lunch.
Let Jason AI hold the line so the founder only sees real interest
In most agencies the person who can actually close a retainer is also the busiest — and one week of triaging 'send me your pricing' and out-of-office replies is how founders quietly abandon outbound. Jason AI is the staffing fix: it answers routine questions, defuses soft objections, and nudges lukewarm replies toward the calendar, while your handoff rule routes genuine interest to the principal within hours. The founder's outbound job shrinks to the two things only they can do — the discovery call and the close — which is exactly why the motion survives past month one.
Typical Call-First Agency Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate on multichannel sequences | 4-8% | Email + LinkedIn + call steps compound; email-only versions of the same sequence typically run 2-4% |
| Engaged-prospect call connect rate | 20-35% | Calls gated on opens, clicks, or an accepted LinkedIn connect; un-gated cold dials run well under 10% |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, warmup running continuously |
| Time from signup to first sequence live | Same day | ~60 minutes to provision on ColdRelay; sequence design and call-task rules are the real setup work in Reply.io |
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 a call-first motion sizes its pool to the principal's calendar rather than to raw volume, so agencies typically start small and add mailboxes only when the daily call list runs thin.
Reply.io is billed separately on its own subscription, covering multichannel sequences, the unified inbox, Jason AI, per-mailbox sending limits, and contact management — priced per its current plans.
The combined cost maps to the motion cleanly: Reply.io's subscription buys the choreography and the reply triage, ColdRelay's per-mailbox pricing buys the deliverability the first touch depends on. When the output is booked discovery calls with prospects who already recognize your name, a single signed retainer typically covers both line items 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 is the sequencing and engagement layer: multichannel sequences combining email, LinkedIn, and call steps, the unified inbox, Jason AI's reply handling, and contact management. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs the email steps send from. An agency running a call-first motion uses both — Reply.io to choreograph the path to the conversation, ColdRelay to make sure the first email on that path lands.
If the goal is a phone call, why does email deliverability matter so much?
Because email is the step that makes every later step warm. The LinkedIn connect works because the prospect saw your email yesterday; the call connects because they have seen your name three times this week. If the email lands in spam, the relay breaks and the call task becomes a pure cold dial. ColdRelay's infrastructure — dedicated IPs on isolated Azure tenants, SPF, DKIM, and DMARC pre-configured — sustains 95%+ inbox placement, which is what keeps the multichannel choreography intact end to end.
Won't Jason AI handling replies undermine the personal-chemistry angle?
It protects it. Chemistry happens on the call, not in inbox triage — and the triage is precisely what stops founders from showing up to outbound at all. Jason AI handles the layer where no relationship is being built: routine questions, scheduling friction, soft objections, out-of-office noise. Your handoff rule ensures any reply showing real interest reaches the principal the same day, so the human enters the conversation exactly where the human matters. The prospect's first live interaction with your agency is a prepared founder on a discovery call, not a templated reply three days late.
How many mailboxes does a call-first agency motion need?
Size the pool to the calendar, not to a volume target. Each ColdRelay mailbox contributes 2 outbound sends/day of its 4/day total (the other 2 are warmup), so a 30-mailbox pool puts about 60 emails out daily — which, after engagement gating, typically distills into a handful of genuinely warm call tasks and replies a day. That's roughly what one principal can work properly while still running the agency. Set Reply.io's per-mailbox sending limits to the 2 outbound sends, and add mailboxes when the daily call list runs thin rather than ahead of demand — a fresh batch provisions in about an hour, so capacity is never the bottleneck.