Reply to an angry customer without grovelling or stonewalling
Drafts a reply that acknowledges the real problem, says exactly what happens next, and promises nothing you cannot deliver.
Builds a reusable reply for a question you answer every day, with clearly marked places to personalise so it never goes out generic.
Works with Claude, ChatGPT, GeminiUpdated 2026-09-27
Use this for the question your team answers twenty times a week. A good saved reply saves the time without sounding copied, and the trick is marking exactly where the agent has to make it specific.
Opening this in Claude or ChatGPT sends the prompt with its {{PLACEHOLDERS}} still in it. Replace them with your own details before you send, or copy the prompt and fill them in first.
The question we keep getting, with two or three real examples of how customers ask it:
{{QUESTION}}
Our answer, and how we like to sound:
{{ANSWER_AND_TONE}}
Write a saved reply.
- Put [SQUARE BRACKETS] around every part the agent must change for each customer, with a note inside saying what goes there. At least one bracket must be in the first sentence, so no reply opens identically.
- Answer the question in the first three sentences. Put any detail after.
- End with the single next step for the customer, not "let us know if you have any other questions".
- Under 120 words, not counting brackets.
Then give two short variants: one for a customer who is already frustrated, and one for a customer who has asked twice.End of prompt: Write a saved reply that does not read like a saved reply
Drafts a reply that acknowledges the real problem, says exactly what happens next, and promises nothing you cannot deliver.
Converts a support thread that ended in a fix into a help article written for the next customer, not for the agent who solved it.
New prompts as they go up, plus founder essays on shipping AI systems. ~2 emails / month.
Prompts get you started. If you want this wired into how your team actually works, see what we do.