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.
In most companies, the Support team buys software in a silo. They find a tool that makes ticket routing 5% faster, they buy it, and the Product team ignores it.
But Sentry is not “most companies.” And we aren’t selling socks. We are selling observability to developers.
If our product interface is a sleek, dark-mode, high-performance Ferrari, but our Support interface looks and acts like a 1998 Honda Civic with a leaky radiator, we have broken the spell.
We didn’t just ask IT to approve the vendor. We asked the people who built Sentry.
The Guardians of DX
Our Product Managers and Engineers are obsessively protective of the Developer Experience (DX). They determine how the product feels, how the APIs respond, and how the docs are structured.
Usually, they view Support tools as “Enterprise Bloatware” - necessary evils that they hope they never have to log into.
We dragged them into the room and said: “This AI is going to talk to your users. It is going to represent your code. If it sucks, it’s on you too.”
The Litmus Test: “Does it Speak Code?”
The feedback from the Product team wasn’t about ROI or deflection rates. It was about respect for the craft.
When we showed them the shortlist of vendors, they didn’t look at the analytics dashboard. They looked at the chat window.
The Engineer’s Potential Objection: “Look at this,” a Senior Frontend Engineer may say during a demo. “The AI pasted a Python snippet, but it stripped the indentation and it isn’t using syntax highlighting. It’s unreadable.”
To a normal buyer, that’s a nitpick. To a developer tool company, that is a dealbreaker.
The PM’s Potential Ultimatum: “This bot is too polite,” a Product Lead may say. “It sounds like a bank teller. Sentry isn’t a bank. We are direct. If the user messed up the config, tell them they messed up the config. Don’t apologize for their syntax error.”
Extending the Surface Area
The Product team is helping us realize something critical: DX doesn’t stop at the sentry.io domain.
We meet customers in the IDE. We meet them in the CLI. We meet them on GitHub. And now, we meet them in this chat window.
If the AI acts like a generic “Support Agent” it creates a jarring disconnect. If the AI acts like an “Engineer”: smart, context-aware, and technical - it feels like an extension of the product.
The “No Garbage” Rule
The Product team prioritize a vendor that:
Understood Technical Context.
Allowed “Agent Voice” Customization.
The Alignment
Support and Product were looking at the same tool with the same goal. Support wanted leverage (help customers help themselves), Product wanted consistency (support the brand).
We are THIS close to finding a tool that did both. It respects the code. It respects the user. And most importantly, it respects dark mode (hey). My Terminal theme may raise questions, but it also builds character.
We got the team’s blessing.