# Q3 Customer Support Review — practice brief Use this brief for two separate presentation projects. Section A follows the structure, chart and notes lessons. Section B follows the final presentation project. Each project has its own six-slide starter and solution. The scenario and data are for practice. This file is Markdown text. You can follow it in a new PowerPoint presentation or download the matching editable PPTX. A starter leaves work for you to do. A solution is an example to compare with your result. ## Section A: structure, chart and speaker-note practice Audience: practice leadership team. Duration: ten minutes. Purpose: agree a weekend rota and two new self-service articles. Files: - [powerpoint-chart-starter.pptx](/en-assets/practice/powerpoint-chart-starter.pptx) - [powerpoint-chart-solution.pptx](/en-assets/practice/powerpoint-chart-solution.pptx) The starter has six slides with real title placeholders. Slide 3 has an empty content placeholder for your chart. The solution shows the result after the October extension, with an editable chart on slide 3 and an editable reference table on slide 5. Both files include Context (slides 1–2), Results (slides 3–5) and Next steps (slide 6) sections. The solution chart has alt text describing the monthly values and period totals. Review that text when you change the data. ### Section A slide map 1. Q3 Customer Support Review — context and purpose. October is a follow-up outside the quarter. 2. Response times improved in every region — a hypothesis for layout practice. No measured response-time series is supplied, so keep the hypothesis label visible. 3. Ticket volume peaked in August — enter Jul, Aug and Sep in the chart lesson. The exercise adds Oct and changes the title to Ticket volume fell steadily after the August peak. 4. Self-service articles reduced repeat tickets — a hypothesis for layout practice. No measured repeat-contact experiment is supplied. 5. Weekend staffing gap remains — the question the team must resolve. Put the five-row Month/Tickets reference table on this existing detail slide. 6. Next steps: weekend rota and two new articles — the proposed decision request. Use Section A for the lessons Use layouts and sections, Build a readable chart, and Use speaker notes and share the right PDF. The result-style titles on slides 2 and 4 need their hypothesis labels until you replace them with statements supported by your own evidence. ## Section B: final presentation project Audience: leadership. Duration: ten minutes. Dana proposes a four-week weekend rota pilot and two draft self-service articles. Their outcomes have not been measured. The ticket figures do not supply savings, staffing costs or a causal explanation. Files: - [presentation-capstone-starter.pptx](/en-assets/practice/presentation-capstone-starter.pptx) - [presentation-capstone-solution.pptx](/en-assets/practice/presentation-capstone-solution.pptx) The capstone starter has the six title placeholders below. Use its content placeholders and the facts in this brief to build the slides. Its notes contain the supplied facts and prompts for each slide. The solution has its editable four-month chart on slide 2. Both capstone files include Context (slide 1), Evidence (slides 2–3) and Decision (slides 4–6) sections. The solution chart has alt text describing the supplied figures and their limits. Review the final reading order and alt text in your own presentation before sharing it. ### Section B slide map 1. Review purpose — introduce the leadership review and the decision to consider a pilot. 2. Monthly evidence — show Jul 1240, Aug 1610, Sep 1180 and Oct 1050 in a native clustered-column chart. Start at zero, label the unit Tickets and highlight August only. 3. Interpretation limits — ticket volume declined after August. Causes and cost effects are unverified. 4. Proposed pilot — name Dana, four weeks, a weekend rota and two draft self-service articles. Keep the work described as proposed. 5. Measurement plan — list weekly ticket volume, repeat-contact rate and coverage observations as proposed measures. 6. Decision requested — ask approval to run the pilot. Add no invented budget, staffing requirement or guaranteed reduction. Use Section B for Build a complete support-review deck. Keep this final project at six slides, including its Review purpose slide. Use the supplied Context, Evidence and Decision sections to organise the thumbnails, or create the same sections if you start in a new presentation. ## Shared ticket dataset and answer checks Month,Tickets Jul,1240 Aug,1610 Sep,1180 Oct,1050 August is the peak. The total for Jul–Sep is 4030. July–October totals 5080. October is an exercise extension for Section A and is outside Q3. Section B uses all four months from the start. The August-to-October fall is 560 tickets. Dividing 560 by August's 1610 gives approximately 34.8%. This measures the ticket-volume decline. No cost-saving figure is supplied. ## Checks before sharing Use real title placeholders, an editable native chart and readable labels. Keep the chart values, table values, time-window labels and speaker notes consistent. Add two to four short speaker cues per slide and rehearse Presenter View. Export attendee slides separately from notes pages. Run Accessibility Checker and open the actual files you plan to deliver. For Section A, compare the four chart bars with the reference table on slide 5. For Section B, check that Interpretation limits and Measurement plan remain separate slides and that the audience handout contains six slide pages without your notes. ## Optional extensions belong in separate practice copies The structure lesson asks you to add a seventh Questions slide and a Close section to a copy of Section A. Neither supplied six-slide solution includes that extension. Keep the capstone files at six slides. The chart lesson's reference table fits on the existing fifth slide. A separate extra evidence slide can be useful in your own work, but is not required for the six-slide practice files.