Insurance Prospecting at Volume, Run Through Instantly
Most brokerages treat outbound as a producer-by-producer activity: a list gets pulled, a batch of emails goes out, and the effort dies when renewals season gets busy. The brokers who compound pipeline run it differently — as an always-on machine. Every business in their territory has an X-date, which means every month a fresh cohort of group benefits, general liability, and workers comp accounts enters its shopping window. The machine's job is to make sure a campaign is already waiting for them.
Instantly is built for exactly this kind of email-first volume play: a simple campaign builder, unlimited connected email accounts on paid plans, and analytics that make month-over-month comparison easy. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs that Instantly actually sends from, so the agency domain carrying binders and claims email never appears in a cold campaign. This guide covers how to wire the two into a renewal-calendar machine.
Why Run Instantly on ColdRelay Infrastructure
Instantly's biggest structural advantage is that paid plans don't meter your connected email accounts — you can attach as many sending mailboxes as your campaigns need. But Instantly doesn't create those mailboxes; it sends from whatever you plug into it, and the deliverability of the mailboxes themselves is the infrastructure layer's problem.
That's the gap ColdRelay fills. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured, ready in about an hour — then bulk-import the whole pool into Instantly via CSV. There's no upfront warmup period before sending; warmup runs continuously as part of each mailbox's daily budget.
For a brokerage running twelve renewal-month segments across three policy lines, that combination matters: Instantly gives you unmetered account connections and a builder fast enough to maintain dozens of parallel campaigns, while ColdRelay gives you a mailbox pool that's actually built to land — at 95%+ inbox placement. The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Instantly is the sending and sequencing layer on top.
Visit Instantly →Connecting ColdRelay Mailboxes to Instantly
Provision the mailbox pool on ColdRelay
Volume campaigns need a real pool, not a handful of seats. ColdRelay supports 100-150 mailboxes per domain on isolated Azure tenants with dedicated IPs — a brokerage running always-on campaigns across group benefits, GL, and workers comp typically starts with 50-150 mailboxes across 1-2 secondary domains. Everything provisions in about an hour with SPF, DKIM, and DMARC already configured.
Bulk-import the pool into Instantly via CSV
Export your mailbox credentials from the ColdRelay dashboard, then in Instantly go to Email Accounts → Add New → Bulk Import (SMTP/IMAP) and upload the CSV. The entire pool connects in one pass — no per-account OAuth dance — which is the point of pairing an unmetered platform with infrastructure that exports cleanly.
Cap each account at 2 outbound sends per day
In each Instantly account's settings, set the daily campaign limit to 2 emails. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay handles the warmup half continuously, so skip layering Instantly's warmup on top of it.
Build one campaign per policy line per renewal month
In Instantly's campaign builder, create a campaign matrix instead of one big blast: 'GL — September renewals', 'Group Benefits — October renewals', and so on. Upload each month's lead segment as its own CSV with policy-line and renewal-month fields, attach the shared mailbox pool to every campaign, and let Instantly rotate sends across it. New month, new segment, same machinery.
Launch A/Z tests on the offer and staff Unibox
Use Instantly's A/Z testing to run multiple subject and body variants of the cost-review offer inside each campaign — Instantly will spread sends across all variants so you can compare them in campaign analytics. Replies from every campaign land in Unibox, one unified queue; route interested replies to the producer who owns that policy line the same day.
The Insurance Broker Instantly Playbook
Run a campaign matrix, not a campaign
The unit of work is policy line × renewal month. A 'GL — September' campaign and a 'Workers comp — September' campaign get different pain language, different proof points, and separately readable analytics. Instantly's builder is light enough that maintaining 12-36 small campaigns is realistic — and each one stays evergreen, refilled with next year's cohort when the month rolls around again.
Make enrollment automatic, not heroic
The failure mode of broker outbound is the list pull that only happens when a producer has a slow week. Put the segmentation upstream instead: maintain a master list keyed on estimated X-date, and on the first of each month export the cohort entering its 90-120-day window and upload it into the matching Instantly campaigns. The machine runs whether or not anyone had a slow week.
A/Z-test the cost-review offer, not just subject lines
Insurance cold email converts on the offer framing, and Instantly's A/Z testing lets you race genuinely different versions — a premium benchmarking angle ('how your workers comp mod compares to firms your size'), a market-conditions angle ('GL rates moved this year; most renewals haven't caught up'), a second-opinion angle ('a 20-minute review before you sign the renewal'). Kill losers monthly and let winning variants carry the next cohort. Never promise specific savings or quote premiums in cold copy — the licensed conversation happens after the reply.
Read analytics by segment, by month
Because every campaign is one policy line and one renewal month, Instantly's campaign analytics become a diagnostic grid: if workers comp segments out-reply benefits segments three months running, that's where the next batch of mailbox capacity goes. Volume without segment-level readouts is just spend; the matrix is what turns send data into an allocation decision.
Typical Insurance Outbound Benchmarks (Instantly + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate by segment | 1.5-4% | Policy-line-specific copy in the renewal window sits at the top; generic always-on blasts at the bottom |
| A/Z variant lift after 3 monthly cycles | 20-40% | Compounding effect of killing losing offer variants each month and re-racing winners |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Daily send capacity at 100 mailboxes | 200 outbound/day | Enough to keep 12+ renewal-month segments in continuous sequence; scale the ColdRelay pool as the matrix grows |
What It Costs: Instantly + 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 since ColdRelay supports 100-150 mailboxes per domain, a volume pool doesn't mean a sprawl of domains.
Instantly is billed separately on its own subscription for the campaign builder, A/Z testing, Unibox, and analytics — and because paid plans don't charge per connected email account, your Instantly bill stays flat as the mailbox pool grows.
That's the economics of the volume play: the only cost that scales with sending capacity is the per-mailbox infrastructure, and that rate drops at higher tiers. One bill for the mailbox pool, one flat bill for the software running the campaign matrix.
| 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; Instantly handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Is ColdRelay an alternative to Instantly?
No — they're complementary layers, not competitors. Instantly is the sending and sequencing layer: campaigns, A/Z testing, Unibox, analytics. ColdRelay is the infrastructure layer underneath — the secondary domains, mailboxes, and dedicated IPs that Instantly sends from. Brokerages running the volume play use both together.
Instantly allows unlimited email accounts — why does the mailbox source matter?
Unmetered connections solve the software cost of scale, not the deliverability of scale. A hundred poorly configured mailboxes land in spam a hundred times over. ColdRelay mailboxes come on isolated Azure tenants with dedicated IPs and SPF, DKIM, and DMARC pre-configured, which is what holds 95%+ inbox placement as the pool grows — Instantly's unlimited connections are only useful when the accounts you connect are built to land.
How many mailboxes does an always-on renewal-month operation need?
Work backward from the matrix. Each mailbox contributes 2 outbound sends/day (of its 4/day total — the other 2 are warmup), so 100 mailboxes is 200 sends/day, roughly 4,000 sends a month across your active segments. A brokerage running three policy lines with a few hundred prospects entering the renewal window each month typically lands between 50 and 150 mailboxes, then scales the pool when a policy line proves out in Instantly's analytics.
Do we have to pause campaigns while new ColdRelay mailboxes warm up?
No. There's no upfront warmup phase — warmup runs continuously as part of each mailbox's 4/day budget (2 outbound + 2 warmup), and mailboxes provision in about an hour with DNS pre-configured. New capacity can be bulk-imported into Instantly via CSV and attached to live campaigns the same day; just don't enable Instantly's own warmup on top of ColdRelay's.