Insurance Prospecting, Run Through Reply.io
Commercial insurance is a relationship sale on a calendar. Whether you broker P&C, group benefits, or liability lines, the prospect who ignores you in March takes your call in September — because their policy renews in December. The brokers who win are the ones in front of the business owner or HR lead 60-120 days before renewal, when there's still time to market the account.
Reply.io is where that motion runs: multichannel sequences that mix email, calls, and LinkedIn in one flow. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs that Reply.io actually sends from, so your agency's primary domain (the one carrying policy documents, certificates of insurance, and claims correspondence) never touches cold outreach. This guide covers how to wire the two together.
Why Run Reply.io on ColdRelay Infrastructure
Reply.io is an engagement platform — it sequences email, calls, and LinkedIn touches from whatever mailboxes you connect, and Jason AI can help draft and optimize the steps. What it doesn't do is provision domains or guarantee the deliverability of the mailboxes themselves. That's the infrastructure layer's job.
That's where ColdRelay fits. Instead of risking your agency domain or hand-configuring DNS on a pile of Google Workspace seats, you order dedicated mailboxes 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 you can send — warmup runs continuously as part of each mailbox's daily budget.
The stakes are higher for brokers than for most senders. Your primary domain carries binders, COIs, and claims email that absolutely must arrive. The pairing is additive, not competitive: ColdRelay is the infrastructure, Reply.io is the multichannel engagement layer on top — you keep its sequencing, dialer, and unified inbox, and just give it mailboxes built to land.
Visit Reply.io →Connecting ColdRelay Mailboxes to Reply.io
Provision mailboxes on ColdRelay
Pick secondary domains adjacent to your agency brand — never the domain your producers use for policy and claims email. ColdRelay supports 100-150 mailboxes per domain; most brokerages start with 20-100 mailboxes across 1-2 domains. 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
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 sends across the pool.
Set per-mailbox sending limits to match
In each email account's sending settings, cap daily volume at 2 outbound emails per day to mirror ColdRelay's per-mailbox budget — 4 sends/day total per mailbox, split 2 outbound + 2 warmup. Leave warmup to ColdRelay rather than enabling a second warmup layer inside Reply.io.
Build a multichannel sequence timed to renewal
Create a Reply.io sequence that opens with 2-3 emails, then adds a call task for the producer and a LinkedIn connection or message step. Use Jason AI to draft conservative, compliance-safe variants, and trigger the sequence 90-120 days before the prospect's known or estimated renewal date — by day 60 you're already late to market the account.
Route replies and launch
Work responses from Reply.io's unified inbox so email replies, call outcomes, and LinkedIn responses sit in one queue. Assign each interested reply to the producer who owns the call — in insurance, the email opens the door, the phone call books the meeting.
The Insurance Broker Reply.io Playbook
Build the list around renewal dates, not titles alone
X-date is the most valuable field in your CRM. Segment Reply.io sequences by renewal month and enroll prospects 90-120 days out, so your first email lands while the account can still be marketed. A generic always-on blast wastes sends on businesses locked in for another ten months.
Keep the copy conservative and compliance-aware
Never imply specific coverage, savings percentages, or premium quotes in cold email — a broker can't quote what they haven't underwritten. Lead with a market check or benchmarking angle ('most firms your size haven't re-marketed their liability program in 3+ renewals') and let the licensed conversation happen on the call.
Use every channel, in order
Insurance buyers rarely move on email alone. Structure Reply.io sequences so email creates familiarity, the LinkedIn touch adds a face and a license number, and the call task — surfaced to the producer at the right step — closes the meeting. Multichannel in one flow is exactly what Reply.io is built for.
Protect the agency domain absolutely
Certificates of insurance, binders, and claims correspondence cannot afford a spam folder. Run every cold sequence from ColdRelay secondary domains on isolated Azure tenants with dedicated IPs, and keep your primary agency domain out of Reply.io entirely.
Typical Insurance Outbound Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate | 2-5% | Renewal-window timing is the biggest lever; in-window sends sit at the top of the range |
| Email-to-meeting conversion | Higher with a call step | Sequences pairing email with a Reply.io call task convert meaningfully better than email-only — insurance closes on the phone |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first campaign | Same day | ~60 minutes to provision on ColdRelay, plus 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.
Reply.io is billed separately on its own subscription for multichannel sequencing, the dialer, Jason AI, and the unified inbox — priced per its current plans.
Infrastructure cost scales with mailbox count; Reply.io's cost scales with users and features. For a brokerage, that's one predictable bill for sending capacity and one for the engagement software your producers work in.
| 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
Is ColdRelay a replacement for Reply.io?
No — they're complementary layers, not competitors. Reply.io handles the engagement side: multichannel sequences, call tasks, LinkedIn steps, and the unified inbox. ColdRelay provides the layer underneath — the secondary domains, mailboxes, and dedicated IPs that Reply.io sends from. Brokerages use both together.
Will cold outreach put our agency's claims and policy email at risk?
Not when the mailboxes come from ColdRelay. Outbound runs on separate secondary domains, dedicated IPs, and isolated Azure tenants — completely walled off from the primary domain carrying certificates, binders, and claims correspondence. Your operational email reputation is untouched by prospecting volume.
When should we start emailing a prospect relative to their renewal date?
Aim for 90-120 days before the X-date, and no later than 60. That window gives the prospect time to grant a broker of record letter or let you market the account before the incumbent locks in the renewal. Segment your Reply.io sequences by renewal month so enrollment happens automatically as accounts enter the window.
Do ColdRelay mailboxes need a warmup period before our producers can start sending?
No waiting period. Each mailbox sends 4 emails/day total — 2 outbound + 2 warmup — with warmup running continuously rather than as an upfront phase. Mailboxes provision in about an hour with SPF, DKIM, and DMARC pre-configured, so a sequence can go live in Reply.io the same day. Don't stack Reply.io's own warmup on top.