Wisaven
🗓️

Year-End Review PPT Template: Numbers, Highlights, Next Year

A year-in-review deck tells a team's year in a few numbers, the highlights, what fell short and what was learned, a moment worth remembering, thanks to the people, and next year's goals.

Get these right

  1. 1Three numbers that sum up the year beat a slide of twenty.
  2. 2Highlights are results, each with the people who made them.
  3. 3Name what fell short before anyone else does.
  4. 4Next year's goals should be few and measurable.

Structure

The deck opens with these slides, in this order.

  1. 1Year in reviewTitle
  2. 2The year in numbersBullets
  3. 3HighlightsBullets
  4. 4What fell shortBullets
  5. 5A momentQuote
  6. 6Next yearBullets
  7. 7Thank youClosing

A complete example · 13 slides

Designed by the AI from this brief, exactly as the workbench would design yours:

A 2026 year-in-review for an eight-person customer-support team, presented at the company's year-end meeting: 46,000 tickets handled, CSAT up from 4.2 to 4.6, median first response down from 11 to 6 minutes; highlights: the self-help knowledge base (15% of tickets deflected), the 48-hour payment escalation with the payments team; fell short: the knowledge base launched two months late; a moment: the customer whose report found a checkout bug; thanks to the shift leads; 2027 goals: automate first replies for the top five issues, CSAT 4.7.
Customer Support 2026
Year in review from an eight-person team · Company year-end meeting
Speaker notes · Thank you for having us. We are eight people, and this is what 2026 looked like from the support desk. I will cover the year in three numbers, what went well, what did not, one moment that stayed with us, and where we are heading in 2027.
The year in numbers
Three figures that tell the story
2 / 13
Speaker notes · Let us start with the scoreboard. Three numbers sum up the year: volume, satisfaction and speed.
Three numbers that define 2026
  • •46,000 tickets handled by eight people
  • •CSAT rose from 4.2 to 4.6
  • •Median first response fell from 11 to 6 minutes
3 / 13
Speaker notes · Forty-six thousand tickets came through the queue this year, handled by a team of eight. Customer satisfaction climbed from 4.2 to 4.6. And the median time to a first reply nearly halved, from eleven minutes to six. The next two slides show those last two changes side by side.
First response time nearly halved
05101520Start of 2026End of 2026116minutes
  • •Median first reply down from 11 to 6 minutes
  • •Faster replies came without adding headcount
4 / 13
Speaker notes · At the start of the year a customer waited eleven minutes for a first reply; by year end it was six. We did this with the same eight people, mainly through the knowledge base deflecting routine questions and clearer shift handovers.
Satisfaction climbed to 4.6
01.252.53.755Start of 2026End of 20264.24.6out of 5
  • •CSAT up 0.4 points over the year
  • •Speed and self-help both pushed the score up
5 / 13
Speaker notes · Satisfaction moved from 4.2 to 4.6 out of 5. That is a big shift for a score that normally moves in hundredths. Faster first replies and the ability to self-serve on common questions are the two drivers we can point to.
Highlights
Two things that changed how we work
6 / 13
Speaker notes · Behind the numbers are two projects we are especially proud of.
Two wins that changed the work
  • •Self-help knowledge base now deflects 15% of tickets
  • •Customers find answers before they need to write in
  • •48-hour payment escalation agreed with the payments team
  • •Payment problems now have a fixed, visible resolution clock
7 / 13
Speaker notes · First, the self-help knowledge base. Fifteen percent of would-be tickets are now resolved by customers themselves, which is roughly one ticket in seven that never reaches the queue. Second, the 48-hour payment escalation path we set up with the payments team. Payment issues used to drift; now they have a firm deadline and both teams can see it.
What fell short: the knowledge base shipped two months late
  • •Knowledge base launched two months behind plan
  • •We underestimated the writing and review effort
  • •Two months of tickets we could have deflected
  • •Lesson: scope the content work, not just the tooling
8 / 13
Speaker notes · Not everything went to plan. The knowledge base launched two months late. We planned the tooling carefully but underestimated how long it would take to write and review the articles. That cost us two months of deflection. The lesson we are taking into 2027 is to scope the content work as its own project, not as a side task.
“[customer's exact words needed] — one careful report that led us to a checkout bug”
— A customer, 2026 support ticket
9 / 13
Speaker notes · One moment stands out. A customer wrote in with a detailed report, and that report led us to a bug in checkout that we had not seen. It is a reminder that support is also the company's early-warning system, and that listening carefully to one person can protect everyone else.
Thank you to our shift leads
  • •Shift leads kept the queue steady through every peak
  • •They trained new joiners while handling tickets themselves
  • •They owned the handover that made six-minute replies possible
  • •None of the three numbers happen without them
10 / 13
Speaker notes · I want to thank our shift leads specifically. They kept the queue moving through every peak, trained new colleagues while still taking tickets, and built the handover discipline behind our six-minute first response. The numbers on the earlier slides are theirs.
Next year
2027 goals
11 / 13
Speaker notes · Finally, where we are going next.
2027: automate the routine, raise the bar
  • •Automate first replies for the top five issues
  • •Free agents for the cases that need a person
  • •Lift CSAT from 4.6 to 4.7
  • •Apply the knowledge base lesson: plan content early
12 / 13
Speaker notes · Two goals for 2027. First, automate first replies for our five most common issues so agents spend their time on cases that genuinely need a person. Second, lift CSAT from 4.6 to 4.7. And we will apply this year's lesson by planning the content work up front.
Thank you
46,000 tickets · CSAT 4.6 · 6-minute first response — see you in 2027
13 / 13
Speaker notes · Thank you to the whole company for trusting us with your customers. Forty-six thousand tickets, a 4.6 CSAT and six-minute first replies. We are happy to take questions.

Names, figures and dates in the example are made up for illustration; pictures were generated.

How it works

  1. 1Open the template: a deck with this structure and the brief appears.
  2. 2Add one line about your case, or attach your notes, spreadsheets or recordings as sources, and press First draft.
  3. 3Edit any slide yourself, or ask the AI to tighten it, chart its figures, add a picture or reorder the deck; download .pptx when it is ready.
✨ Make one from this template

Questions

Does the .pptx open in PowerPoint, Keynote and WPS?
Yes. Text, bullets, pictures and speaker notes are ordinary PowerPoint objects, and charts are native charts you can edit there.
Can I use the example as it is?
The example shows the shape; its names and figures are made up. Open the template and give the AI your own facts, and it designs yours in the same shape.
Is it free?
Writing is billed by the tokens used, usually a few credits per deck; a generated picture is 4 credits; the template, the editor and the download cost nothing.

Other kinds of deck

AI PPT generator →Document to PPT →Everyday documents →
📊Work reportResults, problems, next steps, asks — for a manager or a committee.🧭Project proposalWhy, what, how, how much, by when — to get a yes.📦Product introductionWho it is for, what it does, why it is better, how to get it.🎓Training deckObjectives, concepts, examples, practice, summary.🚀Pitch deckProblem, solution, market, traction, team, ask — ten slides.