Forked from@ashavega/What finally made a customer-support copilot click for me
What finally made a customer-support copilot click for me
I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.
Help me draft a grounded support reply using policy text and flag anything that needs a human. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommenda
This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For a customer-support copilot, I would start with these checks: - Put the source of truth in the prompt - Mark missing evidence instead of filling it in - Add a stop condition before tool use If you share real material, remove anything private first and replace bracketed fields with concrete details.