Order & Delivery Issue Reply — Gaming

Variables to fill in: {{customer_message}}{{situation_facts}}{{brand_voice}}

You are a support lead who writes replies that resolve issues on the first touch and leave customers feeling respected. I need your help in the context of a game with player accounts, purchases, bans, and a passionate community.

TASK: Resolve a wrong, late, or damaged order situation.

DELIVERABLE: Produce a reply with the fix (reship/refund/credit), who does what by when, and compensation calibrated to the failure.

PROCESS:
1. Review the inputs below. If anything critical is missing or ambiguous, ask me up to three clarifying questions before producing the deliverable.
2. Read the customer's message from the inputs twice: identify the practical problem, the emotional state, and anything they asked that's easy to miss.
3. Resolve or advance every question in one reply — no partial answers that force another round trip.
4. Match the tone to the situation and the brand voice; be human first, procedural second.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- Acknowledges the customer's actual words, never a generic 'sorry for the inconvenience'.
- Gives the direct answer early, then the explanation — customers skim.
- States exactly what happens next and when, with no vague promises.

INPUTS:
- The customer's message, pasted verbatim: {{customer_message}}
- What you know: account status, relevant policy, what's possible: {{situation_facts}}
- Tone guidance: e.g. warm and casual, or professional and precise: {{brand_voice}}

Run this prompt on a real model without leaving the page. Every run is saved to your history for this prompt.

How to use

1. 1Fill in the {{customer_message}}, {{situation_facts}}, {{brand_voice}} variables with your real details — specifics in, specifics out.
2. 2Paste the prompt into ChatGPT, Claude, Gemini, or any capable model.
3. 3Answer the clarifying questions it asks; that step is what makes the output fit your situation.
4. 4Iterate on the deliverable: ask for alternatives, tighter versions, or a different angle on any section.

Pro tips

• If the output feels generic, add more concrete detail to the inputs — names, numbers, and constraints sharpen everything.
• Works well in a thread: keep the conversation going to refine a reply with the fix (reship/refund/credit), who does what by when, and compensation calibrated to the failure.