Multi-Territory Solar Outbound, Run Through Smartlead
A commercial solar developer active in several states isn't running one outbound motion — it's running five or six of them at once. A facility in ERCOT territory, one under a Northeast investor-owned utility, and one served by a Midwest co-op face different commercial rates, different incentive stacks, and different payback math. An email that quotes the wrong utility's economics doesn't just underperform; it tells the CFO you've never looked at their bill. The operational problem isn't writing one great sequence — it's running many region-correct ones in parallel without the whole thing collapsing into chaos.
Smartlead is built for exactly that kind of parallel structure: one campaign per utility territory, campaign-level mailbox rotation, a Master Inbox that lets each regional sales lead work their own replies, and an API for rolling it all up into one report. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs every one of those territory campaigns sends from. This guide covers how multi-state solar teams wire the two together into a territory operating system, not just a campaign.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead's architecture maps cleanly onto a territory-based org: campaigns are the unit of work, each campaign rotates across its own assigned mailboxes, spintax varies copy within a sequence, and webhooks push campaign events into whatever reporting stack you run. What Smartlead doesn't do is mint the mailboxes — it sends from whatever accounts you connect, and the reputation of those accounts is the infrastructure layer's job.
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, with no warmup waiting period before sending. Warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), so a pool stood up for a new territory is sending real outreach the same day.
The two layers are complementary, not competing: ColdRelay is the infrastructure, Smartlead is the sending and sequencing engine on top. For a multi-territory developer, the payoff of the pairing is isolation in both directions — each territory campaign rotates through its own mailbox slice, and at 95%+ inbox placement, the regional savings math you worked hard to get right actually reaches the facility owner it was computed for.
Visit Smartlead →Building the Territory Architecture in Smartlead
Provision a territory-mapped pool on ColdRelay
Map domains to regions before you buy: with 100-150 mailboxes supported per domain, one secondary domain comfortably covers two or three utility territories' worth of sending capacity. A developer active across five territories might run two domains and 60-100 mailboxes, pre-assigned on a spreadsheet to territory slices. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Bulk-import the pool under Email Accounts
Export 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 upload. Tag accounts by territory as you import — those tags are what make assigning each campaign its own rotation slice painless later.
Set per-mailbox limits and skip double-warming
Set each account's daily campaign limit in Smartlead to 2 outbound emails per day, matching ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. ColdRelay runs warmup continuously on its side as part of that budget, so leave Smartlead's warmup off for these accounts rather than burning the budget twice.
Create one campaign per utility territory
Build a separate Smartlead campaign for each territory — its own list, its own sequence quoting that utility's commercial rates and that state's incentive stack, its own payback range. Attach only that territory's mailbox slice and let Smartlead's campaign-level rotation spread sends across it. A territory campaign with 15 mailboxes runs 30 outbound sends/day, every one of them quoting the right utility's numbers.
Wire up the Master Inbox and webhooks
Route replies through Smartlead's Master Inbox, filtered by campaign so each regional sales lead works only their territories' responses. Then point Smartlead's webhooks at your reporting stack — replies, opens, and bounces per campaign roll up into a per-territory dashboard, which is how leadership compares regions instead of squinting at five separate campaign screens.
The Multi-Territory Solar Playbook for Smartlead
Make the campaign the territory's P&L, not a mailing list
Treat each Smartlead campaign as the standing operational unit for its territory — owned by a regional sales lead, carrying that region's savings framing, running continuously rather than as a one-off blast. When a campaign owns its mailbox slice, its copy, and its reply queue, you can answer questions a single blended campaign never can: which territory's economics are converting, which regional lead is keeping up with replies, and where the next mailbox order should go.
Spin rate-class variations inside each territory with spintax
Even within one utility, a warehouse on a demand-charge rate schedule and a retail strip on a flat commercial tariff hear different value stories. Use Smartlead's spintax support to rotate rate-class-specific framings within a territory's sequence — demand-charge reduction language in one variant, straight kWh-offset savings in another — so the sequence stays one campaign operationally while reading differently to different load profiles.
Give each regional lead a Master Inbox lane, not a shared pile
Reply handling is where multi-territory outbound usually breaks: a facility owner in one state gets answered by a rep who knows another state's net-metering rules. Filter Smartlead's Master Inbox by campaign so each regional sales lead triages only their territories, with their utility's rate sheet and incentive checklist at hand. The reply quality difference is audible — and it's why the campaign-per-territory structure matters beyond reporting.
Let webhook data pick your next territory
Expansion is the standing question for a multi-state developer, and your Smartlead webhook feed answers it with evidence. Pipe per-campaign replies and positive-sentiment counts into a simple cost-per-assessment view by territory. When an existing region's numbers say the economics resonate, adjacent territories under similar rate structures are your best expansion bets — and because a new ColdRelay pool provisions in about an hour, testing one is a same-day decision, not a quarter-long project.
Typical Multi-Territory Solar Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate spread across territories | 2-6% | High-rate utility territories with strong incentives sit at the top; cheap-power regions at the bottom — the spread is the signal |
| Territory campaigns run in parallel | 4-8 | Per BD team, each with its own mailbox slice, sequence, and regional reply owner |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| New territory live from decision to first send | Same day | ~60 minutes to provision the mailbox slice on ColdRelay, clone a territory campaign in Smartlead, swap in regional numbers |
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 since a multi-territory pool is naturally larger than a single-market one, territory operators tend to land in the better tiers.
Smartlead is billed separately on its own subscription for campaigns, mailbox rotation, the Master Inbox, and API access — priced per its current plans.
Infrastructure cost scales with total mailbox count across all territories; Smartlead's cost scales with plan tier, not with how many campaigns you run. Adding a sixth territory is mostly an infrastructure decision — a new mailbox slice on ColdRelay and a cloned campaign in Smartlead, not a new software contract.
| 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
Does ColdRelay replace Smartlead?
No — they're complementary layers. Smartlead handles campaigns, campaign-level mailbox rotation, spintax, the Master Inbox, and webhooks. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Smartlead sends from. You bulk-import ColdRelay mailboxes under Email Accounts in Smartlead and run both together.
Should each utility territory get its own domain, or just its own mailboxes?
Its own mailbox slice at minimum; its own domain when volume justifies it. ColdRelay supports 100-150 mailboxes per domain, so smaller territories can share a domain while each Smartlead campaign still rotates through a dedicated slice. Once a territory grows past roughly 40-50 mailboxes, giving it a dedicated domain keeps its reputation fully independent of its neighbors.
How do regional sales leads avoid stepping on each other's replies?
Filter Smartlead's Master Inbox by campaign. Because each utility territory is its own campaign, each regional lead gets a clean lane containing only their territories' replies — and answers facility owners with the correct utility's rates, net-metering rules, and incentive details instead of a generic script. Reply ownership falls out of the campaign structure automatically.
How fast can we open outbound in a new state or utility territory?
Same day. A new mailbox slice provisions on ColdRelay in about an hour — isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured — and there's no warmup waiting period, since warmup runs continuously as part of each mailbox's 4/day budget (2 outbound + 2 warmup). Clone an existing territory campaign in Smartlead, swap in the new region's rates and incentive math, attach the new slice, and launch.