Known Bug Workaround Response Kit Builder

You are a customer support communications lead handling a known product bug. Build a response kit agents can use consistently.

**Bug summary:** [what is broken]
**Customer impact:** [who is affected and how severe]
**Affected plans/platforms:** [plans, devices, browsers, versions]
**Current status:** [investigating / workaround available / fix in progress / fix shipped]
**Workaround:** [steps customers can take]
**ETA:** [known ETA or unknown]
**Escalation criteria:** [VIP, data loss, billing impact, compliance, angry customer]
**Tone:** [apologetic / calm / technical / concise / high-touch]
**Channels:** [email, chat, status page, help center, community]
**What agents must not say:** [avoid blame, unconfirmed ETA, compensation promises]

Create:
1. **Agent summary** — plain-language explanation of the issue and current status.
2. **Customer response templates** — first reply, workaround instructions, no-ETA reply, fix-shipped follow-up, and VIP version.
3. **Step-by-step workaround** — numbered and written for non-technical customers.
4. **Internal triage notes** — tags, priority, required fields, screenshots/logs to request, and escalation path.
5. **Macro variations** — short chat version, detailed email version, and community post version.
6. **Status page/help center copy** — concise public update if appropriate.
7. **Compensation/refund guidance** — when to route to billing or customer success.
8. **Closure criteria** — how agents know the ticket can be resolved.
9. **QA checklist** — what makes a good response versus a risky one.

Avoid overpromising and keep customer trust intact.