Use casesReporting

Report last week's support numbers before the week starts

Mitra builds an agent that reads last week's Zendesk tickets every Monday morning and reports the volume, the first-response time and the top five reasons people wrote in. Each number arrives with its direction against the week before. The row goes to Google Sheets and the summary to Slack.

Runs: Every Monday at 9am
Used by: Customer Support · Ops / Chief of Staff

The prompt

Every Monday at 9am, count last week's Zendesk tickets, work out the average first-response time, and find the five most common reasons people wrote in. Append the numbers to my Support Metrics sheet in Google Sheets, then post a summary to #support showing how each one moved against the previous week.

Zendesk

Google Sheets

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Counts last week's tickets
The agent reads every Zendesk ticket opened between Monday and Sunday, including the ones closed the same day.
Works out first-response time
For each ticket the agent measures the gap between the customer's first message and your team's first reply, then averages the week.
Finds the top five reasons
The agent reads what people actually wrote rather than the tags somebody applied, and ranks the five subjects that came up most.
Appends the row to Sheets
One row per week goes into your existing sheet, so the trend builds up on its own and your formulas and charts keep working.
Posts the summary with direction
The Slack post carries every number beside last week's, so the channel reads volume up eleven percent rather than a bare total.

Make it yours.

Support leads who assemble the same Monday numbers by hand, and the ops person who needs them without asking twice. If your queue's direction of travel is only visible when somebody exports a spreadsheet, this is the gap the agent closes. Change any of this by saying so — there is nothing to rewire.

Report on Friday afternoon instead, so the week closes with its own numbers.
Break the volume down by product area or by assignee, and keep the same five-reason ranking.
Drop the Slack post and let the sheet be the record, for teams who read the numbers in a dashboard.

Questions, answered.

How do I automate a weekly support volume report?

Describe the report in one sentence and Mitra builds the agent that produces it every Monday. The agent counts last week's Zendesk tickets, measures first-response time, ranks the reasons people wrote in, then writes a row to Google Sheets and a summary to Slack.

What if my team doesn't tag tickets consistently?

Mitra reads the text of each ticket rather than its tags, so an untagged queue still produces the top five reasons people wrote in. The agent groups the week by what customers actually wanted and reports the counts. Tell Mitra which categories your team uses and the next run uses those names.