{"id":"agent-sales-post-demo-followup-workflow","audience":"sales","category":"agents","track":"agents","technique":"constraints","title":"Brief an agent to build a follow-up automation with stop rules","free":false,"task":"You want an AI agent to build a post-demo follow-up automation in your CRM. Write its brief: trigger when a deal's stage changes to Demo Done, send emails on day 1, 4 and 10, stop the sequence if the prospect replies, books a meeting, or the deal is marked Lost, skip anyone marked Do Not Email, and never activate it: ask you to review first. Output exactly 10 numbered plain-text lines: trigger, 3 steps, 4 conditions, ASK_HUMAN, DONE.","materialLabel":"Meeting notes, CRM fields and actions (attached to your prompt automatically)","material":"Notes from sales team meeting (Tue), Kestrel CRM rollout\n\n- Reps forget to follow up after demos. Want it automatic.\n- Jess: three emails is enough. Day 2, 5, 12? Marco thinks sooner is better.\n- Templates exist already: \"Demo recap\", \"Case study\", \"Last check-in\".\n- Last quarter someone emailed a prospect who had asked us to stop. Legal was not happy.\n- Marco: \"can it also text people?\" (we don't have SMS set up)\n\nCRM fields available:\ndeal.stage (Lead, Demo Booked, Demo Done, Proposal, Won, Lost)\ncontact.do_not_email (true/false)\nactivity.reply_received (true/false)\nactivity.meeting_booked (true/false)\n\nAvailable actions:\ncreate_trigger(event)\nadd_step(day, template)\nadd_condition(if, then)\nactivate_workflow()\nASK_HUMAN(question)\nDONE(summary)","rules":[{"type":"numberedItems","count":10},{"type":"plainText"}],"promptHints":[{"label":"Names the trigger","patterns":["trigger","demo done"]},{"label":"Sets the schedule","patterns":["day 1","1, 4","\\b10\\b"]},{"label":"Adds stop conditions","patterns":["stop","repl","lost","meeting"]},{"label":"Respects do-not-email","patterns":["do.?not.?email","opt.?out","unsubscrib"]},{"label":"Forbids activating","patterns":["activat","go live","turn on"]}],"mistakes":[{"title":"Not showing the log format","why":"Left alone, the AI writes a friendly report with headings instead of a checkable action log.","fix":"Show it literally: \"Format every line like 1. ACTION: tool(args), then ASK_HUMAN: and DONE: lines. Plain text.\"","checks":["numberedItems","plainText"]},{"title":"Leaving the schedule open","why":"The notes float days 2, 5 and 12, so the AI uses those or invents its own.","fix":"Say: \"Steps on day 1, 4 and 10, triggered when stage changes to Demo Done.\"","checks":["r0"]},{"title":"No stop conditions","why":"Automations keep emailing people who already replied or said no.","fix":"Add: \"Stop on reply, meeting booked or Lost. Skip do_not_email contacts.\"","checks":["r1"]},{"title":"Letting it go live","why":"Given activate_workflow, the AI turns it on as soon as it's built.","fix":"Add: \"Never activate. Ask me to review, then DONE.\"","checks":["r2"]}],"hint":"An automation runs forever once it's on. Spell out the trigger, the timing, every reason to stop, and that you switch it on.","rubricLabels":["The trigger is deal.stage changing to Demo Done, and the three add_step lines are on day 1, day 4 and day 10 (not days 2, 5 and 12)","Has add_condition lines that stop the sequence on a reply, a booked meeting and the deal moving to Lost, plus one that skips contacts with do_not_email true","There is no activate_workflow line; an ASK_HUMAN line asks you to review before activation, and the last line starts with DONE"]}