How Reply.io + ColdRelay Work Together
ColdRelay (Infrastructure)
ColdRelay provides the mailboxes Reply.io sends from. Each mailbox is a Microsoft 365 account on a dedicated, isolated Azure tenant with its own dedicated IP, fully-automated DNS (SPF, DKIM, DMARC), and a 95% inbox-placement guarantee. ColdRelay's pricing is per-mailbox: $1 (1-199), $0.85 (200-999), $0.70 (1K-4,999), $0.55 (5K+). Setup completes in 60 minutes, no warmup wait.
Reply.io (Sending Platform)
Reply.io is a multichannel sales engagement platform — email, LinkedIn, calls, SMS, and WhatsApp in one workflow. It handles sequences, A/B testing, AI personalization, reply detection, and analytics across many mailboxes. Reply.io does NOT provide the underlying email infrastructure. You bring your own mailboxes via SMTP/IMAP credentials, and Reply.io orchestrates the sends across them alongside your other channels.
Why use them together
Reply.io is the multichannel brain (email sequences, LinkedIn touches, AI replies, call/SMS steps). ColdRelay is the email-infrastructure body (mailboxes, IPs, DNS). The combination gives you a clean separation: Reply.io handles cross-channel orchestration, ColdRelay handles inbox-placement quality. Switching either side later is straightforward because they're loosely coupled — if you change engagement platforms, the ColdRelay mailboxes still work.
Connect Reply.io to ColdRelay (Step-by-Step)
- 1
Order ColdRelay mailboxes
Sign up at coldrelay.com/sign-up, pick a domain (ColdRelay handles registration for $14), and order your mailbox count. The minimum is 50 mailboxes ($50/month at the base tier). ColdRelay's automation provisions the dedicated mail server, registers the domain, and creates all mailboxes inside an isolated Azure tenant.
Note: Provisioning takes 60 minutes end-to-end. You'll receive a CSV with every mailbox's SMTP host, port, username, and password once it's complete.
- 2
Wait for DNS propagation
ColdRelay configures SPF, DKIM, and DMARC records automatically on the new domain. DNS propagation usually completes in under an hour but can take up to 24. You can verify with the Email Deliverability Test at coldrelay.com/tools/email-deliverability-test — when SPF, DKIM, DMARC, and MX all show as configured, you're ready.
Note: Don't start sending before all four records (SPF, DKIM, DMARC, MX) verify correctly. Sending before authentication is in place causes immediate spam-folder placement.
- 3
Connect mailboxes to Reply.io
In Reply.io, go to Settings → Email Accounts → Add Account → Other (SMTP/IMAP). For each ColdRelay mailbox, paste its SMTP host (box.YOURDOMAIN.com), SMTP port (587), SMTP username (the full email address), and the password from the ColdRelay CSV. Configure IMAP using the same host on port 993 with TLS. Reply.io tests the connection and marks the account as Active once it validates.
Note: Pick the Other / Custom SMTP option, not the Google or Microsoft 365 OAuth buttons. ColdRelay mailboxes authenticate via SMTP password, not OAuth — picking the wrong account type leaves Reply.io waiting for an OAuth redirect that never resolves.
- 4
Set daily limits per mailbox
In each Reply.io email account's settings, set the Daily Limit (sometimes labeled 'emails per day') to 2 outbound emails. This matches ColdRelay's per-mailbox cap (designed for optimal deliverability, not maximum volume). With 50 mailboxes you can send 100 outbound emails/day; 200 mailboxes = 400/day; 1,000 mailboxes = 2,000/day.
Note: Going higher than 2/day/mailbox is the single fastest way to degrade deliverability. ColdRelay's pricing model assumes 2/day — if you need 5,000+ emails/day, add more mailboxes, don't push existing ones harder. Reply.io will happily let you set 100/day per mailbox; that's a footgun.
- 5
Enable Reply.io's email warm-up
Reply.io ships a built-in warm-up add-on. From Settings → Email Accounts → [account] → Warm-Up, enable it for each ColdRelay mailbox. Set the daily warm-up cap to 2 emails and let Reply.io ramp the schedule automatically over the first 2 weeks. The warm-up network exchanges and replies to messages from other Reply.io warm-up participants to build the mailbox's reputation.
Note: Reply.io's warm-up is a paid add-on on most plans — confirm it's included in your subscription before you depend on it. ColdRelay mailboxes ship reputation-ready (the Azure tenant + dedicated IP isolation gives you a clean start) but warm-up is still recommended for the first 2 weeks of active sending.
- 6
Build your sequence and assign mailboxes
In Reply.io, create a new Sequence, paste your prospect list, and design the steps (email touches, LinkedIn invites, manual call/SMS tasks, follow-ups). Under Sequence Settings → Sending Mailboxes, attach your ColdRelay mailboxes as the sending accounts. Reply.io rotates sends across all assigned mailboxes while respecting each one's daily cap.
Note: Use Reply.io's {{variables}} and AI-generated openers for personalization, but always pair them with subject-line spintax. The Spintax Generator at coldrelay.com/tools/spintax-generator generates Reply.io-compatible syntax to avoid mailbox fingerprinting.
- 7
Configure reply handling and the unified inbox
Reply.io's reply detection auto-pauses sequences when a prospect replies and routes messages into the Inbox tab. Verify that each ColdRelay mailbox's IMAP connection stays green — Reply.io polls IMAP on port 993 to surface replies. For team workflows, assign categories (Interested, Not Now, Not Interested) so the AI categorizer can learn your routing.
Note: If replies aren't showing up in the Reply.io inbox, the IMAP credentials are almost always the culprit. Re-test the connection from the email account settings before debugging the sequence.
- 8
Monitor deliverability ongoing
Run the Email Deliverability Test weekly to verify SPF/DKIM/DMARC stay passing. Check Google Postmaster Tools for spam-folder rates and IP reputation. ColdRelay automatically monitors blocklists — you'll get an alert if any of your dedicated IPs hit a major blocklist (Spamhaus, Barracuda, SORBS, SpamCop).
Note: ColdRelay's 95% inbox-placement guarantee is contingent on following the 2/day/mailbox cap. Exceeding the cap voids the guarantee — and Reply.io's per-account limits are the lever to enforce it.
Key Considerations for Reply.io + ColdRelay
Daily send limits per mailbox
Set Reply.io's per-mailbox daily limit to 2 outbound + 2 warm-up = 4 total/day MAX. This is ColdRelay's optimal-deliverability cap. Going higher is the single biggest cause of mailbox burnout we see. Scale total volume by adding more mailboxes, not by pushing existing ones harder.
Dedicated IPs end shared-IP risk
Each ColdRelay mailbox is on a dedicated IP within your isolated Azure tenant. Reply.io users sending through shared infrastructure share IP reputation with random other senders — bad actors on the same IP damage everyone's deliverability. With ColdRelay your IP reputation is entirely your own.
Multichannel sequences keep working
Reply.io's strength is mixing email with LinkedIn touches, calls, SMS, and WhatsApp steps in one sequence. ColdRelay only affects the email leg — your LinkedIn, calling, and SMS steps continue to work exactly as before. Email gets dramatically more reliable; the other channels are unchanged.
AI features still apply
Reply.io's Jason AI assistant, generative replies, and AI categorization operate on top of whatever mailbox you connect. They don't care that ColdRelay is the SMTP provider underneath. Personalization quality, reply-detection accuracy, and categorization are exactly the same with ColdRelay mailboxes as with Google Workspace ones.
Switching cost is low
If you decide Reply.io isn't right and want to switch to Smartlead, Instantly, or another engagement platform later, your ColdRelay mailboxes work with any platform that supports custom SMTP/IMAP. You don't lose the infrastructure investment.
Domain-rotation strategy
ColdRelay caps each domain at 100-150 mailboxes for deliverability reasons. If you need 500+ mailboxes, you'll order multiple domains. Reply.io handles multi-domain campaigns natively — group mailboxes from each domain into separate sequence tracks to spread risk and isolate any single-domain reputation hit.
Pricing Snapshot
ColdRelay
ColdRelay's per-mailbox cost ranges from $1.00 (1-199 mailboxes) down to $0.55 (5,000+). Domain registration is $14/year, one-time. For 200 mailboxes: 200 × $0.85 = $170/month + $14 annual domain cost.
Reply.io
Reply.io is priced per user. The Email Volume plan starts around $59/user/month and covers 1,000 active contacts. The Multichannel plan is roughly $99/user/month and adds LinkedIn, calls, SMS, and WhatsApp. The Agency plan starts around $166/month for 5 users and is designed for managing multiple client workspaces. Pricing scales with seats and channels, not mailbox count.
Total monthly
A typical 200-mailbox cold email operation: ColdRelay infrastructure at ~$170/month + Reply.io Multichannel at ~$99/user/month for a single founder = ~$269/month total. For an agency running 1,000 ColdRelay mailboxes across 3 clients on the Reply.io Agency plan: ColdRelay $700/month + Reply.io ~$166/month = ~$866/month. Compare against Google Workspace at $6+/mailbox/month: 200 GW mailboxes alone would be $1,200/month before Reply.io's seat cost.
Common Issues + Fixes
⚠ Reply.io email account stuck in 'Connecting' or asking for an OAuth login
You picked the Google or Microsoft 365 account type instead of Other / Custom SMTP. ColdRelay mailboxes authenticate via SMTP password, not OAuth. Delete the account in Reply.io and re-add it via Settings → Email Accounts → Add Account → Other, then paste the SMTP host, port 587, the full address as username, and the password from the ColdRelay CSV.
⚠ Warm-up enabled in Reply.io but no warm-up activity is showing
Reply.io's warm-up is a paid add-on on most plans — confirm it's enabled on your subscription, not just toggled on the account. Also check the warm-up daily cap; if it's left at the default high number, Reply.io may be queuing but not actually sending because the mailbox's main daily limit (set to 2) is consumed by sequence sends first. Lower the main daily limit during the first warm-up week if needed.
⚠ Emails landing in spam at Gmail
Run the Email Deliverability Test against the domain. If SPF, DKIM, or DMARC fails, the records may not have propagated yet — wait 24 hours. If they all pass, check Google Postmaster Tools for the domain. The most common cause of post-authentication spam placement is exceeding the 2/day/mailbox cap in Reply.io — verify the per-account daily limit hasn't been overridden at the sequence level.
⚠ Inbox-placement test shows missing DKIM
ColdRelay's DKIM is on the domain's _dkim.YOURDOMAIN.com selector. If a test reports missing DKIM, it usually means the test ran before DNS propagation completed. Wait 24 hours from provisioning and re-test. If still missing, contact ColdRelay support — there's a deliverability consultant included at higher mailbox volumes.
⚠ Reply.io inbox shows no replies even though prospects are replying
Reply.io polls IMAP on port 993 with TLS. Verify the IMAP credentials match the ColdRelay CSV (the IMAP password is the same as the SMTP password but it can drift if a mailbox was reset). Re-test in Reply.io's email account settings (the Test Connection button) and re-save. If IMAP is green but replies still don't appear, check that the sequence has 'Stop on reply' enabled — without it, Reply.io may not parse incoming messages against the sequence.
Frequently Asked Questions
Do I need ColdRelay if I already have Reply.io?
Reply.io is an engagement platform — it doesn't provide mailboxes or DNS. You need an infrastructure provider (ColdRelay, Google Workspace, etc.) underneath it. Most Reply.io users start with Google Workspace mailboxes ($6+/mailbox/month) and switch to ColdRelay because the infrastructure is purpose-built for cold email at a fraction of the cost ($0.55-$1.00/mailbox).
Is ColdRelay better than Google Workspace for use with Reply.io?
For cold email at any scale beyond a handful of mailboxes: yes. Google Workspace charges $6+/mailbox/month and shares some risk across all GW senders. ColdRelay charges $0.55-$1.00/mailbox/month, gives each customer a dedicated Azure tenant with dedicated IPs, and bakes SPF/DKIM/DMARC automation into provisioning. The infrastructure quality is closer to enterprise-grade at indie-tool prices.
How many mailboxes do I need to scale to my target send volume?
ColdRelay's per-mailbox cap is 2 outbound emails/day for optimal deliverability. So if you want to send 1,000 emails/day through Reply.io, you need 500 mailboxes. The Mailbox Calculator at coldrelay.com/tools/mailbox-calculator lets you input your target volume and gives you the exact mailbox count + pricing tier.
Do Reply.io's LinkedIn, call, and SMS steps still work with ColdRelay?
Yes — ColdRelay only provisions the email leg of the sequence. Reply.io's LinkedIn automation, click-to-call dialer, SMS, and WhatsApp steps are independent of which SMTP provider you use. Your multichannel sequences continue to function identically; only email reliability improves.
Will my Reply.io sequences break if I switch to ColdRelay from another provider?
No. Switching infrastructure providers mid-sequence requires reconnecting each mailbox in Reply.io (new SMTP/IMAP credentials), but sequence logic, A/B variants, and contact lists stay intact. The transition takes a few minutes per mailbox. We recommend pausing sequences during the swap to avoid any deliverability blips.
Does Reply.io's Agency plan make sense with ColdRelay?
It's a strong combination for cold email agencies. The Reply.io Agency plan (~$166/month for 5 users) gives you multi-workspace management, and ColdRelay's per-mailbox pricing scales cleanly across clients — you can dedicate a separate domain and isolated Azure tenant to each client's campaigns while running everything from one Reply.io account. See the cold-email-infrastructure-for-agencies page for the full agency-stack walkthrough.
What if Reply.io's deliverability is bad with my ColdRelay mailboxes?
That's almost always a campaign-content issue (subject lines triggering spam filters, link density too high, sender names looking off) rather than an infrastructure issue. ColdRelay's 95% inbox guarantee means the infrastructure is doing its job. Use the CAN-SPAM Checker at coldrelay.com/tools/can-spam-checker and the Subject Line Generator to validate sequence content. ColdRelay's deliverability consultant (included at higher volumes) can help diagnose.