Crewlantern Customer Support Update, May 2027 All Hands
Department update presentation for an all hands slot
A department update presentation has to tell the rest of the company, in a ten minute slot, how the team performed, what it is working on next and what it needs from everyone else. The customer support team at Crewlantern, an invented onboarding software company, reports April in six numbers, shows how reply times recovered after a product launch, welcomes two new people and ends on one ask.
Every slide, in order
The whole deck as it renders, one slide after another. Read it the way the audience would.
The structure
What each slide is doing, so you can reuse the order even with different content.
- Slide 1cover
- Names the department and its ten minute slot, so the update stays the length of the slot.
- Slide 2metrics
- Tickets, response time and satisfaction in six cards, the numbers every department wants from support.
- Slide 3metrics
- First reply time by week, showing the spike after the mobile launch and the recovery.
- Slide 4metrics
- What customers contacted support about, so other teams see which part of the product drives the work.
- Slide 5pillars
- The three priorities for the next quarter, each with the number it should move.
- Slide 6profile
- Welcomes the two new hires by name, inside the whole team, so everyone knows who to ask.
- Slide 7takeaway
- One customer comment that sums up April, with the evidence behind it.
- Slide 8closing
- Closes with one ask of the other teams, which is the point of a department slot at all hands.
Slide by slide
Slide one names the department and the ten minute slot. Slide two gives six numbers for April, from 2,150 tickets to a 4.6 satisfaction rating. Slide three charts first reply time by week. Slide four shows what customers asked about. Slide five sets three priorities to September: faster, fewer and earlier, each with one number. Slide six welcomes the two new hires within the whole team. Slide seven is one customer comment, backed by the change that caused it. Slide eight asks every team to post release notes five working days before a change reaches customers.
How to adapt this deck
A sales team should replace tickets and reply time with pipeline and win rate, and use the pie for deals by source. An engineering team should show releases and incidents, and turn the team slide into a short tour of who owns which part of the product. If your slot is five minutes rather than ten, keep slides two, five and eight: the numbers, the priorities and the ask. Everything else can go in a written follow up linked from the meeting notes.
What measurement guidance says
The GOV.UK Service Manual advises designing metrics with a clear meaning tied to what a service is for, and combining them with user research rather than relying on numbers alone. Its guidance on user satisfaction recommends letting users give feedback at several stages so a team can see which parts cause problems. This update does both: a small set of defined measures, plus ticket topics and a customer comment that explain them.
What makes this deck work
The chart explains a story others lived
Slide three plots first reply time weekly from 1 March: 3.1 hours, a climb to 6.2 after the mobile launch on 10 March, then down to 2.5 by May, under the 4 hour target. Every team remembers the launch, so the chart connects support's numbers to an event they already know about.
Ticket topics point at other teams
The pie on slide four splits 2,150 April tickets into six topics, led by payroll exports at 645, or 30 percent. That is a message for product and sales, not only for support, and it sets up the help centre priority on slide five and the ask on slide eight.
The new hires are shown inside the team
Slide six welcomes Amara and Theo inside the full team of 17, with each person's role. Colleagues learn who handles payroll exports and onboarding questions, which is more useful than two names on their own and makes the welcome feel less like an announcement.
Questions people ask
What should a department update at an all hands include?
A few headline numbers, one chart that tells the period's story, what the team is working on next, any people news, and one clear ask of other teams. Keep it to the length of the slot, usually five to ten minutes, and leave detail for a written follow up.
How many slides should a department update have?
Six to eight for a ten minute slot, about a minute each with time for questions. More than that and presenters rush the slides that matter. If the update has to be shorter, keep the numbers, the priorities and the ask, and drop the rest.
How do I make a team update interesting to other departments?
Connect your numbers to things they did or will do, such as a product launch that caused a spike in tickets, and end with a specific ask of them. People pay attention when the slide is about their work, not only yours.
How do I introduce new hires in a team update?
Show them inside the whole team with their roles, so colleagues know who does what and where the newcomers fit. Add one line on how to say hello. A single slide is enough; longer introductions belong in a team channel post with photos and a short bio.
Which customer support metrics belong in an all hands update?
Volume, speed, resolution and satisfaction: tickets, first reply time, solved on first contact and the survey rating. Add one ratio that links to the business, such as tickets per customer. Leave agent level statistics and queue detail for the team's own weekly review.
Can I reuse last month's update as a starting point?
Yes. Open last month's deck, update the numbers and chart data, and save; earlier versions stay in the version history if you need to compare. To keep both months as separate slides, use Duplicate slide in the rail, since there is no duplicate deck action.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make one like thisOther presentation examples
Post mortem presentation example: timeline, cause, fixes
A post mortem presentation has to show what happened, who was affected and why, without blaming a person, and leave the room with fixes that have owners and dates. Tallisor, an invented payments company, reviews a 47 minute card payments outage caused by one mistyped setting, traces it through five links in a failure chain, and commits to seven dated remediations.
Leadership team update deck: eight slides every week
A weekly leadership team update has to show, in under half an hour, whether the numbers moved, whether last week's decisions actually happened, and what each executive needs from the others before next Monday. Gantrywell, an invented managed detection company, runs the same eight slides every week, starting from six fixed numbers and ending on three asks with names and dates.
Project status report presentation example in 8 slides
A project status report presentation has to show, in the few minutes a leadership meeting gives it, whether the project is on schedule, budget and scope, what changed since the last report, and what the leaders need to do. Palletgrove Distribution, an invented wholesaler, reports week 22 of a 39 week warehouse system rollout: amber overall, one site two weeks late, and four asks.
Want the steps in the builder? Read Add charts, maps and diagrams to slides, then Edit your deck with the AI assistant. For everything this generator can do, see the presentation maker.
Written and checked by the OneCraft team. Last checked .