Call-First Outreach, Run Through Reply.io
Commercial real estate doesn't close over email. Every deal — a disposition mandate, a lease, an off-market acquisition — gets done in a conversation, usually on the phone, usually after months of staying in touch. The honest job description for cold email in CRE is narrower than most senders admit: deliver the property-specific hook that makes the phone call welcome instead of cold. Reply.io is built around exactly that handoff — multichannel sequences where email steps, call tasks, and LinkedIn touches live in one flow, so the email and the call are choreographed instead of run from two different tools. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs Reply.io's email steps actually send from.
This guide covers the call-first workflow specifically — provisioning sending infrastructure on ColdRelay, wiring it into Reply.io, writing email steps that set up the call task instead of replacing it, and using Reply.io's timezone-aware schedules to run a multi-market book without calling a Phoenix owner at 6am.
Why Run Reply.io on ColdRelay Infrastructure
Reply.io's strength for a brokerage team is orchestration: one sequence carries the email that plants the property hook, the call task that converts it into a conversation, and the LinkedIn step that keeps you visible through a long deal cycle. Jason AI sits on the reply side, helping categorize and draft responses, and the unified inbox collects every answer in one place. What Reply.io doesn't do is provision the email layer itself — the mailboxes you connect have to come from somewhere, and their deliverability is decided before Reply.io sends a single step.
That's the layer ColdRelay covers. Mailboxes run on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured, ready in about an hour. For a call-first motion this is more than hygiene: the entire sequence depends on the owner having seen the email before the phone rings. If step one lands in spam, the call task two days later is just another cold call — you've lost the warm-up effect that justified sequencing the channels together in the first place. 95%+ inbox placement is what keeps the choreography intact.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Reply.io is the sequencing and engagement layer on top. Reply.io decides when the email goes, when the call task fires, and what happens to the reply; ColdRelay makes sure the email half of that plan actually reaches the inbox.
Visit Reply.io →Connecting ColdRelay Mailboxes to Reply.io
Provision mailboxes on ColdRelay
Choose secondary domains that read like a brokerage team or named principal — owners take calls from people, and the email address should match the voice on the phone. ColdRelay supports 100-150 mailboxes per domain; because call capacity is the real constraint in a call-first motion, most CRE teams start with 20-60 mailboxes rather than a volume fleet. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Connect the mailboxes in Reply.io and set sending limits
In Reply.io, go to Settings → Email Accounts and connect each ColdRelay mailbox via SMTP/IMAP. Set each account's per-mailbox daily sending limit to 2 outbound emails per day — that mirrors ColdRelay's budget of 4 sends/day total per mailbox, 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 launches.
Create one schedule per market
In Reply.io's Schedules, build a sending schedule for each metro in your book, tied to that market's timezone — emails delivering mid-morning local time, call tasks queuing inside local business hours. A broker covering Dallas, Denver, and Charlotte runs three schedules and assigns each sequence to the right one, so the Phoenix owner never gets a 6am email and the call task list always matches who's actually at their desk.
Build the multichannel sequence around the call
Create a Reply.io sequence with the channels interleaved: an email step that names the property and the specific reason you're writing — and tells the owner you'll try their office later in the week — then a call task two days later, a LinkedIn connection request after the call attempt, and a short follow-up email referencing whichever touch connected. Assign your ColdRelay mailboxes to the sequence so email steps rotate across the pool while call and LinkedIn steps queue as tasks for the broker.
Turn on Jason AI and staff the unified inbox
Enable Jason AI to triage incoming replies — sorting interested owners from not-now responses and wrong contacts, and drafting first-pass answers for review. Every reply lands in Reply.io's unified inbox regardless of which mailbox sent the step, so the broker's morning routine is simple: clear the inbox, call every interested reply the same day, and let the sequence keep working everyone else.
The Call-First Reply.io Playbook
Write the email to set up the call, not replace it
The highest-leverage line in a CRE cold email is the one announcing the call: "I'll try your office Thursday morning — if another time is better, reply and tell me." It converts the call task from an interruption into an appointment the owner half-expects, and it gives reception a reason to put you through. Keep the email itself to three sentences: the property, the one number or observation that proves you've done the work, and the call notice. The email's job is done when the phone gets answered.
Run the call task queue as a daily block, market by market
Reply.io turns due call steps into a task queue — treat it like a broker's call block, not an all-day drip. Work one market's queue at a time inside that market's mid-morning window, with the property record open before you dial; because the schedule already filtered tasks to local business hours, the queue order is the dial order. Two focused hours clearing call tasks beats eight hours of scattered dials, and every outcome logged on the task keeps the sequence branching correctly.
Let Jason AI decide who gets phone time
In a call-first motion the scarce resource is broker hours, not sends. Use Jason AI's reply triage to protect them: interested owners and "what did you have in mind?" replies get a same-day call ahead of any scheduled task; not-now replies get a polite close and a future re-engagement date; wrong-contact replies get corrected in Reply.io's contact records so the next sequence starts with better data. The broker should never spend a call block discovering what an email reply already said.
Keep not-now owners in a slow lane — the relationship is the asset
Most owners who reply aren't sellers this quarter, and in CRE that's not a loss — it's a future deal with a timestamp. Move not-now replies into a separate low-frequency Reply.io sequence: a quarterly email with one genuinely useful market data point for their submarket, a LinkedIn touch when something changes, no call tasks until they re-engage. The same ColdRelay mailbox pool carries both lanes inside the 2 outbound/day budget, and eighteen months later the broker who kept showing up is the one who gets the listing call.
Typical Call-First Outreach Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — the call task only works warm if the email step landed first |
| Call connect rate after an email touch | 12-20% | Versus low single digits on pure cold dials; the announced-call line in the email is the biggest lever |
| Share of meetings booked on the phone | 60-75% | Email starts the thread, but most CRE meetings are agreed verbally on the call step |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup; call and LinkedIn steps don't draw on it |
| Time to first sequence | Same day | ~60 minutes to provision on ColdRelay, plus schedules and sequence setup 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 because a call-first motion is throttled by broker phone hours rather than send volume, most CRE teams run a leaner fleet than volume senders.
Reply.io is billed separately on its own per-user plans, which cover multichannel sequences with email, call, and LinkedIn steps, Jason AI, schedules, contact management, and the unified inbox.
The two costs scale on different axes: Reply.io with the brokers working sequences and call queues, ColdRelay with the mailboxes feeding the email steps. A three-broker team with 40 mailboxes covers 80 outbound emails/day — comfortably more than the call blocks downstream of those emails can absorb, which is the right way around for a relationship business.
| 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 compete with Reply.io?
No — they're complementary layers of the same stack. Reply.io is the sequencing and engagement layer: multichannel sequences, call tasks, LinkedIn steps, Jason AI, schedules, and the unified inbox. ColdRelay is the infrastructure layer underneath: the domains, mailboxes, and dedicated IPs that Reply.io's email steps send from. Reply.io choreographs the touches; ColdRelay makes sure the email touches land.
Why add call tasks at all — isn't email cheaper?
Cheaper per touch, but CRE deals don't close in an inbox. Owners and tenants commit in conversations, and a phone call after a property-specific email connects at several times the rate of a cold dial — the owner already knows who you are and which building you're calling about. Reply.io's value for real estate is precisely that the email and the call live in one sequence, timed off each other, instead of an email tool and a separate call sheet that never sync.
How do I run sequences across multiple markets and timezones?
Build one Reply.io schedule per market, tied to its timezone, and assign each market's sequence to its schedule — emails deliver mid-morning local time and call tasks queue inside local business hours. The ColdRelay mailbox pool is shared across all of them; mailboxes don't care which market a send belongs to, so capacity stays fungible while the timing stays local.
Do call tasks and LinkedIn steps count against the mailbox sending budget?
No. The ColdRelay budget governs email only: each mailbox sends 4 emails/day total — 2 outbound + 2 warmup. Call tasks and LinkedIn steps execute through Reply.io as broker tasks and don't touch the mailboxes, which is what makes multichannel attractive in a call-first motion: the sequence does two or three times the touches without needing a single additional mailbox.