Who is Agent Training Mode designed for?

New or struggling email support agents who already have basic product knowledge and are ready to handle real customer enquiries, under review.

Does the customer know their reply was reviewed?

No. During the email support training period, the customer only sees the final, approved message, sent under the trainee's name.

Does Agent Training Mode slow down response times?

It adds one review step, so response time depends on how quickly the supervisor checks the queue. Teams typically offset this by capping how many trainees report to one supervisor, or by treating training-mode replies as a priority queue for the supervisor.

How many trainees should each supervisor manage?

Many teams cap it at three to five trainees per supervisor during onboarding, so the approval queue keeps moving and doesn't become a bottleneck.

When should agents leave Training Mode?

Once an agent's replies are consistently approved with little or no editing, most teams move them off Training Mode gradually, reducing review frequency before removing it entirely, rather than switching it off in one step.

Can a supervisor approve a reply without editing it?

Yes. If the draft is ready to go, the supervisor approves it as-is and it's sent unchanged.

Is Agent Training Mode only for email?

Yes, it's built specifically for email replies. Other channels have their own monitoring and coaching tools inside FocalScope, since live channels like phone and chat need a different kind of oversight than a written draft that can be held and edited before it's sent.

Can a trainee see what the supervisor changed?

Yes. Trainees receive a copy of both versions, so they can see exactly what was edited and why.

5 Monthly Support Reporting Templates for Team Leads

Home 9
What's new at FocalScope 9
Customer service reports

5 Customer Support Reports Every Team Lead Should Run Monthly

Five monthly reports that show where demand comes from, how fast you respond, and what to fix next.

The five support reports team leads should run every month are: ticket volume and channel trends, response and resolution time, SLA performance, backlog and ticket ageing, and agent workload. Together they show where demand is coming from, how fast you respond, whether you keep your promises, what is piling up, and whether work is shared fairly.

Daily dashboards help you manage the queue in front of you. Monthly support reporting shows the patterns behind it, so you can make better decisions on staffing, workflows, training and service levels instead of reacting to each spike.

Key Takeaways

Run all five reports monthly, then compare each against the previous month and the same month last year.
Always report median alongside average response and resolution times. Outliers distort averages.
Segment every report by channel, priority, and category. Blended numbers hide the real problem.
End each review with two or three owned actions, not a list of observations.

Monthly Support Reporting at a Glance

Report	Key Metrics	Question It Answers	Action It Drives
1. Ticket volume and channel trends	Total volume, channel mix, peak times, top categories	Where and when is demand coming from?	Shift coverage, forecasting, root-cause fixes
2. Response and resolution time	FRT, resolution time (average and median)	How fast do customers get answers and fixes?	Process bottleneck removal
3. SLA performance	SLA compliance %, breach count, breach segmentation	Are we keeping our service promises?	Escalation and handoff fixes
4. Backlog and ticket ageing	Open tickets, age bands, at-risk tickets	What is waiting, and for how long?	Ticket sweeps, capacity planning
5. Agent workload and performance	Tickets handled, handle time, CSAT, escalation rate	Is work distributed fairly and sustainably?	Routing rules, coaching, workload balance

1. What Is a Ticket Volume and Channel Trends Report?

A ticket volume report tracks how many support requests arrive each month, broken down by channel (email, voice, live chat, WhatsApp, social media), enquiry category, and time of day or day of week.

Why it matters: Volume is the clearest signal of customer demand. A spike in email after a product release points to a product issue. Rising live chat or WhatsApp volume shows customers moving towards instant channels.

Metrics to track:

Total enquiries: inbound vs. resolved
Channel distribution: share of volume per channel, month over month
Temporal patterns: volume by hour and by weekday
Top enquiry categories: the most frequent tags and root causes

How to act on it: Look for channel shifts and recurring spikes. Use them to adjust shift rosters, refine automated triage, and send your most common issues to product and documentation teams.

FocalScope tip: Use folder mapping and ticket tagging to view volume by enquiry category across every channel in a single report. AI categorisation on incoming email and calls keeps those categories consistent, so the report reflects what customers actually asked about.

2. What Is a Response and Resolution Time Report?

A response and resolution time report measures two things: First Response Time (FRT), how long a customer waits for a first human reply, and Resolution Time, how long from ticket creation until the issue is solved.

Why it matters: Comparing the two exposes where time is lost. A team can reply within minutes yet take days to resolve because of slow back-end processes or long escalation loops.

Metrics to track:

Average and median FRT
Average and median resolution time
Both metrics broken down by channel, priority and category

