Use casesTriage
Bug reports out of the support queue and into the backlog
Mitra turns support tickets into bug reports. Every morning at 9am the agent reads the new Zendesk tickets and opens a Linear issue for the genuine bugs. The reproduction steps come from the ticket, and the issue link goes back to the reporting channel.
Every morning at 9am, read yesterday's Zendesk tickets and open a Linear issue for the ones describing a bug. Post each issue link back to Slack.
200 credits to start · no credit card
What the agent actually does.
Read yesterday's tickets
The agent reads every Zendesk ticket opened since the last run, including the customer's own description.
Separate bugs from questions
Tickets describing something broken are kept, and how-to questions, billing queries and feature requests stay in support.
Write the reproduction steps
Each issue carries the steps the customer described, what they expected, and the version or browser if the ticket names one.
Link the ticket and the issue
The two point at each other, so support can follow progress without asking anyone.
Tell the reporting channel
A Slack message names the issue and which team it landed with.
Make it yours.
For support and engineering teams who relay bugs by hand, and lose the customer's real steps on the way. Change any of this by saying so — there is nothing to rewire.
- Draft a reply confirming the bug was filed, and hold it for approval.
- File issues only for paying customers, and collect the rest weekly.
- Add a repeat report to the existing issue instead of opening a new one.
Questions, answered.
How do I turn support tickets into bug reports without retyping them?
Which support tickets should become bug reports?
Other things people stop doing.
Ready to
reclaim your day?
Build my first agent200 free credits · no credit card · nothing to install