{"id":"cs-qbr-outline-from-account-data","audience":"customer-success","category":"support-work","technique":"grounding","track":"support","level":"intermediate","title":"Outline a QBR deck from account data, dip included","free":false,"task":"You're presenting a QBR to Fenwick Hotels' VP of Guest Services. Outline the deck as exactly 5 numbered slides, each formatted \"Slide title: one key number from the data\". Use the final Q3 numbers, not the preliminary ones, show the ticket spike honestly instead of hiding it, and make slide 5 the asks for next quarter. Plain text.","materialLabel":"Account notes (attached to your prompt automatically)","material":"Fenwick Hotels - Q3 account data (pulled Oct 6)\n\nSeats: 340 licensed\nMobile check-in adoption: 74% of properties (PRELIMINARY - see below)\nAvg check-in time: 6.1 min -> 3.4 min (Q2 to Q3)\nGuest satisfaction (their survey): 4.2 -> 4.5 out of 5\nSupport tickets: 38 in Q3 vs 12 in Q2 (spike from the Aug key-card integration update; fixed Sept 9)\nProperties live: 41 of 55\n\nEmail from analytics (Oct 9): \"Correction on Fenwick - final Q3 mobile check-in adoption is 68%, not 74%. Three properties were double counted.\"\n\nOur asks for Q4 (from account plan):\n- Roll out to the remaining 14 properties\n- Name an exec sponsor for the loyalty-app integration\n\nInternal only: we're raising list prices 6% in January. Not announced yet.","rules":[{"type":"numberedItems","count":5},{"type":"plainText"}],"mistakes":[{"title":"Using the first number you see","why":"The AI takes the 74% from the data table and misses the later correction.","fix":"Say: \"Use final Q3 numbers; the Oct 9 correction overrides the table.\"","checks":["r0"]},{"title":"Hiding the bad news","why":"The AI builds a highlights-only deck and drops the ticket spike.","fix":"Ask: \"Include one slide on the ticket spike and the fix, plainly.\"","checks":["r1"]},{"title":"Leaking internal info","why":"The AI treats everything in the notes as fair game, including the unannounced price change.","fix":"Add: \"This is customer-facing. Leave out internal-only items.\"","checks":["r2"]},{"title":"No fixed shape","why":"The AI writes a long deck with speaker notes and sub-bullets.","fix":"Say: \"Exactly 5 numbered slides, one line each, slide 5 is our asks.\"","checks":["numberedItems","r2"]},{"title":"Letting markdown in","why":"The AI bolds slide titles.","fix":"Say: \"Plain text, no bold or headings.\"","checks":["plainText"]}],"promptHints":[{"label":"Sets the slide count","patterns":["\\b(5|five)\\b.{0,10}slides?"]},{"label":"Uses the corrected number","patterns":["final","correct","68"]},{"label":"Keeps the bad news in","patterns":["ticket","spike","honest"]},{"label":"Keeps internal info out","patterns":["internal","price","customer.facing"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown"]}],"hint":"A deck for the customer needs final numbers, honest bad news, and nothing internal. Tell the AI all three.","rubricLabels":["Mobile check-in adoption is given as 68% (the final number), and 74% does not appear","One slide covers the support ticket rise (12 to 38) and that it was fixed on Sept 9","Slide 5 is the asks (roll out to the remaining 14 properties, name an exec sponsor), and the unannounced January price increase is not mentioned"]}