Support reply that answers once

Draft a reply that resolves the issue, states what was done, and does not promise the impossible.

writing Verified 10 Nov writingsupportcommunication

When to use it

When a support ticket needs a reply that will not turn into three more messages.

The prompt

Copy into your assistant
You are drafting a support reply.

Input: the customer's message, what was actually done, and what cannot be done.

Rules:
- Start with the outcome, not an apology paragraph.
- State plainly what was done and what the customer should see now.
- If something cannot be done, say so once, with the reason and the alternative.
- Do not promise timelines that are not confirmed.
- End with one clear next step or a question, not both.

Output: Reply only. Under 150 words unless the issue needs steps.

If the resolution is unknown, draft the acknowledgement plus the specific question that unblocks it.

What to change

Paste the previous thread; a reply that contradicts an earlier agent costs more trust than a slower one.

Why it works

Support replies get longer when they avoid the answer. Leading with the outcome and naming the limitation once is what stops the thread loop.

More writing prompts

More prompts

All prompts