Engagor
Resources Case Study

A Monday Night Save

Detecting a Microsoft deliverability crisis in real-time, while everyone was offline.

ENGAGOR Just Russel

Company
Just Russel
Industry
D2C Pet Food
Location
Belgium
Date
January 2026

Key Metrics

9:56 PM

Autonomous detection

Daily volume affected
37%
Worse than other ISPs
26×

"Die tool is top!"

("That tool is amazing!")

Louis Vanderhaeghen CGO, Just Russel

A Monday Night Save: Detecting a Microsoft Deliverability Crisis in Real-Time

How Engagor's autonomous AI discovered a critical email problem while everyone was offline, and provided the answers the ESP couldn't.

  1. The Company

    Just Russel delivers personalized dog and cat food to pet owners across Belgium. As a fast-growing D2C brand, email drives their business: order confirmations, delivery updates, promotions, and win-back campaigns.

    With tens of thousands of emails going out daily, deliverability isn't optional. It's revenue.

  2. The Challenge

    Monday evening. January 19, 2026. The office is empty.

    Somewhere in the email infrastructure, something breaks. Emails to Microsoft recipients (Outlook, Hotmail, Live) start bouncing. Hard.

    In a traditional setup, this goes unnoticed until someone checks the dashboards the next day. Maybe later in the week, when the weekly report comes in. By then, thousands of customers have missed their emails. Revenue is lost. Reputation damage compounds.

    But Just Russel had Engagor watching.

  3. The Discovery

    9:56 PM, Engagor's Autonomous AI detects a critical anomaly:

    Microsoft/Outlook Bounce Crisis, Severity: Critical

    The numbers told a clear story:

    • 10.21% bounce rate to Microsoft (vs. 0.07% to Gmail)
    • 37% of total volume affected, more than 1 in 3 emails
    • 26× worse performance compared to other mailbox providers

    This wasn't a gradual decline. This was a cliff.

  4. The Diagnosis

    Traditional monitoring would show "bounce rate up" and leave you guessing. Engagor went deeper, automatically analyzing SMTP response codes to find the root cause:

    The Verdict

    The shared sending IP was on Microsoft's blocklist.

    This wasn't a content problem. It wasn't an engagement problem. It was infrastructure, and completely outside Just Russel's control.

  5. Meanwhile, the ESP's dashboard offered its own advice:

    ESP Dashboard Recommendation

    "Target more engaged subscribers."

    This is the standard playbook. When deliverability drops, most platforms default to engagement-based recommendations: send less, send to openers only, warm up your list.

    But engagement wasn't the problem.

    The IP was blocklisted. No amount of "targeting engaged subscribers" would fix that. A customer following this advice would be optimizing for the wrong problem entirely, while the real issue continued to damage their sender reputation.

    This is the difference between generic, templated recommendations and actual root cause analysis.

  6. Instant Answers When It Mattered

    When Chief Growth Officer Louis Vanderhaeghen saw the discovery, his first question was immediate: "How much of our traffic is actually going to Microsoft?"

    Instead of digging through dashboards, filtering reports, or waiting for someone to pull the data, he simply asked Engagor's AI Studio in plain language:

    "What is the percentage of distribution for Hotmail/Outlook versus total volume?"

    • Total Microsoft volume: 13,396 emails (37% of daily sends)
    • Breakdown by property: Outlook, Hotmail, Microsoft365
    • Context: "More than 1 in 3 emails go to Microsoft infrastructure"

    No SQL queries. No exports. No waiting. Just a question and an answer.

    "Die tool is top!"

    ("That tool is amazing!")

    — Louis Vanderhaeghen, Chief Growth Officer
  7. The ESP Response

    A support ticket was escalated with the exact technical details Engagor had identified.

    The next morning, the ESP replied:

    "This is a temporary deferral... it's industry-wide."

    Incorrect

    The error code indicated a hard block, not a temporary deferral. And no other senders on different IPs were experiencing the same issue.

    Armed with Engagor's specific diagnosis (the exact IP, exact error code, exact timestamp), Just Russel was able to push back with evidence and escalate appropriately.

  8. The Outcome

    With the real problem identified in minutes rather than days, Just Russel could:

    • Escalate with concrete technical evidence
    • Challenge generic "industry-wide" explanations
    • Begin planning a move to dedicated IP infrastructure
    • Minimize the window of reputation damage
  9. Why It Matters

    Traditional Monitoring Engagor
    Dashboard shows "bounces up" Autonomous discovery at 9:56 PM
    Generic advice: "Target engaged subscribers" Exact root cause: IP blocklist identified
    Manual queries to understand impact Natural language: instant answers
    Wait for next-day review Real-time detection, no humans needed
    Reactive Proactive

About Engagor

If you run lifecycle, CRM, or deliverability, and email revenue matters, this was built for you.

Engagor is an Agentic Email Intelligence Platform (AEIP). Unlike dashboards that wait for you to look, Engagor's AI monitors your email ecosystem 24/7, detects anomalies autonomously, performs root cause analysis, and delivers actionable recommendations, before you even know there's a problem.

See how Engagor can protect your email program →

Built by deliverability practitioners. For brands who can't afford to miss what matters.