Review recalls for root causes
Never paste: Employee pay, disciplinary records with full names, customer addresses and phone numbers, or medical/personal info about techs.
When to use it
Weekly or monthly, to cut repeat visits.
The prompt
Copy this, then replace everything in [brackets].
Analyze our recalls.
Recalls: [list: date, tech initials, original repair, recall reason, equipment brand/age]
Group by cause (missed diagnosis, part failure, install issue, customer education), spot patterns by tech or repair type, and suggest 3 fixes (training, checklist, part supplier).
Before / after
Before: Recalls blamed on ‘bad parts’ forever.
After (example output):
Pattern: 5 of 9 recalls were capacitor replacements on units 12+ years old; 3 of those also had a weak contactor. Fix: add a contactor check to the capacitor repair checklist. Tech pattern: 4 of 9 from one tech, so schedule a ride-along.
Tips
- Look at patterns, not blame.
- Use tech first names or initials in prompts.
- Coach behaviors, not personalities. Ask the AI to keep it specific.
- Review every draft before you send it. You’re accountable for what goes out.
Fill in the brackets
Type your details and the prompt below updates. Everything stays in your browser.
Leave out: Employee pay, disciplinary records with full names, customer addresses and phone numbers, or medical/personal info about techs. Use initials or general terms instead.