{"id":"cs-jargon-status-to-coo-plain","audience":"customer-success","category":"support-work","technique":"tone","track":"support","level":"beginner","title":"Rewrite an engineering status for a non-technical COO","free":false,"task":"Rewrite the internal status as a message to Mira, a COO who is not technical. Start with \"Hi Mira,\". The first sentence must answer her question about the Dec 1 launch honestly, and the message gives no date for the fix. Do not use these words: ETL, schema, connector, staging, QA, hotfix, tenant. Plain text, under 70 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"MIRA'S QUESTION (Nov 5): \"Is the Dec 1 launch still safe? I just need a straight answer.\"\n\nINTERNAL STATUS FROM ENGINEERING:\n\"ETL pipeline for the Daybreak tenant is blocked on schema drift in the SFDC connector. A hotfix is in staging; QA is pending. Prod ETA TBD. Likely end of next week but no commitments. Risk to downstream dashboards until resolved.\"\n\nCONTEXT: Daybreak's launch Dec 1 depends on their sales data appearing in the new dashboards. Mira's team has 60 people ready to start. Mira dislikes hedging but also dislikes surprises.\nYou are Kofi, the CSM.","rules":[{"type":"plainText"},{"type":"maxWords","max":70}],"mistakes":[{"title":"Passing along the likely date","why":"The AI includes \"end of next week\" as an estimate.","fix":"Say: \"Give no date for the fix.\"","checks":["r2"]},{"title":"Keeping the jargon","why":"The AI keeps words like pipeline, connector or hotfix.","fix":"Say: \"Plain words only; do not use ETL, schema, connector, staging, QA, hotfix or tenant.\"","checks":["r1","r2"]},{"title":"Burying the answer","why":"The AI explains the problem before answering her question.","fix":"Say: \"The first sentence answers her question about Dec 1.\"","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":"The AI runs long and cannot count its own words.","fix":"Cap each part (\"each line under 12 words\") and add \"under N words in total\".","checks":["maxWords"]}],"promptHints":[{"label":"Names the reader and opening","patterns":["hi mira","non-technical","not technical"]},{"label":"Answers first","patterns":["first sentence","answer"]},{"label":"Bans jargon and dates","patterns":["jargon","plain","no date","don't use","do not use"]},{"label":"Caps length","patterns":["\\d+\\s*words","under \\d+"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a word cap","patterns":["\\d+\\s*words","under \\d+","word"]}],"hint":"Translate for the reader: answer their question first, use their words, and say what you will not promise.","mission":"Tell Mira honestly whether the Dec 1 launch will happen.","musts":["Answer in first sentence","No fix date","No tech jargon"],"rubricLabels":["The message starts with \"Hi Mira,\" and its first sentence says plainly that the Dec 1 launch cannot be confirmed yet (or is not yet certain)","It explains in everyday words that the sales data is not moving into the dashboards because of a mismatch with their CRM, and that a fix has been built and is being tested","It gives no date for the fix, uses none of the words ETL, schema, connector, staging, QA, hotfix or tenant, and does not promise the launch"]}