The Renewal Calendar, Run as an Operating System
Every commercial account in your territory renews in exactly one month of the year. That single fact is the entire architecture of broker outbound — and most brokerages never build for it. They run outreach as a series of one-off pushes, when what the renewal cycle actually calls for is twelve always-on campaigns, one per renewal month, that prospects flow into automatically as their X-date approaches and flow back into a year later if they didn't move.
Smartlead is unusually well suited to running that system: campaign-level mailbox rotation lets each month's campaign draw on a shared sending pool, spintax keeps copy varied across thousands of sends, and the master inbox puts every reply — from any of the twelve campaigns — into one queue your producers can actually work. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs on isolated Azure tenants that Smartlead sends from, so the agency domain carrying binders and claims correspondence never appears in a cold campaign. This guide covers how to build the operating system.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead is a sending and sequencing platform — it rotates sends across whatever mailboxes you connect, and its job ends at the mailbox boundary. It doesn't provision domains, configure DNS, or guarantee that the accounts you plug in are built to land. That's the infrastructure layer's job, and for a twelve-campaign system that runs 365 days a year, the infrastructure layer is load-bearing: a renewal calendar only works if January's campaign is still inboxing in November.
That's where ColdRelay fits. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured, ready in about an hour — and ColdRelay supports 100-150 mailboxes per domain, so a pool big enough to feed twelve concurrent campaigns doesn't require a sprawl of domains. There's no upfront warmup phase before sending; warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), which is what keeps placement steady at 95%+ across a system that never turns off.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Smartlead is the sending and sequencing layer on top. You keep Smartlead's rotation, spintax engine, and master inbox — you just point them at mailboxes built for permanence.
Visit Smartlead →Building the Twelve-Campaign System in Smartlead
Provision the mailbox pool on ColdRelay
A twelve-campaign calendar needs a pool that can feed every active month at once. ColdRelay supports 100-150 mailboxes per domain on isolated Azure tenants with dedicated IPs — brokerages running the full calendar typically start with 60-120 mailboxes across 1-2 secondary domains, never the agency domain. Everything provisions in about an hour with SPF, DKIM, and DMARC already configured.
Bulk-import the pool into Smartlead
Export mailbox credentials from the ColdRelay dashboard, then in Smartlead go to Email Accounts and use the bulk CSV import to connect the entire pool via SMTP/IMAP in one pass. Tag accounts as you import them — you'll be assigning subsets to campaigns in the next steps, and clean tags make rotation assignments painless.
Set each account to 2 outbound sends per day
In each account's sending settings, cap daily campaign volume at 2 emails to mirror ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay runs the warmup half continuously, so leave Smartlead's own warmup off rather than double-warming the same accounts.
Create the twelve campaigns and assign rotation
Build one Smartlead campaign per renewal month — 'Renewals: January' through 'Renewals: December' — and use campaign-level mailbox rotation to attach a slice of the pool to each. At any given time roughly 2-3 campaigns are in their hot 90-120-day window, so weight rotation toward those months and let the off-peak campaigns idle on a smaller allocation. Prospects enter the campaign matching their X-date month; the campaign itself never gets rebuilt.
Wire the master inbox and webhooks
All twelve campaigns drain into Smartlead's master inbox. Set up reply categorization and assignment so each interested reply routes to the producer who owns that line of business, and use Smartlead's API and webhooks to push reply events into the agency management system — so the renewal calendar's output shows up where producers already live, not in a thirteenth browser tab.
The Insurance Broker Smartlead Playbook
Twelve campaigns, never thirteen
The discipline of the system is that the campaign count never grows. A new policy line, a new territory, a new producer — none of those create new campaigns. They become custom fields and spintax branches inside the existing twelve. Campaigns keyed to anything other than renewal month eventually drift, duplicate, and die; campaigns keyed to the calendar are evergreen, because December comes back every year with a fresh cohort attached.
Let spintax carry the policy-line variation
Instead of forking campaigns per line of business, write one sequence per month and use Smartlead's spintax to branch the pain language on a policy-line custom field — the GL prospect reads about liability rate movement, the benefits prospect reads about plan renewals and employee retention, the workers comp prospect reads about their mod. One campaign, three conversations. As a side effect, spintax also keeps copy non-identical across thousands of rotated sends, which is exactly what a year-round sender wants.
Route replies by line of business, not by campaign
The master inbox is where the calendar pays off, and the routing key is the line, not the month. A benefits reply from the March campaign and a benefits reply from the August campaign belong to the same producer. Build assignment rules on the policy-line field, hold producers to a same-day response standard, and push reply events through Smartlead's webhooks into the AMS so the producer's follow-up task exists before they've finished reading the email.
Use sub-accounts to scale the system across offices
A multi-office brokerage shouldn't run one office's renewal calendar inside another's workspace. Smartlead's client sub-accounts give each office or producer team its own twelve-campaign instance with its own analytics, while the ColdRelay mailbox pool stays centrally provisioned and allocated. Agency principals get white-label-style rollup reporting via the API; each office gets a calendar it owns.
Typical Insurance Outbound Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate, in-window campaigns | 2-5% | Campaigns in their 90-120-day renewal window; spintax-matched policy-line copy sits at the top of the range |
| Always-on campaigns maintained | 12 | One per renewal month, evergreen — prospects rotate through; the campaigns never get rebuilt |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Reply-to-producer handoff | Same day | Master inbox assignment rules plus webhook push into the AMS; insurance replies go cold in 48 hours |
What It Costs: Smartlead + 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 at 100-150 mailboxes per domain, a pool sized for twelve concurrent campaigns fits on one or two secondary domains.
Smartlead is billed separately on its own subscription for campaigns, mailbox rotation, spintax, the master inbox, sub-accounts, and API access — priced per its current plans.
The calendar's cost structure is pleasantly boring: the infrastructure bill scales with the mailbox pool at rates that drop in higher tiers, and the Smartlead bill covers the software the whole system runs in. Because the twelve campaigns are evergreen, you build once and the marginal cost of next year's cohort is the list, not the machinery.
| 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; Smartlead handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Is ColdRelay an alternative to Smartlead?
No — they're complementary layers, not competitors. Smartlead is the sending and sequencing layer: campaigns, mailbox rotation, spintax, the master inbox, sub-accounts. ColdRelay is the infrastructure layer underneath — the secondary domains, mailboxes, and dedicated IPs on isolated Azure tenants that Smartlead sends from. The renewal-calendar system uses both together.
Why one campaign per renewal month instead of one per policy line?
Because the renewal month determines when a prospect should hear from you, and the policy line only determines what they should read. Timing belongs in the campaign structure; messaging belongs in spintax and custom fields. Splitting campaigns by line multiplies twelve campaigns into thirty-six, triples the maintenance surface, and fragments your rotation — while a spintax branch on a policy-line field achieves the same message fit inside the calendar you already run.
How do replies from twelve campaigns reach the right producer?
Through Smartlead's master inbox, which pools replies from every campaign into one queue. Assignment rules keyed on the policy-line field route GL replies to the commercial lines producer and benefits replies to the benefits producer regardless of which month's campaign generated them, and Smartlead's webhooks can push each reply event into your agency management system so the follow-up task is waiting before the producer opens their inbox.
Can an always-on system really run year-round without burning the mailboxes?
That's exactly what the send budget is for. Each ColdRelay mailbox sends 4 emails/day total — 2 outbound + 2 warmup — with warmup running continuously rather than as a one-time upfront phase, which keeps reputation steady through all twelve months. Mailboxes provision in about an hour with SPF, DKIM, and DMARC pre-configured, and because the pool lives on secondary domains, the agency domain carrying binders and claims email is never exposed to outbound volume at all.