What to get right
- Log every recall the same way. Date, tech initials, original repair, why they came back, equipment brand and age.
- Sort by cause, not by tech. Missed diagnosis, part failure, install issue or customer education. The cause tells you the fix.
- Look for patterns. One repair type, one part supplier, or one tech after a certain time of day.
- Coach in private. If one tech shows up a lot, that’s a ride-along and a one-on-one, not a group email.
The prompt
This is the Review recalls for root causes workflow, word for word. Copy it, fill in the [brackets], and paste it into the AI tool your company uses.
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). Fill it in with the prompt builder → Open the full workflow
How to use it
- Pull the last month or quarter of recalls into a simple list.
- Use tech initials, not names, and no customer details.
- Run the prompt to group them by cause and spot patterns.
- Pick the three fixes and give each one an owner and a date.
- Run the same review next month and compare.
Related workflows
Questions shops ask
What causes most HVAC callbacks?
It varies by shop, which is why you sort your own list. The usual buckets are missed diagnosis, part failure, install issues, and customers who weren’t told what to expect.
Should techs be charged for callbacks?
That’s a pay-plan decision with legal limits in some states. Fixing the root cause usually does more than a penalty. Check your state’s wage rules before docking pay.
How often should we review callbacks?
Monthly works for most shops. Weekly is better during peak season if callbacks are climbing.
Weekly email
One new workflow a week for service shop owners and their teams.
HVAC, plumbing, electrical. No hype; unsubscribe whenever.