PR-2089 · Live
Return Trace
When a repair job closes at a place the team has already visited recently, Return Trace notices the repeat. It checks whether the same kind of work happened at that location inside a window the Service Manager sets. When it finds a match, it links the new job back to the original one. Then it builds a one-page brief on what most likely caused the repeat: the location's recent service history, which technicians worked it during that stretch, how old the affected equipment is, and whether a repair quote was offered and turned down. The Service Manager reads the brief and records what they are going to do about it. They might coach the tech, change a program, send a replacement quote, or call the customer. When the field management system is connected, that decision is written straight back onto the original job.
The promise
The Service Manager opens a repeat job and the story is already on one page. They can see when the team was last here, who worked it, how old the equipment is, and whether a fix was offered and declined. The digging across service history, dispatch records, and equipment files is done. They spend their time on the decision that matters, whether that is coaching the tech, changing the program, or quoting the replacement, and they do it without holding the whole location's history in their head. The repeats they used to miss now come to them linked and explained, and the pattern behind them is finally visible.
How it works
The path from input to value.
- 01
A repeat job closes
When a repair or remediation job closes, Return Trace checks the location for earlier work of the same type inside the window the Service Manager set.
- 02
The repeat job is linked
If it finds a match, Return Trace ties the new job back to the original one and flags it as a callback.
- 03
The brief gets built
Return Trace pulls together the recent service history, the techs who worked the location, the affected equipment's age, and any declined quote, into one page.
- 04
The Service Manager decides
They read the brief and record the action they are taking: coaching, a program change, a replacement quote, or a customer conversation.
- 05
The decision lands on the job
When the field management system is connected, the recorded corrective action is written back onto the original job so it lives with the work.
The day before. The day after.
Same moments. Lived differently.
The Service Manager sits down with last week's callback list. Six repeats. They start on the first one, opening the location and scrolling its recent service history.
8:30 AMThe six callbacks are waiting as briefs, each already linked to the original job, with the history, the techs, the equipment age, and any declined quote on one page.
8:30 AMBefore
The Service Manager sits down with last week's callback list. Six repeats. They start on the first one, opening the location and scrolling its recent service history.
After
The six callbacks are waiting as briefs, each already linked to the original job, with the history, the techs, the equipment age, and any declined quote on one page.
They are still assembling the evidence. They cross-reference dispatch to see which techs were out there, open the equipment record, and look for the quote the customer declined. They get through three of the six before the morning gets away from them.
9:15 AMThey work through all six, recording a corrective action on each: coaching for one tech, a replacement quote on two aging units, a program change on another.
9:15 AMBefore
They are still assembling the evidence. They cross-reference dispatch to see which techs were out there, open the equipment record, and look for the quote the customer declined. They get through three of the six before the morning gets away from them.
After
They work through all six, recording a corrective action on each: coaching for one tech, a replacement quote on two aging units, a program change on another.
A repeat from two weeks ago closes again at the same address. It logs as a new job and nobody flags it as rework, so it never makes the callback list.
1:00 PMThe repeat at the same address closes and Return Trace links it on its own. It shows up as a callback instead of disappearing into the new-job pile.
1:00 PMBefore
A repeat from two weeks ago closes again at the same address. It logs as a new job and nobody flags it as rework, so it never makes the callback list.
After
The repeat at the same address closes and Return Trace links it on its own. It shows up as a callback instead of disappearing into the new-job pile.
They suspect a few of these are the same furnace model but they haven't had time to confirm it. The pattern stays a hunch.
4:00 PMThree of the week's callbacks were the same furnace model. The brief made the pattern obvious, and they have already taken it to the GM.
4:00 PMBefore
They suspect a few of these are the same furnace model but they haven't had time to confirm it. The pattern stays a hunch.
After
Three of the week's callbacks were the same furnace model. The brief made the pattern obvious, and they have already taken it to the GM.
What it doesn’t do
The edges we drew on purpose.
A product that tries to do everything ends up doing nothing well. Here’s what we left out, and why we don’t feel bad about it.
- ×Watches closed jobs only; it does not monitor open or in-progress jobs for risk.
- ×Does not schedule, dispatch, or book the rework visit.
- ×Does not file or manage warranty claims.
- ×Does not produce first-time-fix rate or technician scorecards as a standalone report.