The Deliverability Hub is a dedicated area in lemlist that brings your deliverability insights into one place, across lemwarm (Warm-up) and lemlist (Outreach). Instead of switching tools or guessing why performance drops, you can monitor key signals (delivered vs. bounced, bounce trends, inbox/spam signals, and sending behavior) and set up alerts to catch problems early.
Learning objective
By the end of this tutorial, you’ll know how to navigate the Deliverability Hub, analyze deliverability for both Outreach and Warm-up, and configure alerts so your team can detect and fix deliverability issues before they impact pipeline.
Why this matters
Deliverability issues rarely happen all at once—they build up gradually. Without a single source of truth, teams often notice problems too late, after reply rates drop. Deliverability Hub helps you spot red flags earlier, understand what’s changing (bounces, spam signals, sending behavior), and scale outbound safely across multiple mailboxes/domains.
Prerequisites
You have at least one mailbox connected in lemlist (for Outreach metrics).
If you want to use the Warm-up tab, your mailboxes should be connected to lemwarm and actively warming up.
Availability: Deliverability Hub is included in all plans and is available in the free trial.
Core lesson — Step-by-step workflow
Phase 1: Open Deliverability Hub and choose what you want to monitor
Go to Deliverability Hub.
In the left navigation, click Deliverability hub. Then select the area you want to explore:lemlist | Outreach to review delivered vs. bounced performance for your campaigns
lemwarm | Warm-up to review warm-up reputation and inbox/spam signals
Alerts to configure proactive monitoring
Phase 2: Filter your view to pinpoint the cause (time range, granularity, mailbox, provider, domain)
Set filters before you interpret any metrics.
Use the top filter bar to focus on the right slice of data:Date range (e.g., last 7/14/30 days)
Granularity (Daily/Weekly/Monthly/Yearly)
Mailboxes (single mailbox or multiple)
Providers and domains (to isolate provider-specific or domain-specific issues)
This is the fastest way to confirm whether a deliverability drop is localized (one sender/provider) or systemic (domain-wide).
Phase 3: Analyze Outreach deliverability (Delivered vs. bounced, trends, and breakdowns)
Start with the headline Outreach KPIs.
In lemlist | Outreach, use the KPI cards to quickly assess performance in the selected time range:Total email sent
Delivered and delivery rate
Not delivered (Bounced) and bounce rate
Avg daily sent (useful for spotting sending spikes or slowdowns)
Check delivery vs. bounce trends over time.
Use the charts to see whether deliverability issues are getting worse, improving, or spiking on specific days (often a clue for list quality changes, provider throttling, or sending volume changes).
Identify which providers are driving the problem.
The Performance by Email Provider table helps you compare performance by sender/recipient provider (e.g., Google → Google vs. Microsoft → Google). If one provider pair shows a much higher bounce rate, prioritize investigation there.
Drill down by mailbox to find the sender at risk.
The Outreach Performance by Mailbox table makes it easy to see which mailbox has abnormal bounce rates or reduced delivery rate—ideal for Sales Ops and managers overseeing multiple senders.
Review performance by recipient domain.
Use Outreach Performance by Recipient Domain to spot domains that systematically bounce. This can reveal segmentation issues (e.g., a specific target domain set), data quality problems, or domain-specific blocking.
Best practice: When bounce rate rises, first narrow down by mailbox and provider. Fixing one sender’s setup or behavior is often faster (and safer) than changing the entire campaign strategy.
Phase 4: Analyze Warm-up deliverability (lemwarm insights inside lemlist)
Switch to Warm-up to assess reputation signals.
Open lemwarm | Warm-up to monitor warm-up performance without leaving lemlist.
Review real-time warm-up health signals.
The top KPI cards give you a quick snapshot of warm-up performance (based on selected filters), including:Deliverability Score
Inbox Rate
Inbox Count
Spam Count
Compare deliverability score trends by mailbox and by domain.
Use these charts to spot whether a deliverability issue is isolated to a single mailbox (sender reputation) or affecting an entire domain (domain reputation/authentication/sending behavior).
Use the mailbox warm-up summary to manage at scale.
The Mailbox Warm-up Summary table provides an operational view per mailbox (average score, inbox/spam counts, daily limit, ramp-up). This is especially useful for Sales Ops teams managing multiple senders.
Phase 5: Set up Alerts to catch deliverability issues early
Open the Alerts tab and start creating an alert.
Go to Alerts, then click Create an alert in the section you want to monitor (Warm-up or Outreach).
Configure the alert type, target, and severity.
In the Email deliverability alerts modal:Select an Alert type (the KPI you want to monitor).
Select the Monitoring target (global, or a specific mailbox/domain depending on the alert type).
Select a Severity level (e.g., Warning or Critical).
Define when the alert should trigger.
Set the threshold logic:Operator (above/below/equal)
Threshold (%)
Period (days) and whether it’s a rolling average or consecutive days
This prevents overreacting to one-day anomalies and helps you track real trends.
Choose how you want to be notified (Email and/or in-app).
Enable Email notifications to alert additional stakeholders (e.g., Sales Ops, managers, agencies), and keep In-app enabled for quick visibility in lemlist.
Verify your alerts are active.
Once saved, your alert appears in the corresponding list (Warm-up alerts or Outreach alerts), showing the metric, target, and threshold rules.
Phase 6: Monitor alert logs (what triggered, when, and where)
Review Alert logs to track incidents over time.
Use Alerts logs to see when alerts were triggered and whether they’re active or resolved. This is helpful for reporting, audits, and understanding whether your fixes worked.
Practical application: a simple weekly deliverability routine (SDR/AE + Sales Ops)
Monday (Outreach): Filter to last 7 days → check Bounced KPI and the Delivery & Bounce Rate Over Time chart. If bounce rate spikes, drill down by provider and mailbox.
Mid-week (Warm-up): Check Inbox Rate and Spam Count → if spam increases, review score trends by mailbox vs. domain to decide whether you need a mailbox-level fix or domain-level investigation.
Always-on: Keep alerts enabled for your key KPIs (e.g., spam rate in Warm-up, bounce rate in Outreach) so you don’t have to manually watch dashboards every day.
Troubleshooting & common pitfalls
Issue: “I’m seeing a warning that no mailboxes are warming up.”
Root cause: No mailbox is connected to lemwarm, or warm-up isn’t started.
Fix: Connect mailboxes to lemwarm and ensure warm-up is running. Then return to lemwarm | Warm-up and refresh your filters.
Issue: “My charts/tables look empty or inconsistent.”
Root cause: Filters are too narrow (date range too short, wrong mailbox/provider selected) or there wasn’t sending activity in that period.
Fix: Expand the date range and select All mailboxes / All providers to validate whether it’s a data issue or a filter issue.
Issue: “Alerts aren’t triggering when I expect them to.”
Root cause: The alert is configured with a rolling window/consecutive-days rule that hasn’t been met yet, or the threshold is set too high/low.
Fix: Recheck Operator, Threshold (%), and Period (days). Consider starting with a Warning severity at a realistic threshold, then tighten it after you observe real traffic patterns.