Skip to content

Weekly support performance

A free weekly customer support report template. AI summarizes ticket volume, response times, resolution rates, and top issues every Monday.

Runs weekly Scheduled Delivered to Slack, Email
Weekly support performance
Active

Trigger

Runs weekly

Instructions

Generate a weekly support performance report covering the past 7 days.

Delivery

Slack · Email

Example output

A realistic sample of what this automation delivers — your version draws on your data.

Weekly support performance Runs weekly · Sent to Slack, Email
Sample output
Median response time, last 8 weeks minutes
W1 W2 W3 W4 W5 W6 W7 W8 0 123 245
First reply Resolution

Top line. 168 tickets opened (vs. 142 trailing-4-week avg), 159 closed. First-reply median: 18 minutes (target <30). CSAT 4.7/5.

Themes

  1. Source connection (28 tickets, +14 WoW). Almost all on the new warehouse picker — same root cause flagged in the customer feedback trends report.
  2. Billing (12 tickets). Mostly seat-management questions; possible doc fix.
  3. Performance (8 tickets, -4 WoW). Dropping after the Friday hotfix.

Tickets needing leadership awareness

  • #4912 — NorthwindCo ($72K ARR), 3 escalations in 7 days, P2 open 72h. CSM looped in this morning.
  • #4880 — Acme, “exec demo Monday”. Sam to handle directly.

SLA breaches: 0 P1, 1 P2 (resolved within +2h of target).

Generated by Basedash AI from your connected data sources Support
The prompt

Copy, paste, customize.

Drop this into a Basedash automation. AI fills in the numbers from every source you've connected.

Instructions
Generate a weekly support performance report covering the past 7 days.

Cover:

**Volume.** Total tickets created, resolved, and currently open. Compare to last week and the trailing 4-week average.

**Response time.** Median time to first reply and median time to resolution.

**Quality.** Customer satisfaction (CSAT) average, percent of tickets reopened, percent escalated.

**Themes.** Top five issue categories driving ticket volume this week.

**Notable.** Two or three specific tickets that warrant leadership attention — VIP escalations, novel bug patterns, or repeat reports.

**Outliers.** Tickets open longer than 72 hours.

Lead with numbers. End with a one-line summary of where to focus next week.
Data sources

Powered by these sources.

Basedash automations read across every connected source in a single run. These are the ones this template tends to use most.

Frequently asked questions

What support metrics should I track weekly?
What's a healthy first-reply time?

Get started in under 30 minutes

We can help you migrate your data and dashboards from any other tool.