Lemlist's built-in inbox management works for teams just starting out. But the teams hitting 3 to 5% reply rates consistently are almost always running external pre-warmed inboxes connected to Lemlist — not the platform's default sending infrastructure. The difference is not the tool. It is the inbox underneath the tool.
💡 TL;DR
Lemlist's default inbox infrastructure uses shared IPs — which deliver 65 to 75% inbox placement on new campaigns. Connecting Litemail pre-warmed inboxes at $4.99/inbox/month via SMTP or OAuth raises this to 94–96% from day one. The setup takes under 20 minutes per inbox. In a direct comparison with the same Lemlist sequence and same ICP list, external pre-warmed dedicated IP inboxes generated 3.1% reply rate versus 0.9% from Lemlist's default inboxes. The only variable was inbox infrastructure. Pre-warmed inboxes are available on Google Workspace and Microsoft 365 — both supported by Lemlist's connection options.
Why Lemlist's Default Inbox Setup Underperforms for Cold Email
Lemlist is a strong cold email platform. Its personalisation capabilities — dynamic images with prospect names, custom intro videos, liquid syntax variables — are genuinely best-in-class for creative sequences. What it is not strong on is inbox infrastructure. The platform's default sending inboxes run on shared IPs. That means your campaigns share a reputation pool with every other Lemlist user sending from the same IP range.
A content marketing agency running cold outreach for their SaaS clients ran a 30-day test in Q4 2025. Same Lemlist sequence, same ICP (VP Marketing at B2B SaaS companies), same copy. Six inboxes on Lemlist's default infrastructure. Six Litemail pre-warmed inboxes connected via SMTP. The result: default inboxes averaged 0.9% reply rate. Litemail inboxes averaged 3.1%. The team switched all client campaigns to external inboxes within the week. Monthly infrastructure cost increase: $29.94 for 6 Litemail inboxes. Monthly reply rate impact: 320% improvement.
How to Connect Pre-Warmed Inboxes to Lemlist — Step by Step
Lemlist supports connecting external sending inboxes via SMTP and OAuth (Google and Microsoft direct connections). OAuth is the cleaner option — it provides better authentication, more reliable connection, and avoids the app password complexity of SMTP. Here is the exact setup process for both.
🔧
Google Workspace OAuth connection (recommended)
In Lemlist: Settings → Email Providers → Add email account → Connect with Google. Sign in with the Google Workspace account credentials for the Litemail inbox. Lemlist requests access to send email on behalf of the account. Grant access. The connection is live. No SMTP credentials needed, no app passwords, no port configuration. Verify by sending a test email from within Lemlist before activating any sequences.
🔧
Microsoft 365 OAuth connection
In Lemlist: Settings → Email Providers → Add email account → Connect with Microsoft. Sign in with the Microsoft 365 account credentials. Grant Lemlist access. Same process as Google OAuth — clean, no SMTP configuration needed. Microsoft 365 connections are recommended for teams targeting enterprise accounts where M365-to-M365 sending benefits from within-ecosystem reputation alignment.
🔧
SMTP connection (if OAuth is not available)
In Lemlist: Settings → Email Providers → Add email account → Connect via SMTP. For Google Workspace: SMTP server smtp.gmail.com, Port 587 (TLS) or 465 (SSL), username is the full inbox email address, password is an app-specific password generated in Google Account Security settings. For Microsoft 365: SMTP server smtp.office365.com, Port 587, username is the full address, password is the account password with modern auth enabled.
Inbox Rotation in Lemlist With External Inboxes
Lemlist's inbox rotation feature distributes sends across multiple connected inboxes. When configured with pre-warmed external inboxes, this gives you both the placement quality of dedicated IPs and the volume capability of distributed sending. Here is how to configure it correctly.
In Lemlist, after connecting multiple inboxes, you can assign rotation at the campaign or sequence level. Enable rotation in campaign settings and select which inboxes to include in the pool. Lemlist distributes sends round-robin by default — you can weight the distribution toward specific inboxes if you want to preserve a particular inbox for follow-up sends.
The recommended rotation setup for a team sending 500 to 1,000 emails per day: 4 to 7 connected pre-warmed inboxes across 2 to 3 sending domains, each inbox at 150 to 200/day maximum. This configuration keeps every inbox under the daily ceiling where inbox placement stays consistent and gives you redundancy if any single inbox shows deliverability signals requiring a pause.
[INTERNAL LINK: Google Workspace cold email volume guide → /blog/google-workspace-cold-email-500-per-day-limit]
Lemlist's Personalisation Features + Clean Infrastructure — The Combination
Lemlist's differentiated value is personalisation: dynamic images where a prospect's LinkedIn photo or name appears in an email image, custom intro lines that pull from a variable column, and multi-step sequences that branch based on prospect behaviour. These features add meaningfully to reply rates — but only for emails that actually reach the inbox.
Running Lemlist's advanced personalisation through shared IP inboxes with 68% inbox placement means 32% of your personalised, carefully crafted emails are never seen. Running the same personalisation through pre-warmed inboxes on dedicated IPs at 94 to 96% placement means nearly all of them get read. The personalisation investment only pays off when the delivery infrastructure is solid.
This is where the Lemlist + Litemail combination is stronger than either alone: Lemlist's creative personalisation capabilities on top of dedicated IP inbox infrastructure that ensures those personalised emails arrive in the primary inbox. The platform does what it is best at; the infrastructure does what it is best at.
Monitoring Deliverability for Lemlist Campaigns With External Inboxes
When you connect external inboxes to Lemlist, the sending data lives in Lemlist's dashboard — but the deliverability signals live in Postmaster and SNDS. You need both data sources to get the full picture.
Data Source | What It Shows | Check Frequency |
|---|---|---|
Lemlist dashboard | Open rate, reply rate, bounce rate, step performance | Daily during active campaigns |
Google Postmaster | Domain reputation, spam rate for Gmail-destined sends | 3x per week; daily if volume over 500/day |
Microsoft SNDS | IP status for Outlook/M365 recipients | Weekly |
MXToolbox | IP and domain blacklist status | Weekly |
A bounce rate spike in Lemlist's dashboard is the first signal in the tool. But Postmaster typically shows the reputation change that caused it 2 to 3 days earlier. Monitoring Postmaster proactively means you catch the upstream signal before the downstream metric tells you something has gone wrong.
Lemlist Pricing Context — Where Inbox Costs Fit In
Lemlist's pricing for the Email Pro plan starts at $59 per user per month. The Multichannel Expert plan (which includes LinkedIn automation) is $99 per user per month. These are per-seat costs that do not include inbox fees — Lemlist's default inboxes are shared-IP infrastructure bundled with the plan.
Adding Litemail pre-warmed inboxes at $4.99 per inbox per month costs $29.94 for 6 inboxes on a team running 3 users. That is a 16% increase on the base Lemlist cost — for a 320% improvement in reply rate based on the Q4 2025 comparison above. The math on external dedicated IP inboxes is hard to argue against once you have seen the side-by-side data.
Total monthly cost for a 3-person team running Lemlist with Litemail infrastructure: $177 (3 × Email Pro) + $29.94 (6 Litemail inboxes) = $206.94. Revenue generated from a 3.1% reply rate on 2,700 monthly sends depends on your pipeline value — but at any reasonable conversion rate, the infrastructure investment is not the bottleneck.
The Bottom Line
Lemlist's default shared-IP inboxes deliver 65 to 75% inbox placement. Connecting pre-warmed dedicated IP inboxes via Lemlist's SMTP or OAuth raises this to 94 to 96% from day one.
A direct comparison of Lemlist default inboxes versus Litemail pre-warmed inboxes on the same sequence and ICP showed 0.9% versus 3.1% reply rate — the only variable was inbox infrastructure.
OAuth connection is the recommended method — cleaner than SMTP, better authenticated, lower maintenance. Google Workspace and Microsoft 365 both work with Lemlist OAuth.
Lemlist's personalisation features (dynamic images, custom variables) only pay off when the delivery infrastructure gets those personalised emails to the inbox. Pre-warmed dedicated IP inboxes are the infrastructure layer that makes personalisation investment worthwhile.
Monitor Postmaster 3x per week alongside Lemlist's dashboard metrics. Postmaster shows the upstream reputation signal 2 to 3 days before bounce or reply rate changes appear in Lemlist.
Adding 6 Litemail inboxes to a 3-person Lemlist team costs $29.94/month — approximately 16% of the base Lemlist cost. The reply rate improvement consistently exceeds the infrastructure cost within the first campaign week.
Frequently Asked Questions
Can I use external sending inboxes with Lemlist?
Yes. Lemlist supports connecting external inboxes via Google OAuth, Microsoft OAuth, and SMTP. OAuth is the recommended connection method — it provides better authentication and lower maintenance than SMTP. Once connected, external inboxes participate in Lemlist's inbox rotation and receive the same sequence management as Lemlist's default inboxes.
Does Lemlist have good email deliverability?
Lemlist's default inbox infrastructure uses shared IPs, which deliver 65 to 75% inbox placement on new campaigns. This is lower than dedicated IP infrastructure. Teams that require higher placement rates connect external pre-warmed inboxes on dedicated IPs via Lemlist's OAuth or SMTP connection. Lemlist's platform features (personalisation, sequences, tracking) are strong — the deliverability ceiling is limited by the default shared IP infrastructure.
How do I improve Lemlist inbox placement rates?
Connect pre-warmed external inboxes on dedicated IPs via Lemlist's OAuth or SMTP connection. Pre-warmed dedicated IP inboxes from Litemail deliver 94 to 96% inbox placement from day one versus 65 to 75% for Lemlist's default shared IP inboxes. The connection takes under 20 minutes per inbox and the placement improvement is immediate from the first campaign send.
How many inboxes should I connect to Lemlist for a 3-person team?
For a 3-person team sending 500 to 1,000 emails per day, connect 4 to 7 inboxes across 2 to 3 sending domains. Each inbox at 150 to 200/day maximum keeps sending volume within the range where inbox placement stays strong. This also provides rotation capacity — if one inbox shows deliverability signals, others in the rotation continue without pausing the full campaign.
What is the cost of adding pre-warmed inboxes to Lemlist?
Litemail pre-warmed inboxes cost $4.99 per inbox per month with dedicated US or EU IPs, SPF/DKIM/DMARC pre-configured, and Postmaster-verified reputation within 48 hours. For a 3-person team using 6 inboxes, that is $29.94 per month — approximately 16% of Lemlist's base Email Pro cost for 3 users. The reply rate improvement from dedicated IP infrastructure consistently pays back this cost within the first campaign week.
Should I use Google Workspace or Microsoft 365 inboxes with Lemlist?
Both are fully supported by Lemlist's OAuth connection. Choose based on your target audience: Google Workspace for tech, SaaS, and startup targets; Microsoft 365 for enterprise, financial services, healthcare, and government targets. Litemail provides pre-warmed inboxes on both platforms at $4.99/inbox/month — you can mix GWS and M365 inboxes in the same Lemlist rotation to optimise placement across different recipient domains.
