Why recall and safety wording needs a source card
A small business might have a manufacturer notice, email from a supplier, internal spreadsheet, order history, warranty page, replacement form, and customer-service macro that do not say the same thing. AI tools can compress that into dangerous certainty: “all units recalled,” “free replacement for everyone,” “safe to keep using,” or “refund guaranteed.” A source card gives the owner one approved reference before AI-assisted content or answers discuss safety, eligibility, or next steps.
STOP PUBLISHING: do not let AI invent affected products, serial-number ranges, severity, safety instructions, regulatory status, legal conclusions, warranty coverage, refund eligibility, replacement timelines, repair instructions, disposal advice, or customer-specific promises. Route safety, legal, compliance, product-liability, medical, child-safety, food, electrical, battery, vehicle, and regulated-product wording to the owner and qualified reviewer.
Copy/paste recall and safety-notice source card
| Field | What to capture | Review rule |
|---|---|---|
| Notice scope | Product name, SKU, lot/serial range, model, vendor/manufacturer, date issued, affected channel, and official source URL or document. | Do not apply one notice to all products, variants, locations, or customers unless the official source says so. |
| Risk statement | Approved plain-language risk, known incident source, customer action needed, and where the risk statement came from. | Never downplay, exaggerate, diagnose, or reinterpret a safety risk from an AI draft. |
| Customer action | Stop-use rule, contact path, inspection step, replacement form, repair path, return/refund path, disposal instruction, and escalation owner. | Owner/legal/compliance review is required before telling customers to keep using, stop using, modify, return, dispose, or repair a product. |
| Eligibility and proof | Receipt/order proof, purchase date, serial/lot/photo proof, location, warranty status, customer-safe verification language, and exception process. | Do not promise eligibility, refunds, replacements, credits, warranty coverage, or timelines without the active source. |
| Public wording boundary | Approved short answer, forbidden claims, internal-only details, customer support script, and update cadence. | Keep public wording narrow: what is affected, where to verify, what customers should do, and who reviews exceptions. |
Safe public wording templates
Recall/safety notice answer: Please verify whether your [product/model/SKU/lot/serial range] is included in the current notice at [official notice/support path]. Do not rely on AI summaries for eligibility, safety, warranty, refund, or replacement decisions.Customer action note: If your item may be affected, stop and follow the current instructions at [official path] or contact [support path]. Our team will review [order/serial/photo/proof] before confirming next steps.Internal AI note: STOP PUBLISHING. Do not invent affected products, risk level, safety instructions, legal/regulatory status, refund eligibility, replacement timelines, warranty coverage, or repair/disposal steps. Use only the approved source card.AI audit prompt
Act as a cautious AI-search and customer-support QA assistant. Review the recall/safety-notice source card below and identify claims an AI answer engine or support macro might overstate or invent.
Do not invent affected products, serial ranges, risk severity, safety instructions, legal/regulatory status, refund eligibility, replacement timelines, warranty coverage, repair steps, disposal instructions, or customer-specific promises. Use only verified sources.
Source card:
- Product/SKU/model/lot/serial range covered:
- Official manufacturer/vendor/regulatory/source URL:
- Notice date and last reviewed date:
- Customer action required:
- Proof needed from customer:
- Refund/replacement/warranty source:
- Support/escalation owner:
- Internal-only or sensitive details to avoid publishing:
- Conflicting stale pages, PDFs, ads, marketplace listings, or support macros:
Return: 1) approved public summary, 2) claims needing owner/legal/compliance review, 3) stale/conflicting source risks, 4) safe chatbot/FAQ answer, 5) STOP PUBLISHING items, and 6) next source-maintenance tasks.Weekly source-maintenance questions
- Do product pages, marketplace listings, PDFs, support macros, recall pages, email templates, and warranty pages point to the same official notice?
- Are affected SKUs, serial ranges, lots, dates, and customer actions clearly linked to a dated source?
- Can customers verify their item through an official path without relying on an AI summary?
- Which safety, legal, compliance, warranty, refund, replacement, or disposal claims require owner or qualified reviewer sign-off?