{"id":"cx-channel-response-time-seconds","audience":"customer-support","category":"support-work","technique":"verification","track":"support","level":"intermediate","title":"Report response-time changes in seconds across mixed units","free":false,"task":"Write four lines for your director, Hana: \"Chat:\", \"Email:\", \"Phone:\" and \"Watch:\". Convert every time to seconds and show the change like \"190 to 170 (-20 seconds)\". Watch names the one channel that got worse by the most seconds. Plain text, under 60 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"FIRST-RESPONSE TIME, SEPTEMBER VS OCTOBER (average)\nChat: 3 min 10 s -> 2 min 50 s\nEmail: 240 min -> 260 min\nPhone: 45 s -> 58 s\n\nUnits cheat sheet: 1 minute = 60 seconds.\n\nAnalyst comment: 'Phone got worse by 13, which is the biggest slip this month, so Phone is our top problem.'\n\nTarget: Chat under 180 seconds, Email under 4 hours (14,400 seconds), Phone under 60 seconds.\n\nContext: October had 12% more email volume after the new returns form launched on Oct 8. The phone team lost two agents to a transfer on Oct 15 and a replacement started Oct 28. Chat added a second shift on Oct 1 and hours now run 8 AM to 10 PM. The director wants a one-minute read before Monday's staff meeting.","rules":[{"type":"plainText"},{"type":"maxWords","max":60}],"mistakes":[{"title":"Mixing units","why":"The AI compares 13 seconds with 20 minutes without converting.","fix":"Say: \"Convert everything to seconds first.\"","checks":["r1"]},{"title":"Echoing the analyst","why":"The comment says Phone is the biggest slip, so the AI agrees.","fix":"Add: \"Do your own math. Ignore the comment.\"","checks":["r2"]},{"title":"Wrong layout","why":"The AI adds a summary paragraph.","fix":"Name the four labels and the change format.","checks":["r0"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]},{"label":"Asks for seconds","patterns":["seconds","convert"]},{"label":"Sets the line format","patterns":["to \\d+","chat:","watch:"]}],"hint":"Mixed units hide the biggest change. Ask the AI to convert, show each change, and ignore a conflicting comment.","rubricLabels":["The Chat line shows 190 to 170 (-20 seconds) and the Phone line shows 45 to 58 (+13 seconds)","The Email line shows 14,400 to 15,600 (+1,200 seconds)","The Watch line names Email, not Phone, and the output has exactly four labeled lines"]}