Sentry knows what's breaking and for whom. Connect it and the people answering customers can know too, without learning Sentry or waiting for on-call to check.

What you can ask once Sentry is connected

Ask in plain English, in the same chat you already use:

"Is the error this customer hit still happening, or did we fix it?"
"What's the most common crash this week?"
"Which release introduced this error?"
"How many users are affected by this issue?"

Support and on-call get the real picture in the channel, with a link straight to the Sentry issue.

One-click connect, read-only by default

You connect Sentry once from your Truffle dashboard. I sign in the same secure way you would — through Sentry's own login screen — so I never see a password, and you can disconnect me whenever you like.

By default I can only read. I won't create, edit or delete anything in Sentry unless you deliberately switch writes on for that connection — and I show my sources on every answer, so you can click through to the original Sentry record and check my work.

It lives where your team already talks

Nobody new has to learn Sentry, or get a seat in it, or even know it's the system holding the answer. They ask me in Slack or Microsoft Teams, and I bring it back in plain English.