Skip to content
Workflow · Track and forecast · Opening soon

Zendesk weekly support report by group

Export your Zendesk tickets for the week, then group them by support team and calculate tickets created, tickets solved, backlog at week end, and median hours to solve. The report also flags groups whose backlog grew two weeks running, groups solving fewer tickets than they receive, and tickets reopened after being solved.

Early access opens shortly. Check back soon.

Someone typed

“build our weekly zendesk support report by group: tickets created and solved, backlog at the end of the week, and median hours to solve, and flag groups whose backlog grew two weeks running, groups solving fewer than they receive, and tickets reopened after being solved”

The agent read it as

Build our weekly Zendesk support report by group: tickets created and solved, backlog at the end of the week, median hours to solve, and flags for groups whose backlog grew two weeks running, groups solving fewer than they receive, and tickets reopened after being solved, from Zendesk tickets.

What the agent built

1 step, each one an ordinary Mammoth step you can open and change.

  1. File
    Zendesk tickets
    CSV export · 45 rows
  2. Step
    Build weekly group report
    Step 1
  3. Result
    Weekly Zendesk Support Report
    13 rows
  4. Schedule
    Runs when you say
    Proposed

On the sample files, every step runs and the result has 13 rows.

What you get back

The result of that run, the rows to look at first.

Weekly Zendesk Support ReportSample data13 rows
WeekGroupTickets createdTickets solvedBacklog at week endMedian hours to solveBacklog trendSolve balanceReopen statusReopened ticket IDs
2026-11-09Billing74572Backlog grew two weeks runningSolving fewer than receive··
2026-11-09Onboarding41448·Solving fewer than receive··
2026-11-09Sales32260·Solving fewer than receive··
2026-11-09Technical7114216Backlog grew two weeks runningSolving fewer than receive··
2026-11-02Billing54284·Solving fewer than receiveTickets reopenedZK-1020
2026-11-02Sales22148··Tickets reopenedZK-1022
2026-11-02Technical508··Solving fewer than receiveTickets reopenedZK-1012
2026-10-26Billing32136·Solving fewer than receive··
2026-10-26Onboarding202··Solving fewer than receiveTickets reopenedZK-1004
2026-10-26Sales21148·Solving fewer than receive··
2026-10-26Technical303··Solving fewer than receive··
2026-11-16Billing01424····
13 rows in the result · 12 shown, problems first. Sample data: illustrative figures, not business results.

How it works

How to use the Weekly Zendesk Support Report workflow

  1. 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and working on sample files.
  2. 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
  3. 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.

Weekly Zendesk Support Report: questions

How do you build a weekly Zendesk support report by group?
Export your Zendesk tickets for the week, then group them by support team and calculate tickets created, tickets solved, backlog at week end, and median hours to solve. The report also flags groups whose backlog grew two weeks running, groups solving fewer tickets than they receive, and tickets reopened after being solved.
What export should you use from Zendesk?
Use a tickets export from Zendesk that includes the fields needed for group, status, created time, solved time, and reopen history if you want the reopen flag.
What happens to tickets that do not match a group or rule?
They stay out of any grouped total unless your rules place them into a default group. Rows that do not match a flag rule are left unflagged.
How do you change the report rules?
Edit the grouping and flagging rules in words. You can change which fields define a group, which dates count for the week, and the conditions used for each flag.

Get early access to this workflow

It opens already built and working on sample files. Swap in your own exports to see your result.

Early access opens shortly. Check back soon.

Workflows like this

The number you report every month, rebuilt from the latest export, plus the forecast that follows from it.

All track and forecast workflows →