2026 Annual Self-Review: Wang Fang, Customer Support Team Lead

My Role and Responsibilities

I lead an eight-person customer-support team covering three channels: email, chat and phone. My responsibilities over the year included:

• Setting and tracking the team's service targets (customer satisfaction, response time, retention).
• Staffing, scheduling and coaching across all three channels.
• Reporting on team performance to management.
• Representing support in cross-team work, in particular with the payments team.
• Owning support projects, including the knowledge-base launch.

Key Results Against 2026 Goals

All three headline goals for the year were met or exceeded.

CSAT: 4.6 against a target of 4.5

The team closed the year above the satisfaction target across email, chat and phone. [source needed: channel-level CSAT breakdown]

Median first response: 6 minutes against a target of under 8

We brought the median first response to 6 minutes, two minutes inside the target. The weekly dashboard (see below) made it possible to see response-time drift early and rebalance staffing across channels before it affected customers.

Turnover: 12% against a target of under 20%

Team turnover came in at 12%, well under the 20% ceiling. Keeping the team stable through the year supported both the CSAT and response-time results, since experienced agents resolve issues faster and more consistently.

How I Grew This Year

Data analysis

I built the team's weekly performance dashboard. It now gives us a regular view of CSAT, first response times and workload by channel, and it has become the basis for our staffing decisions and for my reporting to management. Building it required me to develop skills in working with our support data that I did not have at the start of the year.

Cross-team collaboration

I worked much more closely with the payments team this year. [figure needed: outcome of payments collaboration, e.g. issue volume reduced or process agreed] Working across team boundaries has improved how quickly payment-related customer issues are resolved and has given me a better understanding of how other parts of the business operate.

Where I Fell Short

Knowledge-base launch: two months late

The knowledge-base launch was my main project shortfall this year. It was delivered two months behind schedule. [source needed: planned vs. actual launch dates and the main causes of the delay]

What I take from this:

• I should have raised the schedule risk earlier rather than trying to absorb it within the team.
• Project milestones needed to be tracked with the same discipline I applied to the operational metrics on the dashboard.
• Launching later meant the team spent longer answering repeat questions manually, which is directly relevant to next year's automation goal.

Goals for 2027

1. Automate first replies for the top five issues

Build automated first responses for the five most common customer issues across email and chat. This builds on the now-launched knowledge base and on the dashboard data that identifies which issues recur most.

• Success measure: [figure needed: target share of first replies automated, or target reduction in agent-handled volume]
• Expected benefit: faster first responses and more agent time for complex cases.

2. Train two deputies

Develop two team members into deputies who can run the team's day-to-day operations in my absence.

• Success measure: [figure needed: date by which each deputy covers a full rota independently]
• Expected benefit: a more resilient team, clearer growth paths for staff, and more of my own time freed for cross-team and project work, which should also reduce the risk of project delays like this year's knowledge-base launch.

Closing

2026 was a year in which the team exceeded every operational target and in which I grew as a manager in both data and cross-team work. The late knowledge-base launch is the clear lesson, and the two 2027 goals are chosen to build on what went well while addressing that gap.