The prompt
Score 10 of 10, Excellent
Use it when Your support team answers the same questions every day, and you want a set of saved replies built from your policies, each with when to use it.
- {{company}}
- {{channel}}
- {{policies}}
- {{ticket_types}}
- {{voice}}
- {{fields}}
Full prompt and why it works
Prompt
Build a library of support macros (saved replies) for {{company}} from our policies and our most common tickets, for our agents to use in {{channel}}. Agents send these many times a day, so each one has to be accurate to the policy and say plainly when not to use it. A wrong macro spreads a wrong answer to every customer who gets it. Our policies, with section numbers: """ {{policies}} """ Our most common ticket types, with rough volumes if known, and examples of what customers write: """ {{ticket_types}} """ Our voice: {{voice}} Fill-in fields our help desk supports, exactly as written (for example [FIRST_NAME], [ORDER_NUMBER]): {{fields}} For each common ticket type, write one macro with: - Name: a short label agents can search, such as "Refund: outside 30 days" (form only). - Use when, and do not use when: one line each. - The reply: under 120 words, with fill-in fields in square brackets and numbered steps where the customer must do something. Put the policy section in a note for agents, not in the customer's text. - What the agent must check or change before sending. Then add: 1. A table of all macros with the columns Name, Ticket type, Policy section, Needs agent judgment (yes or no). 2. Ticket types that should not get a macro at all because each case needs a person, such as complaints about staff or safety issues. 3. Policy gaps: questions customers ask that the policy does not answer, marked [POLICY NEEDED]. Use only what the policies say. Do not add refunds, credits, exceptions, timelines or promises they do not contain, and keep every condition and time limit. Avoid stock phrases such as "We apologize for any inconvenience" and "Please do not hesitate to contact us". A good macro reads like a person wrote it for this customer once the fields are filled in. If a ticket type is not covered by any policy, list it under the gaps instead of writing a macro. If two policies conflict, quote both there rather than choosing one.
Variables
- {{company}}
- Your company, for example "an online furniture store".
- {{channel}}
- Where agents use them, for example "email and live chat".
- {{policies}}
- Your support policies with section numbers: refunds, shipping, warranty, accounts and so on.
- {{ticket_types}}
- The most common ticket types, with rough volumes and examples of what customers write.
- {{voice}}
- How you sound, for example "friendly, plain, first names, no jargon".
- {{fields}}
- The fill-in fields your help desk supports, exactly as written.
Why it works
- What to avoid. Every condition and time limit is kept and no refund, credit or exception is added, because a macro repeats its mistakes to every customer.
- Format. Each macro carries its own use-when and do-not-use-when lines, and the summary table shows which ones need an agent's judgment.
- If unsure. Tickets no policy covers, and policies that conflict, go to a gaps list marked [POLICY NEEDED] instead of becoming macros.