07.05 Crisis PR: Batch-Level Major Quality Defect Recall and Overseas Sentiment Defense
Governance metadata | Owner: Finance & Legal Lead | Last reviewed: 2026-10-22 | Next review: 2027-01-31
Core principle: a crisis is not "deleting posts to put out the fire", but a graded, transparent and traceable systematic response; it must connect seamlessly with the crisis grading (P0/P1/P2) of the 01.10 GR4 Launch Operations Gate, with sentiment monitoring front-loaded, recall messaging unified, and a clear position for media/KOL responses.
1. Misconceptions Corrected
- Misconception 1: crisis = negative sentiment, just delete the posts. Deleting posts escalates the conflict, and regulators and platforms have zero tolerance for "manipulating public opinion"; the correct action is a graded response + factual clarification + a closed loop of corrective action.
- Misconception 2: a recall is Legal's business. The external recall messaging, channel delisting coordination and user compensation position must be aligned across marketing / PR / legal / supply chain; otherwise conflicting positions amplify the crisis.
- Misconception 3: KOLs only handle seeding, not crises. In a crisis, top KOLs and the media are both amplifiers and shock absorbers; trust and an emergency communication channel must be built in advance.
- Misconception 4: each crisis tier runs its own show. The sentiment / recall / media response in this document must map onto the P0/P1/P2 grading of the 01.10 GR4 Launch Operations Gate, to avoid a mismatch in response intensity.
2. The Sentiment Monitoring System
| Monitoring layer | Target | Frequency | Trigger signal |
|---|---|---|---|
| Social media volume | Xiaohongshu / Douyin / Weibo / e-commerce reviews | Daily | A spike in negative volume, keyword clustering |
| E-commerce reviews | Negative reviews / return reasons | Daily | Safety words such as fire / overheating / injury |
| Media / regulators | News reports / inspection announcements | Weekly + real time | A regulator naming the brand, media verification requests |
| Competitors / industry | Spillover from similar incidents | Weekly | Industry-wide sentiment spillover |
3. Alignment with the Crisis Grading in the 01.10 GR4 Launch Operations Gate
| Level | Determination | Response action | External position |
|---|---|---|---|
| P0 | Safety incident / mandatory recall / regulatory case filing | Launch the highest-level response, with CEO-level command | A unified statement + proactive recall + a compensation plan |
| P1 | Concentrated complaints / media verification requests / widespread negative reviews | A cross-functional team responds within 24h | Factual clarification + a corrective-action timetable |
| P2 | Isolated negative posts / single complaints | Routine handling by customer service and the community | A case-by-case response, recorded and archived |
The grading determination and organisational ownership are reused directly from the crisis grading plan in the 01.10 GR4 Launch Operations Gate; this document adds the sentiment monitoring inputs and the library of external messaging.
4. The Recall PR Messaging Framework
- First thing: confirm the facts, lock down the scope of impact, and do not speculate externally before the internal position is unified.
- Statement structure: incident statement → measures already taken → user compensation / recall path → corrective-action commitment → contact channel.
- Taboos: shifting blame, vague timing, and compensation that cannot be delivered; the messaging must be consistent with the recall process in 07.02 Market Access: US/EU/Japan Wireless Compliance (FCC_CE_TELEC) and EPR Environmental Recycling and with the P0 contingency plan in the 01.10 GR4 Launch Operations Gate.
5. Media / KOL Response
- Media verification requests: appoint a single spokesperson who responds within 2~4h with "received, under verification", avoiding the escalation that "no comment" causes.
- KOL coordination: proactively share the facts and the position with KOLs you have worked with, and strive for an objective retelling; for top accounts you have not worked with, keep monitoring without active steering.
- Evidence trail: archive all external communication records, as the basis for subsequent regulatory explanations and legal defences.
6. Crisis Escalation Response Decision Tree
Sentiment / incident signal triggered
│
├─ Is it a safety incident / regulatory case filing / mandatory recall?
│ ├─ Yes ──➔ Escalate to P0 and launch the highest-level response in the [01.10 GR4 Launch Operations Gate]
│ │ └─ A unified statement + proactive recall (aligned with [07.02 Market Access: US/EU/Japan Wireless Compliance (FCC_CE_TELEC) and EPR Environmental Recycling])
│ └─ No ──➔ Move to the next level of determination
│
├─ Is it concentrated complaints / media verification requests / widespread negative reviews?
│ ├─ Yes ──➔ P1, with a cross-functional team responding within 24h
│ └─ No ──➔ P2 routine handling
│
└─ P2: a case-by-case response + record and archive, with continued monitoring for escalation7. Crisis Response Checklist
[ ] Monitoring rules: daily scanning of safety words and negative sentiment volume is configured
[ ] Grading mapping: signals are mapped to the P0/P1/P2 tiers of the 01.10 GR4 Launch Operations Gate
[ ] Spokesperson: a single external spokesperson has been appointed, and the messaging library is ready
[ ] Recall messaging: the statement structure template and the compensation path are ready (P0)
[ ] KOL channel: an emergency communication list of partner KOLs has been built
[ ] Evidence trail: all communication records are traceable
[ ] Drills: the crisis grading plan has been drilled ≥1 time per year
8. Traffic Lights (RAG)
| Step | 🔴 Red | 🟡 Yellow | 🟢 Green |
|---|---|---|---|
| Monitoring | Flying blind with no monitoring | Rules still to be refined | Daily + real-time coverage |
| Grading | Response intensity mismatched | Determination pending confirmation | Clearly mapped to the 01.10 GR4 Launch Operations Gate |
| Messaging | Each department says something different | Messaging still to be unified | A single spokesperson + templates |
| Recall | Concealing and not reporting | Compensation still undecided | Proactive recall + a closed loop |
9. Counterexample
After a hardware brand saw a batch of overheating complaints, the marketing team deleted posts first, Legal did not step in, and the customer service position contradicted the official statement; the media caught it as "manipulating public opinion + concealment", regulators intervened and issued a network-wide notice, and brand trust fell off a cliff. Root cause: failure to connect with the graded contingency plan of the 01.10 GR4 Launch Operations Gate, treating the crisis as a PR post-deletion instead of a systematic response.
10. Further Reading
- Crisis grading for launch operations and production-sales coordination ➔ 01.10 GR4 Launch Operations Gate
- Shipwreck-grade overseas compliance risks and the recall process ➔ 07.02 Market Access: US/EU/Japan Wireless Compliance (FCC_CE_TELEC) and EPR Environmental Recycling
- The domestic compliance recall handover ➔ 07.01 Market Access: China CCC Mandatory Certification, E-Commerce Compliance and the Data Security Law (PIPL)