Dashboard template

Tickets in, tickets out, and how long people waited.

A support desk page for the team lead and the wall screen: what came in today, what is still open and how old, who is handling what, and whether customers were happy when it was over.

First reply: 14 min

Support performance

Tickets, response times and happy endings.

Help desk tools report on tickets; they are worse at the questions a manager actually has — is the backlog growing, which category is driving it, and are we inside the response times we promised. This template answers those from Zendesk or any help desk, and joins the tickets to your customer list so priority accounts are visible.

The support lead uses the top row through the day and the agent table in one-to-ones. Product and operations use the category breakdown to see which defect or process is generating tickets, which is where most of the real savings are.

Agents see their own row and the team totals, not each other’s figures — a row-level rule handles that without a second dashboard. For a broader set of team metrics see the KPIs every business should track.

  • Support team leads who want the backlog and response times on a screen the team can see.
  • Operations and product managers who need ticket categories to prioritise fixes.
  • Managed service providers who owe customers an SLA report every month.
The metrics

What a support performance dashboard should show.

Each figure below is on the template from the first minute — rename, redefine or remove any of them.

Tickets opened

New tickets today and this week, by channel (email, chat, phone, form) and by category.

Tickets resolved

Closed in the same periods. When opened runs ahead of resolved for three days, the backlog chart below explains why.

First response time

Median minutes from ticket created to first agent reply, during business hours. Median, not average — one abandoned ticket should not move it.

Resolution time

Median hours from created to solved, by priority and category.

SLA compliance

Tickets answered inside the promised time ÷ all tickets, by priority. The figure that goes in the customer-facing report.

Backlog

Open tickets right now, and how many are older than 24 hours, 3 days and 7 days.

Customer satisfaction

Good ratings ÷ all ratings on solved tickets, with response count, rolling 30 days.

Reopen rate

Solved tickets reopened by the customer ÷ solved. A cheap way to catch answers that closed the ticket but not the problem.

The panels

The charts on the page, and the decision each one supports.

Opened vs resolved by day

Two bars per day for 30 days with the backlog as a line. Decides whether to bring in cover before the weekend, not after.

Backlog by age

Open tickets in age bands, by priority. The oldest high-priority tickets are listed with owner — the ones to escalate now.

Agent league table

Tickets solved, first response, resolution time and satisfaction per agent. Each agent sees their own row; the lead sees everyone.

Tickets by category

Volume and resolution time by category and sub-category, month over month. Points product and operations at the root cause with the biggest payoff.

Response time by hour of day

A heatmap of first-response time by hour and weekday. Shows exactly where staffing is thin.

Satisfaction trend

Weekly satisfaction score with the latest negative comments alongside. Turns a percentage into something the team can act on.

Where the numbers come from

Connect the systems you already run.

The template expects data like this. Connect it live or import it, relate the tables once, and every panel fills in.

See all 50+ connectors
ZeZendeskHuHubSpotSaSalesforcePoPostgreSQLGoGoogle SheetsREREST APIsNoNotion
FAQ

Support performance template questions.

Something else on your mind? Ask us directly — a person answers.

What should a support dashboard include?

Tickets opened and resolved, backlog by age, first response and resolution time as medians, SLA compliance by priority, satisfaction score and a per-agent table. Add ticket categories so the rest of the company can see what is causing the volume.

Can each agent see only their own performance?

Yes. A row-level rule on the assignee column shows each agent their own tickets and figures while the team lead sees everyone. It applies to downloads and scheduled reports too.

How often does the support dashboard update?

Help desk data refreshes on the schedule you choose; many teams refresh every 15 minutes for the wall screen. Response-time medians recalculate each refresh.

Can we start from this template and change it?

Yes. Add your own SLA tiers, split by product or region, or add a customer-facing version with only the SLA figures. It is a normal dashboard once you start.

Your support performance dashboard, this week.

Bring your data and we'll set this template up on it live — then shape it around the questions you actually ask.

Talk to sales

Prefer to see plans first? See pricing

Contact usWhatsApp