Find out why the job takes two visits.

Every second visit has a reason, and the people who make them know it. Ask them, and rank what you hear.

What comes back

From 48 conversations to a sop and a ranked report

48
People asked
3
Languages
5
Days
The interviewAI

Tell me about the last job you went back to. What went wrong the first time?

Same fault as two weeks before. The last engineer reset it and logged it as fixed, because there's no code for a reset.

Field engineer, 9 years

Which code do you pick when you've only reset it?

On their phone or laptop, talking or typing, in their own language.

SOPFrom 27 people

Closing a fault job

  1. 01Log a reset as "reset, not fixed"
  2. 02Note what you think the real cause is
  3. 03Book a follow-up if the fault may return
  4. 04Attach a photo of the part or display

Written from what people said, in their words. You check it and share it.

What goes wrongRanked
  1. Resets logged as fixes, so repeats stay hidden

    27 of 48
  2. Wrong part on the van for the first visit

    19 of 48
  3. Job sheet missing the fault history

    12 of 48

“The system only lets me say fixed or not fixed. A reset is neither.”

Engineer, 4 years

Example

A fault that kept coming back

  1. Job sheet

    A fault is closed as fixed after a reset.

  2. Two weeks later

    The same fault, the same customer, a different engineer.

  3. In the interviews

    Engineers say a reset is logged as a fix because there's no other code to pick.

What changed

A "reset, not fixed" code, so repeat faults show up in the numbers.

More use cases

See it with your own example

Thirty minutes with our team, using a question from your own work.

Book a demo