Support teams write the same kinds of replies all day — acknowledgements, apologies, refunds, escalations, and FAQs — and the difference between a great reply and a robotic one is tone and specificity. This pack gives you prompt templates for each scenario, with fill-in-the-blank variables so every reply starts warm, clear, and on-brand.
How it works
Each prompt gives the model the three things a good support reply needs: the customer’s issue, the product, and the tone. The bracketed fields let you paste the actual ticket and set whether the reply should be formal or friendly. Filter by ticket type, fill in the brackets, copy, and run — then add the human detail before sending.
Tips for support that doesn’t feel automated
- Set the tone explicitly. “Friendly, plain-spoken, no corporate jargon” produces very different replies than “formal.” Match it to your brand and the customer’s mood.
- Use the empathy bank for hard moments. Angry or disappointed customers need validation before a fix. The de-escalation and empathy prompts give you genuine phrasing, not clichés.
- Standardise escalations. A consistent escalation summary saves engineering hours of thread-reading and gets your customer a faster answer.
- Protect customer data. Redact personal and payment details before pasting anything into an AI tool, and only use tools your data policy permits.