How to act on it: Watch for rising times when volume is stable, which signals a process problem rather than a capacity one. Always compare median against average. A large gap means a few long-running tickets are distorting the picture.

Note: Faster is not always better. Cutting handle time must never come at the cost of accurate resolution.

FocalScope tip: Run the response and resolution report by channel, priority and category from the built-in Excel templates, and compare median against average in the same sheet.

3. What Is an SLA Performance Report?

An SLA performance report shows how consistently your team meets agreed response and resolution deadlines.

Formulas:

Response SLA compliance = (tickets answered within the response target ÷ tickets subject to a response SLA) × 100
Resolution SLA compliance = (tickets resolved within the resolution target ÷ tickets subject to a resolution SLA) × 100

Why it matters: SLAs set customer expectations. Tracking compliance month to month reveals systemic delays before they damage trust or lead to churn.

Metrics to track:

Overall compliance rate: reported separately for response and resolution
Breach volume: tickets that missed a response or resolution target
Breach segmentation: by priority, category and channel

How to act on it: Work out whether breaches come from internal handoffs or uneven queues. If technical escalations keep breaching, the problem sits in the tier-2 handoff, not in front-line agent speed.

FocalScope tip: Use colour-coded SLA status flags and automated escalation rules to alert team leads before a deadline is missed. Team leads can also watch at-risk tickets from the FocalScope mobile app, so a looming breach does not wait for the monthly report.

4. What Is a Backlog and Ticket Ageing Report?

A backlog report lists open, unresolved tickets and shows how long each has been waiting. Why it matters: Strong resolution numbers can hide a growing pile of old tickets. Without an age breakdown, complex issues sit untouched while agents clear the easy, newer ones.

Metrics to track:

Total open tickets: awaiting agent action or customer reply
Ticket age distribution: for example under 24 hours, 1–7 days, 8–14 days, over 14 days
At-risk tickets: those approaching an SLA breach

How to act on it: Separate tickets waiting on your team from those waiting on customers or third parties. Then use the age bands to run regular ticket sweeps that close out neglected requests.

FocalScope tip: Filter open tickets by age and SLA status, and use a My Watch folder to keep at-risk tickets in view between monthly reviews.

5. What Is an Agent Workload and Performance Report?

An agent workload report shows how work is spread across your team and how each agent is performing relative to the complexity of what they handle.

Why it matters: Raw ticket counts are misleading. An agent resolving 20 complex technical escalations may carry a heavier load than one closing 80 password resets.

Metrics to track:

Tickets assigned, handled and resolved per agent
Average handle time and CSAT score
Outstanding ticket balance and escalation rate

How to act on it: Rebalance auto-assignment rules, spot early signs of overload, and target coaching where handle times spike on specific issue types.

FocalScope tip: Use the ticket queue equalizer and auto-assignment rules to even out workload, then check this report next month to confirm it worked.

How Do You Turn Monthly Reports Into Action?

At the end of each review, choose two or three priorities, assign an owner to each, and check progress in next month’s report. Typical priorities include adjusting channel coverage, refining routing rules, fixing a tier-2 handoff, or updating the knowledge base.

Frequently Asked Questions

How often should support teams run these reports?

Monthly for trend analysis, alongside live dashboards for daily queue management. Quarterly reviews can then build on the monthly data.

What is the difference between average and median resolution time?

The average adds up all resolution times and divides by ticket count, so a few very slow tickets can inflate it. The median is the middle value and shows what a typical customer experiences. Report both.

What is a good SLA compliance rate?

It depends on your targets and customer commitments. Many teams aim for the high 90s on critical tickets, but the more useful measure is the trend over time and where breaches cluster.

Which support report should a new team lead start with?

Start with ticket volume and channel trends. It explains your demand, which gives context to every other report.

Can I build these reports in Excel?

Yes. Excel works well for filtering and pivoting support data, provided your helpdesk exports clean, consistent fields across channels.

Run Every Monthly Report in One Place With FocalScope

Monthly reporting only works if data from every channel lands in the same place. FocalScope brings it together:

Omnichannel reporting: email, voice, live chat, WhatsApp and social data in one platform
70+ built-in reports: ticket volume, SLA performance, backlog and agent productivity, delivered as ready-to-use Excel templates
Customisable Excel engine: filter, adapt and pivot metrics in a familiar format
Scheduled delivery: reports sent automatically to team leads’ inboxes on the schedule you set

Book a 30-minute demo and see your team’s performance in one view.

Related Topics