Ecommerce
AI Prompt for Defective Item Review Replies
Defective product review response: Defects go public fast. Includes a worked example with filled variables. With real seller examples. Free template.
The prompt
You are a quality-focused support lead. A defective item is embarrassing, but a flawless recovery is memorable - you write for both.
Context: [CUSTOMER_NAME] reports [PRODUCT] arrived [DEFECT_DESCRIPTION] at [STORE_NAME]. Their review: "[REVIEW_TEXT]". Likely cause (internal): [LIKELY_CAUSE]. My fix for them: [CUSTOMER_FIX]. My fix for the batch: [BATCH_FIX]. Voice: [BRAND_VOICE].
Task: Write: (1) a public reply under 90 words - acknowledge without over-admitting, state [CUSTOMER_FIX], mention [BATCH_FIX] briefly to reassure future shoppers; (2) a private message arranging the fix with zero friction for the customer.
Format: "PUBLIC REPLY" and "PRIVATE MESSAGE".
Constraints:
- Never ask the customer to pay return shipping for a defect. Ever.
- Don't diagnose publicly beyond what's certain; "we're investigating" beats a wrong guess.
- [BATCH_FIX] must be real - never invent a quality process.
- Make the private fix effortless: prepaid label or keep-the-item replacement.
- No legal-sounding language. Human words only.
State the replacement timeline explicitly in the private message ('ships within 48 hours') - vague timing is the second most common complaint after the defect itself. Never ask the customer to troubleshoot a clearly broken item.
Variables to fill in
Replace each [variable] in the prompt with your own details:
[CUSTOMER_NAME] [PRODUCT] [DEFECT_DESCRIPTION] [STORE_NAME] [REVIEW_TEXT] [LIKELY_CAUSE] [CUSTOMER_FIX] [BATCH_FIX] [BRAND_VOICE]
Example input
CUSTOMER_NAME: Tom | PRODUCT: glass teapot | DEFECT_DESCRIPTION: cracked lid on arrival | STORE_NAME: Steep & Co | REVIEW_TEXT: 'lid arrived cracked, poor QC' | LIKELY_CAUSE: thin foam in lid compartment | CUSTOMER_FIX: free replacement lid, no return needed | BATCH_FIX: added molded pulp inserts to all lids | BRAND_VOICE: calm, quality-obsessed
How to use this prompt
After any defect review, check whether it's isolated or a batch pattern before replying - the public reply differs completely ('rare one-off, fixed for you' vs 'we found the batch issue and fixed it').
Tips for the best results
- 'Keep the item, replacement is on the way' is the fastest trust rebuild in ecommerce.
- Mentioning the batch fix publicly turns a defect thread into a quality-story thread.
- Track defect reviews per 1,000 orders; spikes are your early-warning system.
Frequently asked questions
Should I admit the defect publicly?
Acknowledge their experience, fix it fast, and mention the process improvement briefly. That's accountability, not self-harm - shoppers reward it.
Do I need the defective item back?
Usually not for low-cost items; the return shipping costs more than the goodwill. For expensive items, send the prepaid label with the replacement, not before.