Notify customers about a product recall or safety issue
Recall email, store and website notice, support script, and staff brief that state the hazard and remedy clearly and calmly.
The prompt
Help me write customer communications for a product recall or safety issue.
Product affected: [NAME, SKUs, model or lot numbers, dates sold, where sold]
The hazard: [WHAT CAN HAPPEN - factual wording from the manufacturer or investigation]
Incidents reported: [NUMBER and type - or "none"]
Remedy: [refund / replacement / repair kit / disposal instructions]
How customers claim it: [URL, phone, hours, whether proof of purchase is needed]
Regulator involvement: [e.g. "announced jointly with the CPSC", another country's authority, voluntary - or [CONFIRM]]
Customers we can reach: [order emails, loyalty members, in-store buyers with no contact details]
Write:
1. A direct email and SMS to known buyers. Subject line says "recall" and names the product. Then: stop using it now, the hazard in plain words, how to identify affected units, the remedy, how to claim it.
2. A website banner, recall page, and in-store sign for buyers we cannot reach.
3. A support script and FAQ: how do I find the lot number, I threw away the receipt, I bought it as a gift, I resold it, someone was hurt.
4. A short internal brief for store and support staff: what to say, what not to say, how to log reports, when to escalate.
Rules:
- Clear and calm. Never minimize the hazard or speculate about cause or fault. No marketing or upsells in any recall message.
- Do not invent incident counts, dates, or remedy terms; use [CONFIRM].
- If a customer reports an injury, tell them to seek medical care (emergency services if urgent) and log the report for the safety team.
- Legal, and the regulator where involved, must approve wording before anything is sent.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- NAME, SKUs, model or lot numbers, dates sold, where sold
- NUMBER and type - or "none"
- refund / replacement / repair kit / disposal instructions
- URL, phone, hours, whether proof of purchase is needed
- CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write order, shipping, refund, and delay noticesTransactional messages: confirmations, cancellations, refunds, shipping updates, and delays.
- Write a compliant collections call script for overdue accountsA debt collection call script with required disclosures, hardship options, and phrases to avoid under collection rules.
- Write status page, email, and agent updates for a service outageA customer communication kit for an outage: status-page updates for every stage, banner, social post, agent macro, and resolved email.
- Respond to a customer complaint at a bank or financial firmA fair, compliant complaint response that addresses each issue, explains the outcome, and states the customer's escalation rights.