{"id":"exec-customer-call-notes-crm-json","audience":"consultants","category":"leadership-work","track":"leadership","level":"intermediate","technique":"format","title":"Convert customer call notes into a CRM JSON record","free":false,"task":"Convert the call notes into one JSON object in a single code block with exactly these keys: account, contact, call_date (YYYY-MM-DD), sentiment (positive, neutral or negative), commitments (array of objects with owner and action), next_step_date (YYYY-MM-DD or null), risks (array of strings, at most 2). Use only the notes. At most 16 lines inside the block, and nothing outside it.","materialLabel":"Call notes (attached to your prompt automatically)","material":"Call with Brisa Foods, Thursday March 6, 2025, 30 minutes.\n\nContact: Dani Ruiz, Purchasing Lead. Dani sounded relieved about the renewal terms; positive overall, though she said the onboarding last year \"dragged\".\n\nCommitments\n- Dani will send the updated delivery locations list by Tuesday March 11.\n- Our side: Marcus will confirm the new pricing sheet in writing by Friday March 7.\n- Our side: Tessa will schedule a training session; no date yet.\nNext step: follow-up call on March 20.\n\nRisks mentioned: their budget approval is pending until the end of March; the second warehouse go-live might slip (Dani unsure).\nOther: Dani asked about the weather. Dani's cat. (irrelevant)\nEarlier notes said the call was on March 5; the correct date is March 6.","rules":[{"type":"codeBlocks","count":1},{"type":"maxCodeLines","max":16},{"type":"maxProseWords","max":5}],"mistakes":[{"title":"Old call date","why":"The AI uses March 5.","fix":"Say: \"The call was March 6.\"","checks":["r0"]},{"title":"Too many risks","why":"The AI lists 4 risks.","fix":"Say: \"At most 2 risks, from the notes.\"","checks":["r2"]},{"title":"Wrong keys","why":"The AI adds extra keys.","fix":"Say: \"Exactly the seven keys.\"","checks":["r0"]},{"title":"Missing commitments","why":"The AI omits Tessa's.","fix":"Say: \"Include all three commitments.\"","checks":["r1"]},{"title":"Extra text","why":"The AI explains.","fix":"Say: \"Only the code block.\"","checks":["codeBlocks","maxProseWords"]},{"title":"Too many lines","why":"The AI pretty-prints.","fix":"Say: \"At most 16 lines inside.\"","checks":["maxCodeLines"]}],"promptHints":[{"label":"Keys","patterns":["account","contact","call_date","commitments","next_step_date","risks"]},{"label":"ISO","patterns":["yyyy-mm-dd"]},{"label":"Sentiment","patterns":["positive","neutral","negative"]},{"label":"Limit risks","patterns":["at most 2"]},{"label":"One block","patterns":["code block","only"]}],"hint":"List the keys, date format, allowed sentiment values and the risk limit.","rubricLabels":["The JSON has exactly the keys account, contact, call_date, sentiment, commitments, next_step_date and risks, with call_date 2025-03-06 (not 03-05) and sentiment positive","commitments is an array of three objects with exactly the keys owner and action: Dani (send delivery locations list by 2025-03-11 or by Tuesday), Marcus (confirm pricing sheet in writing by 2025-03-07) and Tessa (schedule training); next_step_date is 2025-03-20","risks has at most 2 strings about the pending budget approval and the possible warehouse go-live slip, and nothing is outside the code block"]}