{"id":"cs-save-plan-weekly-calendar-no-calls-week","audience":"managers","category":"support-work","technique":"constraints","track":"support","level":"advanced","title":"Schedule a four-week save plan around a no-calls week","free":false,"task":"Build a four-week save plan table with the header row exactly \"Week of | Action | Owner\" and four rows for the weeks starting Mon Nov 9, Nov 16, Nov 23 and Nov 30. Place each action in the right week. No customer calls in the week of Nov 23. Plain text, table only, under 70 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"SAVE PLAN: Westgate Foods (renews Dec 31). Four actions, no fixed order except where noted:\n- Executive sponsor call with Mr. Hale (Pat). Must happen in the first week; it unblocks everything.\n- Usage review with the admin (Kit). Needs the sponsor call done first. Phone or video call.\n- Written success plan sent to Mr. Hale (Pat). Email only, not a call.\n- Director check-in call with Mr. Hale (Mira). A call; after the success plan is sent.\n\nCALENDAR: Nov 6 is a Friday. Mondays: Nov 9, Nov 16, Nov 23, Nov 30.\nBLACKOUT: Thanksgiving week (Nov 23-27): the customer asked for no calls that week; emails are fine.\nWeek 2's usage review needs the customer admin, who is available the week of Nov 16 only.\n\nDraft from Pat: 'Director call in week 3 is fine, Mira has a gap that week.' (Conflicts with the no-calls week.)","rules":[{"type":"plainText"},{"type":"maxWords","max":70}],"mistakes":[{"title":"Scheduling a call in the blackout week","why":"Pat's draft puts the director call in week 3.","fix":"Say: \"No customer calls in the week of Nov 23.\"","checks":["r2"]},{"title":"Wrong sequence","why":"The AI puts the usage review before the sponsor call.","fix":"Say: \"Respect the order: sponsor call, usage review, success plan, then the director call.\"","checks":["r1"]},{"title":"Wrong table","why":"The AI adds a notes column.","fix":"Give the exact header row and say table only.","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":"States the blackout","patterns":["no (customer )?calls","nov 23","blackout"]},{"label":"Gives the header","patterns":["week of \\|","header"]}],"hint":"Scheduling needs the dependencies and the blackout week. State both, the dates and the table header.","rubricLabels":["The header row is exactly \"Week of | Action | Owner\" with four rows for Nov 9, Nov 16, Nov 23 and Nov 30","The actions are placed: Nov 9 sponsor call (Pat), Nov 16 usage review (Kit), Nov 23 written success plan (Pat), Nov 30 director check-in call (Mira)","No call is placed in the week of Nov 23, and nothing is placed outside the table"]}