Reply.io is a capable cold email platform — but like every sending tool, it's only as effective as the inboxes connected to it. Reply.io handles sequencing, reply detection, and CRM integration. The inboxes determine whether your emails land in the primary inbox or get filtered. Teams complaining about poor Reply.io campaign performance almost always have an inbox problem, not a platform problem. This guide covers the complete setup: connecting pre-warmed inboxes to Reply.io, configuring volume and rotation settings, and the verification steps that confirm your infrastructure is ready before the first campaign email goes out.
Connecting Pre-Warmed Inboxes to Reply.io — The Right Way
💡 TL;DR
Connect pre-warmed inboxes to Reply.io via OAuth (Google or Microsoft sign-in) — not SMTP. OAuth gives Reply.io the access needed for accurate reply detection, List-Unsubscribe header injection, and stable long-term connection. Pre-warmed GWS and MS365 inboxes from Litemail ($4.99/inbox) connect in under 5 minutes per inbox and arrive with Good/High Postmaster reputation — campaigns launch the day inboxes are delivered. Set per-inbox daily limits to 40–50 emails and enable round-robin rotation across all inboxes in the campaign.
Here's the full step-by-step — connection, configuration, and the verification checks that confirm everything is working before you send.
Step-by-Step: Connect Pre-Warmed Inboxes to Reply.io
Before connecting, confirm your inboxes pass all DNS checks. Run MXToolbox SPF, DKIM, and DMARC checks for each sending domain. All three must pass. Litemail pre-warmed inboxes are delivered with all three configured — verify before proceeding regardless.
Log into Reply.io and navigate to Settings → Email Accounts → Add Email Account
Select your inbox provider: Google for GWS inboxes, Microsoft for MS365 inboxes
Click the OAuth sign-in button for your provider and authenticate with the sending inbox's credentials — the full email address and password for that specific sending inbox
Grant Reply.io the requested permissions — these cover send, read, and label access needed for reply detection and sequence management
Once connected, open the inbox settings and configure:
Daily sending limit: 40 emails/day (start here; increase to 50 after 2 weeks of confirmed Good Postmaster reputation)
Send delay: 120–420 seconds between emails (2–7 minutes randomised)
Working hours: 8am–5pm in the recipient's time zone where possible
Repeat for each additional inbox in your pool
💡 After Connecting — Run This Verification
Send a test email from Reply.io using the newly connected inbox to a Gmail address you control. Open the email, click the three dots menu, select Show Original. Confirm: SPF: PASS, DKIM: PASS, DMARC: PASS in the Authentication-Results header. Any failure means the inbox's DNS configuration has an issue that will harm deliverability — do not launch campaigns until all three pass.
Inbox Rotation in Reply.io — Getting It Right
Reply.io supports multi-inbox campaigns where sends are distributed across a pool of connected inboxes. The rotation settings determine how evenly that distribution works and whether any single inbox gets pushed beyond its safe daily limit.
Campaign-Level Inbox Assignment
In your Reply.io campaign settings, assign all pre-warmed inboxes to the campaign under the Sending Settings section. Reply.io rotates sends across assigned inboxes automatically. The platform distributes based on available capacity — set at the per-inbox daily limit you configured during inbox setup.
The Critical Detail Most Teams Miss
Reply.io's rotation respects per-inbox daily limits — but only if those limits are configured at the inbox level, not just at the campaign level. Campaign-level daily limits divide the total across however many inboxes are connected. If you add a new inbox mid-campaign, the per-inbox share changes. Per-inbox limits at the account level enforce an absolute ceiling regardless of campaign assignment changes.
Mixed GWS and MS365 in One Campaign
Reply.io supports mixed inbox types in the same campaign — GWS and MS365 inboxes can both be assigned to a single campaign and rotated together. For mixed prospect lists (some Gmail recipients, some Exchange recipients), this provides a natural distribution advantage: Gmail-hosted prospects tend to get better placement from GWS inboxes in the rotation, Exchange-hosted prospects from MS365 inboxes.
Why Inbox Quality Determines Reply.io Results More Than Platform Settings
Reply.io's platform capabilities — multi-step sequences, A/B testing, reply detection, CRM sync — are consistent regardless of the inboxes connected. The performance difference between high-performing and underperforming Reply.io campaigns is almost always in the inboxes, not the platform.
In our testing at Litemail, teams using Reply.io with fresh inboxes (61% primary inbox placement) versus pre-warmed inboxes (94–96% placement) showed a 54% difference in effective email reach from identical campaign configurations. Same sequences, same Reply.io settings, same prospect lists. The platform delivered identically — the inboxes determined how many emails actually reached a human.
Reply.io's reply detection is also more accurate when inboxes are connected via OAuth versus SMTP. OAuth gives Reply.io deeper access to inbox events, reducing false negatives in reply detection — situations where a prospect replied but Reply.io didn't detect it and continued the sequence. This matters particularly for Reply.io's AI-powered reply categorisation, which requires accurate reply data to function correctly.
Monitoring Reply.io Inbox Health
Reply.io provides per-inbox sending statistics that serve as the first layer of health monitoring. Check these weekly:
Emails sent vs daily limit: Any inbox consistently at exactly its daily limit may need the limit reviewed — if demand exceeds the inbox pool capacity, add inboxes rather than increasing per-inbox limits.
Bounce rate per inbox: Reply.io tracks bounced emails per inbox. Any inbox above 2% of sends in a week should be paused for list investigation.
Reply rate by inbox: A sudden drop of 30%+ in reply rate from a specific inbox often indicates deliverability degradation before Postmaster shows it. Investigate the inbox specifically if it's significantly underperforming others in the same campaign.
Supplement Reply.io's in-platform data with weekly Google Postmaster Tools checks on all sending domains. Postmaster shows domain-level reputation that per-inbox platform metrics don't directly surface. Keep spam complaint rate below 0.08% — Google's 2026 threshold — by checking Postmaster weekly and adjusting targeting or copy if complaint rate approaches 0.05%.
Connect Pre-Warmed Inboxes to Reply.io in Minutes
Litemail pre-warmed inboxes — $4.99/inbox, connects to Reply.io via Google or Microsoft OAuth, Good/High Postmaster within 48 hours, automated DNS. Campaigns launch the day inboxes are delivered.
Get Pre-Warmed Inboxes from $4.99 →
Connects to Reply.io via OAuth · No minimum order · GWS and MS365 · Delivered in 24 hours
About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach. From $4.99/inbox with automated DNS, dedicated US and EU IPs, and full admin access. View pre-warmed inbox plans →
Related reading:
Reply.io Inbox Alternatives 2026 · Reply.io Review 2026 · SPF/DKIM/DMARC Auto-Setup 2026 · Pre-Warmed Inbox Rotation Strategy for High Volume · Best Pre-Warmed Inbox Providers 2026 (Ranked)
Key Takeaways
Connect pre-warmed inboxes to Reply.io via OAuth (Google or Microsoft sign-in) — not SMTP. OAuth enables accurate reply detection, List-Unsubscribe header injection, and more stable long-term connection than SMTP app passwords.
Set per-inbox daily limits at the inbox account level (40 emails/day to start) — not only at the campaign level. Per-inbox account-level limits enforce an absolute ceiling regardless of campaign assignment changes or new inbox additions.
After connecting each inbox, send a test email through Reply.io and verify SPF: PASS, DKIM: PASS, DMARC: PASS in the Gmail headers before launching campaigns. Any failure means DNS has an issue — fix before sending.
Inbox quality determines Reply.io results more than any platform setting. Teams using pre-warmed inboxes (94–96% placement) versus fresh inboxes (61% placement) see a 54% difference in effective email reach from identical Reply.io configurations.
Monitor per-inbox reply rate trends weekly in Reply.io. A 30%+ drop in reply rate from a specific inbox often precedes a visible Postmaster reputation change by 3–5 days — it's an early deliverability warning.
Frequently Asked Questions
How do I connect Google Workspace to Reply.io?
In Reply.io: Settings → Email Accounts → Add Email Account → Google. Click the Google OAuth sign-in button, authenticate with the sending inbox's credentials, and grant the required permissions. Connection takes 3–5 minutes per inbox. After connecting, set the per-inbox daily limit to 40 emails and configure a 2–7 minute randomised send delay. Verify SPF/DKIM/DMARC pass via a test email before running campaigns.
Should I connect inboxes to Reply.io via SMTP or OAuth?
OAuth — always. OAuth gives Reply.io deeper integration with your Google or Microsoft account, enabling accurate reply detection, proper List-Unsubscribe header injection, and more stable connections than SMTP app passwords. Google is also progressively restricting high-volume SMTP access for Workspace accounts, making OAuth the more reliable long-term connection method. Pre-warmed inboxes from Litemail support OAuth connection to Reply.io out of the box.
How many inboxes do I need for Reply.io campaigns?
One inbox per 30–50 cold emails per day. For 500 emails per day in Reply.io: 10–17 inboxes. For 1,000 emails per day: 20–34 inboxes. At Litemail's $4.99/inbox, 20 pre-warmed inboxes costs $99.80/month — the infrastructure for 1,000 daily Reply.io sends. Start with the minimum needed for your target volume and add inboxes as you scale.
Why is my Reply.io campaign underperforming despite good sequences?
Check inbox placement before rewriting sequences. If your inboxes have Unknown or Medium Postmaster reputation — fresh inboxes or degraded inboxes — emails are landing in spam before anyone reads the sequence. Check Google Postmaster Tools for your sending domains. If reputation is below Good, fix infrastructure first. Switching to pre-warmed Litemail inboxes (Good/High Postmaster from day one) typically increases effective email reach by 30–54% from identical Reply.io configurations.
Pre-Warmed Inboxes for Reply.io — Connected and Campaign-Ready in Hours
Litemail pre-warmed inboxes — $4.99/inbox, connects to Reply.io via OAuth in under 5 minutes, Good/High Postmaster reputation from day one, automated SPF/DKIM/DMARC, dedicated US and EU IPs. Launch campaigns the day inboxes are delivered. No minimum order.
Get Pre-Warmed Inboxes from $4.99 →
Connects to Reply.io via OAuth · No minimum order · Good/High Postmaster within 48hrs · US and EU IPs included
About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach. From $4.99/inbox with automated DNS setup, dedicated US and EU IPs, 4 to 12 weeks of genuine warm-up history, and full admin access. View pre-warmed inbox plans →
Related reading: Reply.io Inbox Alternatives 2026 · Reply.io Review 2026 · Pre-Warmed Inbox Rotation for High Volume · Best Pre-Warmed Inbox Providers 2026 (Ranked)
