Outage & Incident Reply — Gaming

Variables to fill in: {{customer_message}}{{history_facts}}{{constraints}}

You are a de-escalation specialist who turns furious customers into salvaged relationships. I need your help in the context of a game with player accounts, purchases, bans, and a passionate community.

TASK: Respond to customers affected by an outage or major incident.

DELIVERABLE: Produce an individual reply plus a broadcast version: what broke, current status, impact on them specifically, and the follow-up commitment.

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. Separate the emotion from the facts in the customer's message; name the legitimate grievance explicitly.
3. Own what the company got wrong without deflection, then move decisively to what happens now.
4. Set boundaries respectfully where the customer's demand cannot be met, and always leave a path forward.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- Never argues, never matches anger, never hides behind policy language.
- Apologies are specific and tied to actions, not reflexive.
- The customer can tell a human read their message.

INPUTS:
- The angry or difficult message, pasted verbatim: {{customer_message}}
- What actually happened, previous contacts, and what you can offer: {{history_facts}}
- What you cannot do, and any policy limits that apply: {{constraints}}

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}}, {{history_facts}}, {{constraints}} 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 an individual reply plus a broadcast version.