We’re operationalizing AI inside the Sentry Support team in real time, with real customers and real stakes. This series captures what works, what breaks, and what we change as it happens, with a non-zero chance it becomes a cautionary tale instead of a success story.
Traditional Support waits for the customer to fail. We decided to intercept them before they do.
The Death of the Safety Net
In the world of SaaS, most Support organizations are built like world-class Goalkeepers. We pride ourselves on the “Great Save.” We celebrate the Support Engineer who dives into a 4:00 PM Friday fire, deflects a catastrophic bug, and earns a “Thank You” note from a frantic CTO.
It’s heroic. It’s emotional. And it’s a fundamental strategic failure.
If your goalie is the busiest person on the pitch, you aren’t winning; you’re surviving. You are playing a defensive game, pinned in your own box, waiting for the customer to make a mistake, break the product, or lose their patience. By the time a customer “submits a ticket,” the friction has already occurred. The goal has been scored against you. You’re just cleaning up the net.
From Goalie to Midfielder
We’ve spent the last year burning the “Goalkeeper” playbook. We are moving our defensive line up thirty yards. We are moving into the Midfield.
In soccer, the midfielder is the playmaker. They don’t wait for the ball to reach the goal line; they intercept the pass. They read the game, disrupt the opponent’s flow, and transition immediately from defense to attack.
When we talk about “Moving Support to the Midfield,” we are talking about Proactive Interception.
The traditional triage reality—where a user hits a snag, hunts for a “Contact Us” link, fills out a five-field form (argh), and waits for an asynchronous “we’ve received your request” email—is an obsolete model. In fact, it’s worse than obsolete; it’s a deterrent. It actively punishes the user for needing help.
The 90% Silent Churn
CROs often look at CSAT and think, “Our customers love us!” because the people who write in are happy with the fix. This is a survivor bias trap.
The real danger isn’t the 10% of users who open a ticket. The danger is the 90% of technical traffic that starts and ends in the product. These are the prospects who hit a friction point, can’t find an immediate answer, and—rather than waiting 4 to 24 hours for a human response—simply close the tab.
They don’t complain. They just leave. They are the “Lost” customers, and your Goalie never even saw the ball.
The Fix: Interception
Our strategy document was clear: if the traffic starts in the product, the solution must live in the UI.
By embedding an AI agent directly into the user’s workflow—not buried in a Help Center three clicks away—we changed the physics of the interaction. We stopped asking the customer to come to us. We went to them.
When a developer is staring at a 401 Unauthorized error in the console, they don’t want a “relationship” with a support agent. They want a solution, and they want it at the speed of thought. By putting AI in the “Midfield”—intercepting that error message before it turns into a “Contact Support” thought—we capture that 90% of silent traffic.
We aren’t just “deflecting tickets.” We are protecting the user’s momentum.
The Impact on the P&L
For a B2D2B SaaS company, the Midfield model is the only way to decouple headcount from revenue. If you stay in the Goalkeeper model, your costs scale linearly with your problems. More customers = more tickets = more goalies.
By moving to the Midfield, you are investing in a system that scales through intelligence, not empathy. You save your humans for the “Championship” moments—the high-value architectural consultations—and let the AI play the Midfield, intercepting the thousands of daily “passes” that used to end up as goals against your team’s productivity.
It’s time to stop celebrating the “Great Save” and start celebrating the “Interception.”