Outbound Organized the Way Your Agency Is
Most PPC agencies aren't one team — they're pods. A Google Ads pod, a Meta pod, maybe a TikTok or Amazon PPC specialist. Each pod has its own proof points, its own vocabulary, and its own ideal prospect. Yet most agency outbound flattens all of that into one generic "we do paid media" sequence, and the reply rate shows it.
Smartlead's structure maps cleanly onto the pod model: one campaign per platform specialty, each with its own mailbox rotation, its own spintax variants, and its own slice of the Master Inbox. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs each campaign actually sends from. This guide covers how to wire the two together so a Google Ads prospect hears from your Google Ads pod, in Google Ads language, and never from a generalist.
Why Run Smartlead on ColdRelay Infrastructure
Smartlead is a sending and sequencing platform — it sends from whatever mailboxes you connect to it. It doesn't provision domains or guarantee the deliverability of the mailboxes themselves; that's the infrastructure layer's job.
That's where ColdRelay fits. Instead of standing up workspace seats and hand-configuring DNS for every domain, 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 budget — so a new platform pod can have its own sending capacity live the same afternoon you decide to spin it up.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Smartlead is the sender on top. You keep Smartlead's campaign-level mailbox rotation, spintax engine, Master Inbox, and API — you just point them at mailboxes built to land. For a multi-pod agency, the campaign-level rotation is the key piece: it lets each platform specialty draw from its own dedicated slice of the mailbox pool.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead, Pod by Pod
Provision a mailbox pool per platform pod on ColdRelay
Order secondary domains adjacent to your agency brand — never your client-facing domain. ColdRelay supports 100-150 mailboxes per domain, so even one domain can carry several pods; a typical three-pod agency starts with 90-150 mailboxes split across Google Ads, Meta, and a third specialty. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Bulk-import the mailboxes under Email Accounts
Export the mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard, then use Smartlead's bulk CSV import under Email Accounts to connect the whole pool in one upload. Tag accounts by pod as you import — a consistent naming convention like ga-, meta-, ttk- in the sender names makes the next step trivial.
Create one Smartlead campaign per platform specialty
Build separate campaigns for Google Ads, Meta, TikTok, and Amazon PPC prospects, and attach only that pod's mailboxes to each campaign. Smartlead's campaign-level mailbox rotation then spreads each pod's sends across its own pool — Google Ads outreach never borrows Meta's capacity, and a deliverability wobble in one pod can't drag down the others.
Set per-mailbox limits to match the ColdRelay budget
Cap each account's daily campaign sends at 2 outbound emails per day, mirroring ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. Leave ColdRelay's continuous warmup running rather than stacking Smartlead's warmup on top. A 40-mailbox pod gives that platform team 80 outbound sends/day, independently of its siblings.
Wire Smartlead's webhooks into your agency dashboard
Use Smartlead's API and webhooks to push sent, open, and reply events per campaign into the same white-label reporting dashboard your clients already see for ad performance. New-business pipeline by platform pod becomes one more chart next to ROAS — and pod leads can see exactly what their outbound is producing without logging into Smartlead.
The PPC Agency Smartlead Playbook
One campaign per platform, with platform-native proof
A Quality Score anecdote means nothing to a TikTok advertiser, and a thumb-stop-rate story means nothing to an Amazon seller. Keep each Smartlead campaign's copy entirely inside its platform's vocabulary — Performance Max and search-term waste for Google Ads, creative fatigue and CAPI for Meta, ACoS and Sponsored Products for Amazon. Specificity is the proof that the pod actually lives on that platform.
Use spintax for vertical variants, not just synonym shuffling
Smartlead's spintax support is usually wasted on swapping greetings. Use it structurally instead: within each platform campaign, spin whole proof-point clauses by vertical — {ecom CPA story|lead-gen CPL story|app-install story} — so a single campaign reads natively to every vertical on the list while staying one campaign to manage and measure.
Triage the Master Inbox by pod, not by whoever's free
Route reply handling so each platform pod owns its own slice of Smartlead's Master Inbox. A reply asking about Performance Max budget pacing should get an answer from the Google Ads lead within hours, not a generic "let me loop in the team" from an SDR. The first reply is the first deliverable — make it sound like the pod the prospect would actually hire.
Treat pods as separate funnels in your reporting
With webhook events flowing into your agency dashboard, benchmark each platform campaign on its own: replies per 100 sends, calls booked per pod, close rate by specialty. You'll quickly learn which pod's outbound deserves more mailboxes — and because capacity is provisioned per pod on ColdRelay, scaling the winner doesn't mean rebuilding anything, just adding mailboxes to its pool.
Typical PPC Agency Outbound Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools |
| Reply rate, platform-specific campaigns | 3-6% | Platform-native copy from a named pod beats generalist agency outreach |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time to launch a new platform pod's outbound | Same day | ~60 minutes to provision its mailbox pool, plus campaign setup in Smartlead |
| Spintax variants per platform campaign | 3-5 vertical branches | Enough to read natively per vertical without fragmenting campaign data |
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 because pricing is per mailbox, each pod's capacity is a line item you can scale independently.
Smartlead is billed separately on its own subscription for campaigns, mailbox rotation, spintax, the Master Inbox, and API access — priced per its current plans.
Infrastructure cost scales with total mailbox count across pods; Smartlead's cost scales with plan tier. Because both layers are pooled across every platform campaign, adding a fourth pod is an incremental mailbox order, not a new stack.
| 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 doing different jobs. Smartlead handles campaigns, mailbox rotation, spintax, and reply management in the Master Inbox. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Smartlead sends from. You use them together — infrastructure below, sending software on top.
Should each platform pod get its own domain, or share one?
Either works. ColdRelay supports 100-150 mailboxes per domain, so a smaller agency can run three pods on one domain and separate them at the Smartlead campaign level. Larger agencies often give each pod its own secondary domain so sender identity matches the pod's specialty. Both setups keep everything off your client-facing domain.
Can we white-label outbound reporting for the agency dashboard our clients see?
Yes — that's what Smartlead's API and webhooks are for. Push per-campaign sent, open, and reply events into the same dashboard you use for client ad reporting, so new-business pipeline by platform pod sits alongside ROAS and spend. ColdRelay supplies the sending infrastructure underneath; the reporting layer is entirely yours to brand.
Do I still need Smartlead's warmup if I use ColdRelay?
ColdRelay mailboxes run their own continuous warmup — 2 warmup sends/day per mailbox as part of the 4/day budget — so there's no waiting period before a new pod's campaign can launch. You generally don't need to stack Smartlead's warmup on top; point Smartlead at outbound sending only.