{"id":"cx-ceo-note-angry-enterprise-approved-only","audience":"executives","category":"support-work","technique":"constraints","track":"support","level":"advanced","title":"Draft a CEO note that promises only what has been approved","free":false,"task":"Draft a short email from the CEO to Ms. Alvarez. First line exactly \"Dear Ms. Alvarez,\" and last line exactly \"Sam Okoro, CEO\". Include only the approved actions and the committed date. Do not name a cause, mention contract changes, or promise anything not approved. Plain text, under 90 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"CUSTOMER LETTER (Ms. Alvarez, COO of Orbit Logistics)\n\"Your platform was down on Nov 2 while our drivers were dispatching. We lost a morning. I expect an explanation, compensation and changes to our contract so this cannot recur.\"\n\nINTERNAL DECISIONS (as of Nov 6)\n- Approved by the CFO: a service credit of $5,000.\n- Approved: a call from our CTO, Dana Wu, within 2 business days.\n- Committed: a written root-cause report to the customer by Nov 20.\n- Root cause: still under review; do not guess.\n- Contract changes: NOT approved and not under discussion. Legal will handle any contract request separately.\n- The outage ran from 02:14 to 04:40 UTC on Nov 2.","rules":[{"type":"plainText"},{"type":"maxWords","max":90}],"mistakes":[{"title":"Promising contract changes","why":"The AI responds to her contract request.","fix":"Say: \"No contract changes; only the approved actions.\"","checks":["r2"]},{"title":"Guessing the cause","why":"The AI explains why the outage happened.","fix":"Say: \"Do not name a cause; the report comes by Nov 20.\"","checks":["r2"]},{"title":"Leaving out the committed date","why":"The AI promises a report 'soon'.","fix":"Say: \"Give the report date Nov 20.\"","checks":["r1","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":"Quotes the first and last lines","patterns":["dear ms\\. alvarez","sam okoro, ceo"]},{"label":"Lists the approved actions","patterns":["\\$5,000","2 business days","nov 20"]},{"label":"Rules out unapproved promises","patterns":["only (the )?approved","don'?t promise","no contract"]},{"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+"]}],"hint":"Quote the first and last lines, list the approved actions and say what must not be promised.","rubricLabels":["The email starts with the line \"Dear Ms. Alvarez,\" and ends with the line \"Sam Okoro, CEO\"","The email mentions the $5,000 service credit, a call from Dana Wu (the CTO) within 2 business days, and the written root-cause report by Nov 20","The email does not name a cause, does not promise or discuss contract changes, and does not promise any other compensation"]}