Enterprise SDR Cadences, Without the Domain Risk
Salesloft is the operating system for most structured sales teams — cadences, per-rep mailboxes, Salesforce sync, and analytics that tell a manager exactly which step of which cadence is converting. What Salesloft doesn't decide is which mailboxes those cadences send from. By default, every SDR connects their corporate @company.com mailbox and starts running cold steps from it.
That default is where deliverability problems start. This guide covers the split that mature RevOps teams make: cold, top-of-funnel cadence volume moves to dedicated ColdRelay mailboxes on secondary domains, while warm replies and late-stage threads stay on corporate mailboxes — all still orchestrated inside Salesloft.
Why Run Salesloft Cadences on ColdRelay Infrastructure
The classic failure mode on an SDR floor looks like this: ten reps each running 100+ cold sends a day from their corporate mailboxes. For a few months it works. Then open rates slide, prospects stop seeing the emails, and eventually the whole org's domain reputation is damaged — including the CEO's email to a board member landing in spam. Because everyone shares one domain, every rep's cold volume is everyone's problem.
ColdRelay fixes the layer Salesloft sits on top of. RevOps provisions dedicated mailboxes on secondary domains — isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured — in about an hour. Each rep gets a pool of sending identities for cold cadences, and the corporate domain is never exposed to top-of-funnel volume again.
The two products are complementary, not competing: Salesloft remains the engagement layer — cadences, reply handling, Salesforce sync, analytics — and ColdRelay is the infrastructure layer underneath it, supplying the domains, mailboxes, and IPs those cadences actually send from.
Visit Salesloft →Connecting ColdRelay Mailboxes to Salesloft
Provision the team's sending pool on ColdRelay
RevOps picks secondary domains adjacent to the corporate brand (e.g., trycompany.com, getcompany.io) and provisions mailboxes on isolated Azure tenants with dedicated IPs. ColdRelay supports 100-150 mailboxes per domain, so a 10-rep team typically starts with 100-300 mailboxes across 2-3 domains. DNS (SPF, DKIM, DMARC) comes pre-configured, and the whole pool is ready in about an hour.
Assign mailboxes per rep and connect them in Salesloft
Distribute mailboxes evenly across the team — 10-30 per SDR is a common starting allocation. Each rep (or an admin acting on their behalf) connects their assigned mailboxes in Salesloft under Settings → Email → Connected Mailboxes, alongside the corporate mailbox they keep for warm threads.
Set admin-level send limits to match the mailbox budget
In Salesloft's admin send-limit governance settings, cap each connected ColdRelay mailbox at 2 cold emails per day. That mirrors ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup — with warmup running continuously on ColdRelay's side, so there's no separate warmup period before reps can start sending.
Build cold cadences on the new identities
Create top-of-funnel cadences in Salesloft with email steps routed through the ColdRelay mailboxes, mixing in the call and LinkedIn steps your team already runs. Keep nurture and re-engagement cadences for existing opportunities on corporate mailboxes — the routing rule is simple: cold list, ColdRelay identity; known contact, corporate identity.
Wire Salesforce sync and monitor cadence analytics
Salesloft's Salesforce sync logs every cold touch against the lead or contact record regardless of which mailbox sent it, so attribution stays clean. Use Salesloft's cadence analytics to compare reply rates per cadence and per rep, and scale the ColdRelay pool when the team's daily send capacity becomes the bottleneck.
The Sales Team Salesloft Playbook
Make the cold/warm split a RevOps policy, not a rep choice
Codify it: any first touch to a net-new prospect sends from a ColdRelay mailbox; any thread with an open opportunity sends from the rep's corporate mailbox. Enforce it with Salesloft's admin send-limit governance so a single rep can't quietly route 150 cold sends/day through @company.com.
Budget capacity per rep, not per campaign
At 2 cold sends/day per mailbox, a rep with 25 ColdRelay mailboxes has 50 cold touches/day — roughly 1,000 per month. Size each SDR's mailbox allocation to their quota math first, then let cadence design decide how those touches are spent.
Move the conversation to corporate on first reply
When a prospect replies to a cold step, have the rep continue the thread from the ColdRelay identity but book the meeting under their corporate calendar and move all post-meeting follow-up to @company.com. Warm pipeline lives where executives, legal, and procurement expect it to.
Let cadence analytics drive copy, not volume
When a cadence underperforms, the instinct on an SDR floor is to add sends. With a fixed 2-outbound-per-mailbox budget, the lever is quality: use Salesloft's per-step analytics to find the step where replies die, rewrite it, and A/B across reps before adding a single mailbox.
Typical Sales Team Outbound Benchmarks (Salesloft + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants vs. a shared corporate domain carrying every rep's volume |
| Reply rate on cold cadences | 1.5-4% | Enterprise ICPs trend lower than SMB; multi-channel cadences (email + call + LinkedIn) land at the top of the range |
| Cold capacity per rep | 50/day | 25 mailboxes × 2 outbound/day each (4 sends/day total per mailbox — 2 outbound + 2 warmup) |
| Time to first cadence send | Same day | ~60 minutes to provision the pool, then mailbox connection and cadence setup in Salesloft |
| Reputation risk to the corporate domain | Zero | All cold volume runs on separate ColdRelay domains — the CEO's email never pays for SDR sends |
What It Costs: Salesloft + ColdRelay
Infrastructure is billed per mailbox per month, with volume tiers that drop as you scale (see the table below) — meaningful for SDR teams provisioning 100+ mailboxes at once. Domains' DNS setup, dedicated IPs, and isolated Azure tenants are included.
Salesloft is billed separately per seat on its own plans, covering cadences, the dialer, Salesforce sync, and analytics.
The costs scale on different axes: Salesloft with headcount, ColdRelay with sending capacity. A team can double its cold volume by adding mailboxes without adding a single Salesloft seat — and vice versa.
| 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; Salesloft handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Is ColdRelay a replacement for Salesloft?
No — they're complementary layers of the same stack. Salesloft is the sales engagement layer: cadences, reply handling, dialer, Salesforce sync, and analytics. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs those cadences send from. Teams run both together.
Our SDRs already send cold email from their corporate mailboxes. Why change?
Because every rep shares the corporate domain's reputation. Ten reps at 100+ cold sends/day will eventually drag the whole org into spam folders — including executive and customer-facing email. Moving cold volume to ColdRelay mailboxes on secondary domains isolates that risk completely while warm threads stay on @company.com.
Do reps need to warm up the new mailboxes before launching cadences?
No separate warmup period. ColdRelay mailboxes warm continuously as part of the standard budget — each mailbox sends 4 emails/day total, 2 outbound + 2 warmup — so reps can start cold cadence sends the same day the pool is provisioned.
How many mailboxes does an SDR team need?
Work backwards from cold touches per rep. At 2 outbound sends/day per mailbox, a rep needing 50 cold emails/day needs 25 mailboxes; a 10-rep team at that pace needs 250. With 100-150 mailboxes supported per domain, that's a pool across 2-3 secondary domains, and RevOps can scale it as quota math changes.