Example Achievement Log for a Customer Experience Manager

This Customer Experience Manager tracked wins, operational shifts, and real feedback across the year to have substance for their review instead of vague memory. You'll see how naming specific metrics, who said what, and what didn't work the first time turns a brag document into something your manager can actually use.

A year in the life of a Customer Experience Manager's log

Jan - task: Took on Zendesk ticket categorization audit. Backlog was 8,000 old tickets with wrong tags. Sorting and relabeling to align with new product lines.
Feb - feedback: Maya said in standup that my email templates were 'actually readable for once' and she'd use them as model. Meant something since she's usually critical.
Feb - achievement: NPS went from 34 to 41 across Q1. Pushed support team to stop deflecting billing questions to finance, handle them same-day instead. Reduced escalation time by 6 days average.
Apr - task: Inherited response to CX survey showing 62% of respondents felt ignored after first contact. Built new intake form with priority flags. Launched May 15th.
May - achievement: Follow-up survey two months later: 'felt heard' went from 38% to 51%. Fewer repeat inquiries. Support handled 340 tickets in June vs 298 in May with same headcount.
May - feedback: Derek, the VP, told me in the parking lot he'd heard from two customers unprompted that we were easier to reach. Said that never happens.
Jul - task: Tried to automate post-resolution survey via Typeform API integration. Failed on day 1. Response rate was worse than email. Reverted Aug 4th, back to manual send.
Aug - achievement: Trained Priya and Amir to handle tier-2 escalations. Freed me to do quarterly calibration calls with top-complaining accounts. 8 calls, all stayed as customers.
Oct - task: Rebuilt support queue routing in Zendesk because seniority-based assignment left juniors with complex cases. Skill-tagged each person, weighted by product area. Went live Oct 19th.
Nov - achievement: CSAT on complex cases went from 71% to 79% in first month under new routing. Average handle time on billing queries dropped 12 minutes per ticket.
Dec - feedback: In the year-end all-hands, James singled out the team for keeping churn flat despite 40% increase in new customer volume. He knows that was structure, not luck.

What makes a strong entry

What most people write: Improved support processes and team performance.

What went in the log: Rebuilt support queue routing in Zendesk because seniority-based assignment left juniors with complex cases. Skill-tagged each person, weighted by product area. Went live Oct 19th.

The strong version names the actual system, the specific failure it solved, the concrete change made, and the date it landed. Without these, your manager has no way to verify it or remember why it mattered when six months have passed.

What most people write: Led effort to improve customer feedback and communication.

What went in the log: Inherited response to CX survey showing 62% of respondents felt ignored after first contact. Built new intake form with priority flags. Launched May 15th.

The strong version shows the starting problem as a number, the exact tool used to fix it, and when it went live. A vague 'led effort' disappears instantly; a numbered baseline and a ship date stick with whoever reads this later.

How this becomes your review in November

I inherited customer satisfaction metrics that looked stuck: NPS at 34, 62% of respondents feeling ignored after first contact, and support ticket categorization spread across 8,000 orphaned records. I rebuilt the intake workflow, retagged the entire backlog, and restructured support queue assignment to route cases to the right skill level instead of by seniority. By June, follow-up surveys showed 51% felt heard, up from 38%, and CSAT on complex cases reached 79%. The operational change had teeth: we processed 340 tickets in June with the same headcount that had done 298 in May, churn remained flat despite a 40% increase in new customer volume, and NPS climbed to 41. I also learnt quickly when the Typeform integration failed, reverted it within days and went back to what worked. Derek mentioned that customers had unprompted praise for us, which he said never happens.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Customer Experience Manager.