> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bad Review Response Prep

> After a poor CSAT score or negative review, prepare internal talking points plus an external response draft — facts from the ticket record only, zero defensiveness.

<Info>
  **Category:** Communication · [View source ↗](https://github.com/bryan-getthread/skills/blob/main/skills/communication/bad-review-response-prep/SKILL.md)
</Info>

**Connectors:** none — works with Thread out of the box

**Role:** [Technician](/start-here/roles/technician), [CSM / Account Manager](/start-here/roles/csm-account-manager)

**Outcome:** Retention & Growth (CSAT/Expansion), Fewer Escalations & Less Noise

**When to use:** "We got a bad CSAT on this ticket — help me respond" / "prep talking points before I call this client about their negative feedback" — a poor review or survey comment needs a considered reply, not a reflex.

**Run it:** on one ticket.

## Prompt

```
Turn a stinging review into two artifacts: an honest internal read of what actually happened,
and an external response that de-escalates instead of litigating.

1. Read the full ticket the review is attached to (and recent related tickets for the same
   contact). Build the factual timeline: response times, actions taken, commitments made and
   whether they were kept.

2. Produce the INTERNAL talking points first (for me/manager, never sent):
   - What the client experienced, stated from their side without rebuttal.
   - Where the record shows we fell short, plainly — missed follow-up, long gaps, unmet
     commitment. If the record shows we performed well, say that too; some reviews reflect
     frustration with the problem, not the service.
   - What the record does NOT establish — gaps where neither blame nor defense is supported.
   - One or two concrete make-it-right options grounded in what happened.

3. Then draft the EXTERNAL response (de-escalation posture):
   - Thank them for the feedback; acknowledge the specific experience they described.
   - Own what the record supports owning — specifically, not with a blanket grovel.
   - One concrete next step with a time commitment (a call from the service manager by <day>
     is the usual right move).
   - No corrections of their version of events, no policy citations, no "however."

4. Offer to store the talking points as a plain-text internal note, and show me the external
   draft for review. Output both clearly separated and labeled INTERNAL vs DRAFT REPLY.

Facts from the record only — never characterize what happened beyond what's documented, in
either direction. Zero defensiveness in the external draft: no rebuttals, no justifications, no
blaming a vendor, a colleague, or the client. If the review is factually wrong, the internal
points may say so; the external reply still doesn't argue. Never offer credits, refunds, or
concessions in the draft — flag "consider a goodwill gesture" internally and leave it to
management.
```


## Related topics

- [Audit Prep Review](/skill-library/compliance-and-audit/audit-prep-review.md)
- [Escalation Prep](/skill-library/escalation/escalation-prep.md)
- [QBR & SBR Prep](/skill-library/account-management/qbr-and-sbr-prep.md)
