{"id":"cs-integration-slip-sponsor-email","audience":"customer-success","category":"support-work","technique":"tone","track":"support","level":"intermediate","title":"Tell a sponsor an integration slipped without excuses","free":false,"task":"Write an email to Ms. Varga. Line 1 is \"Subject:\" with 7 words or fewer. Use exactly 4 sentences: the new date, the cause on our side, what we are doing, and one thing we need from her. No excuses and no blame. Last line exactly \"Raf, Customer Success\". Plain text.","materialLabel":"Your material (attached to your prompt automatically)","material":"PROJECT: Varga Logistics, ERP integration. Sponsor: Ms. Elena Varga (COO).\nOriginal go-live: Nov 16. New go-live: Dec 7.\nCAUSE (ours): our connector fails on purchase orders with more than 200 lines; engineering found it on Nov 2. A fix is in testing and due Nov 20.\nWHAT WE DO: Kit (engineer) tests the fix against Varga's real orders on Nov 23-24; then a one-day dry run on Dec 1.\nNEED FROM HER: Varga's IT must keep the test system available Nov 23-24 (confirm by Nov 13).\nNOT TO SAY: 'the customer's data is messy' (a teammate wrote that). Nor blame on engineering vendors.\nElena likes direct emails: new date first.","rules":[{"type":"plainText"},{"type":"maxWords","max":110}],"mistakes":[{"title":"Blaming the data","why":"The teammate's note says the customer's data is messy.","fix":"Add: \"No excuses and no blame.\"","checks":["r2"]},{"title":"Burying the new date","why":"The AI explains first and gives the date last.","fix":"Say: \"Sentence 1 is the new date.\"","checks":["r1"]},{"title":"Wrong sentence count or lines","why":"The AI writes six sentences and a generic subject.","fix":"Say: \"Exactly 4 sentences; subject 7 words or fewer; exact last line.\"","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":"Orders the sentences","patterns":["new date","cause","ask"]},{"label":"Bans blame","patterns":["no excuses","no blame"]}],"hint":"Bad-news emails lead with the new date, own the cause and make one clear ask. Name the order and the limits.","rubricLabels":["Line 1 begins with \"Subject:\" with 7 words or fewer, and the last line is exactly \"Raf, Customer Success\"","Has exactly four sentences: the new go-live of Dec 7, the cause (our connector fails on purchase orders over 200 lines), what we are doing (testing the fix Nov 23-24 and a dry run Dec 1), and the ask (keep the test system available Nov 23-24, confirmed by Nov 13)","Makes no excuses and does not blame the customer's data or any vendor"]}