Support Team Dashboard

This page shows how we did, what we're changing, and each person's goals for this week. The snapshot below is this week (June 27 – July 3) — an outage-heavy week: a site outage plus a big GGU access/400-error wave. The charts further down are the baseline month (May 10 – June 9). Check items off as you finish them — your checkmarks save on your computer.

📊 This week at a glance (June 27 – July 3)

34
waiting on us right now
(was 6 · goal 0)
20
tickets with no owner
(was 1 · goal 0)
~28
closed without a reply
(was 0 · goal 0)
71%
tickets tagged
(was ~10% · goal: all)
80
tickets closed this week
(Sakina 55 · Anam 15 · Sidra 10)

Outage week: the team closed 80 tickets and Sakina cleared the whole overnight outage batch 👏. The red numbers are mostly the fresh evening wave (still unassigned) and outage tickets closed by backend fix without a note — both fixable with the three habits below. Same-day and 4-hour reply rates are measured again next week.

📊 Baseline — how we did last month

134
tickets handled
(93 student · 41 instructor)
15 hrs
typical wait for a first reply
(goal: same day)
58%
of students got a reply
within 1 day
15
tickets closed without
any reply at all
1 in 4
tickets were customers writing in
again about the same thing

How long customers waited for a first reply

Most late replies are tickets that arrived after the morning batch or on weekends. Green = within target.

What student tickets were about

Logging in and getting access to courses is a third of everything — good answers here are worth turning into saved replies.

The biggest problem: silence

15 real questions were closed without a reply. Most of the "writing in again" volume traces back to these — answering the first message prevents the second one.

The standard we're working toward: at any point in the day, no ticket sits with the customer's message unanswered. A ticket that's open but waiting on the customer is fine. A ticket that's waiting on us is the only thing that counts against us. The aim is simple: end every shift with nobody waiting on us.

🔁 Three habits, starting now

1Reply before you close

Every ticket gets an answer — or a one-line note saying why it doesn't need one. Closing a ticket without replying is how we ended up with customers writing in twice.

2Assign yourself

When you pick up a ticket, assign it to yourself. It's how we know what's being worked on — and how your work gets counted.

3Tag every ticket

One tag per ticket so we can see patterns.billingaccessdiscussionsgradingcontentlms-integrationfeature-requestmisdirected

✅ This week's goals (by Friday)

Anam

US hours · first touch on US-hours student tickets + service work from Sidra

Sidra

US hours · runs Services (instructor requests) and decides what goes to Anam

Sakina

Pakistan hours · runs Support (student tickets) · back from vacation and carrying the student inbox 👏

📈 What we track every week

Every Friday we review these together. Same numbers, every week — so progress is visible and nothing slips quietly.

What we measure Where we started This week (Jul 3) The goal
Tickets waiting on us (unanswered messages)~9340
Tickets with no owner4200
Closed without a reply15 last month~28*0
Students answered same day58%measured next week100%
Instructors answered within 4 working hoursrarelymeasured next weekevery time
Oldest open request4+ months~5.3 months (#410)younger every week
Tickets taggednone71%all

⏱️ How fast we reply, from now on

Students — same day, always within 1 day

Sakina covers Pakistan hours, Anam covers US hours. Between you, almost every weekday hour is covered — that's how we get to same-day for everyone.

Instructors — within 4 working hours

Instructors run live classes; a fast "we're on it, answer by Thursday" beats a slow perfect answer. This also applies to instructor emails that land in the student inbox.