Multi-Location MSP Outbound, Run Through Smartlead
An MSP with offices in three metros isn't running one outbound motion — it's running three, and they only look alike from a distance. The Dallas campaign should name Dallas clients, reply from a Dallas-flavored identity, and land in the Dallas account manager's queue; the Denver campaign should do none of those things. The mistake multi-location firms make is flattening all of it into a single national blast, which reads local to nobody.
Smartlead is built for running parallel motions like this from one pane of glass: sub-accounts or campaigns per market, campaign-level mailbox rotation, and a master inbox that collects every reply regardless of which metro it came from. ColdRelay is the layer underneath — the secondary domains, dedicated mailboxes, and dedicated IPs that all of those metro campaigns actually send from. This guide covers wiring the two together so one shared infrastructure pool powers a genuinely local campaign in every city you operate in.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead gives a multi-location firm the org chart for its outbound: client sub-accounts that can mirror your offices, campaign-level mailbox rotation so each metro's sends spread across its assigned senders, and a master inbox that keeps every reply visible to whoever runs growth centrally. What it doesn't do is provision the domains and mailboxes those campaigns send from — that's the infrastructure layer's job.
That's where ColdRelay fits. Instead of each office buying its own workspace seats and fighting its own DNS, you provision one pool of dedicated mailboxes on isolated Azure tenants with dedicated IPs — fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour — and divide it across metros inside Smartlead. ColdRelay supports 100-150 mailboxes per domain, so a single order covers several markets, and reallocating capacity between cities is a Smartlead assignment change, not a procurement cycle.
The shared pool is the operational unlock: deliverability is managed once, centrally, at 95%+ inbox placement, while each metro campaign stays free to be aggressively local in its copy and identity. ColdRelay is the infrastructure, Smartlead is the sending and segmentation layer on top — additive, not competitive.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead
Provision one shared pool on ColdRelay, sized across your metros
Add up the markets first: a three-office MSP might weight 30 mailboxes to its largest metro and 15 each to the other two — 60 total, on one or two secondary domains kept separate from the primary domain your clients open tickets on. ColdRelay supports 100-150 mailboxes per domain, so the whole multi-market pool fits a single order. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Export the credentials and bulk-import into Smartlead
Export the mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard, then in Smartlead go to Email Accounts → Add Account → Bulk Import via CSV. The ColdRelay export matches the column layout Smartlead expects, so a 60-mailbox multi-metro pool lands in one pass.
Mirror your offices in Smartlead's structure
Decide the org model: a sub-account per office if each location's manager should see only their own campaigns and stats, or a single account with one campaign per metro if growth is run centrally. Either way, assign each metro campaign its slice of the ColdRelay pool — Smartlead's campaign-level mailbox rotation then spreads that market's sends across only its assigned mailboxes.
Set per-mailbox limits to the ColdRelay budget
Cap each mailbox at 2 outbound emails per day in Smartlead, mirroring ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. Warmup runs continuously inside that budget, so there's no separate warmup period before the first metro campaign launches and no need to layer Smartlead's warmup on top.
Launch the metro campaigns and work the master inbox
Clone your sequence per metro, swap in that market's local proof points and reply-to identity, and launch. Replies from every city flow into Smartlead's master inbox; tag them by campaign so each one routes to the right office's account manager. If leadership wants per-location numbers, Smartlead's API and webhooks push campaign stats into a dashboard split by metro — no logging into three views to compile a report.
The Multi-Location MSP Smartlead Playbook
One campaign per metro — never a national blast
A prospect in Phoenix deletes an email that smells like it came from a national call center, because the whole reason they'd hire an MSP is someone nearby. Structure Smartlead with a distinct campaign (or sub-account) per market so every variable — list, copy, sender identity, schedule — is set per city. The campaigns can share a sequence skeleton, but the moment one metro's stats dip you can see it, fix it, and not touch the markets that are working.
Stack local proof points per market, and let spintax keep them fresh
Each metro campaign should carry evidence only that market's prospects care about: client counts in that city, a named local vertical you dominate there, the neighborhood your office sits in. Use Smartlead's spintax to rotate among several true local proofs — one send mentions the medical group downtown, another the manufacturer by the airport — so high-volume sends into a single metro don't read as identical copies, and the campaign feels like a firm with roots rather than a template with a city variable.
Route master-inbox replies to the office that owns the relationship
Centralized sending must not mean centralized replying — a hot prospect answered by someone two time zones away undoes the local positioning the campaign built. Work Smartlead's master inbox as a routing desk: every reply is tagged by its metro campaign, handed to that office's account manager the same business day, and answered by the person who could actually drive over for the assessment. The handoff speed is the conversion lever; the master inbox is just what makes it visible.
Reallocate the mailbox pool by market opportunity, not office politics
Because the ColdRelay pool is shared, capacity follows results: review reply and meeting rates per metro quarterly, then shift mailbox assignments in Smartlead toward the markets that convert. Opening in a fourth city stops being an infrastructure project — reassign part of the pool to pilot the market, and only order a fresh tranche on ColdRelay once the pilot proves demand. Treat sending capacity like technician hours: allocated where the pipeline is, reviewed on a schedule.
Typical Multi-Location MSP Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate | 3-6% | Metro-segmented campaigns with local proof points; varies by market maturity |
| Localized vs. generic copy reply lift | 1.5-2x | Per-metro proof points and local sender identity vs. one national template |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to first metro campaign | Same day | ~60 minutes to provision the pool, plus campaign setup in Smartlead |
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) — which rewards the shared-pool model, since one consolidated multi-metro order prices better than three offices buying separately. DNS, dedicated IPs, and isolated Azure tenants are included.
Smartlead is billed separately on its own subscription for campaigns, sub-accounts, mailbox rotation, the master inbox, and API access — priced per its current plans.
One infrastructure bill sized to total mailbox count across all markets, one software bill for the platform every office works in. Adding a metro moves mailboxes between campaigns or adds a tranche to the pool — it never adds a new vendor relationship per office.
| 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 of one stack. Smartlead is the sending and segmentation software: per-metro campaigns or sub-accounts, mailbox rotation, the master inbox, spintax, API reporting. ColdRelay is the infrastructure underneath: the secondary domains, dedicated mailboxes, and dedicated IPs every one of those metro campaigns sends from. You connect ColdRelay mailboxes to Smartlead and run both together.
Should each office buy its own mailboxes, or should we share one pool?
Share the pool. One consolidated ColdRelay order lands in better volume tiers than three small per-office orders, deliverability gets managed once instead of three times, and reallocating capacity between metros becomes a Smartlead assignment change rather than a purchase. ColdRelay supports 100-150 mailboxes per domain, so even a five-market pool fits comfortably on one or two domains.
Sub-accounts or separate campaigns — how should we map our offices into Smartlead?
Use sub-accounts when each location's manager should operate independently — their own campaigns, stats, and login, with the master view kept centrally. Use one account with a campaign per metro when a central growth person runs everything and offices only receive routed replies. Both models pull from the same ColdRelay mailbox pool; the choice is about who manages campaigns, not how the infrastructure is divided.
Do we need a warmup period before launching our first metro campaigns?
No separate warmup period. ColdRelay mailboxes warm continuously — 2 warmup sends/day per mailbox as part of the 4/day total budget, alongside 2 outbound — so you can provision the pool in the morning, bulk-import into Smartlead, and launch every metro campaign the same day. Skip Smartlead's own warmup on these mailboxes; the budget already covers it.