Every controller knows the ritual. You dispatch an engineer, then twenty minutes later you ring to check they are on the way. Later you ring again to see if they are on scene. Then once more to find out if it is done, because a network is asking. It feels like managing the job. Mostly it is just interrupting a busy person to ask a question the system should already know the answer to. Here is how to stop.

Why the phone chasing happens

You chase engineers because you are blind between "assigned" and "back at base". Once a job leaves your desk, the only way to find out what is happening is to ask the one person who is elbow-deep in it. So you call — and every call you make is a call that pulls the engineer's attention off the vehicle and onto their phone. You are creating the very interruption you would hate on your own shift.

The engineer is not being difficult. They are working. From their side, the office ringing every twenty minutes for a status they will report when they have a second is its own kind of friction. Both of you are stuck in a loop that exists only because information is not flowing on its own.

Flip the direction of the information

The fix is to stop pulling updates out of the engineer and let the updates push to you instead. That means giving the engineer a fast, one-tap way to move the job along — accepted, en route, on scene, completed — and having those changes appear on your dashboard the moment they happen. No call required in either direction. The engineer taps once with oily hands; you see it instantly.

When dispatch itself is done well, this starts at the beginning. A job that is assigned and pushed to the engineer by email and SMS already carries the address and the fault, so the engineer is not ringing you back for details either. The whole conversation you used to have on the phone becomes a set of taps and a live status.

What good status flow looks like

  • Assigned. The engineer gets the job on their phone with everything they need — no callback for the postcode.
  • Accepted. One tap tells you they have got it and are moving. If that tap does not come, you know to act — without having guessed.
  • On scene. A timestamp lands automatically, which doubles as your proof of attendance.
  • Completed. The job closes with notes and photos attached, ready to bill, and your dashboard clears it from the "open" list.

The knock-on wins

The first thing you get back is your own time — a controller not making status calls can log the next case and keep dispatch moving. The second is the engineer's time, and their goodwill, because nobody enjoys being rung every twenty minutes. But the quieter win is that those tapped statuses are timestamped, so you get proof of attendance as a by-product of not chasing. The evidence you used to extract by phone now records itself.

There is a customer benefit too. Once the engineer's status is flowing into the system, you can pass it straight on — the fleet watches a live update link instead of ringing you for the ETA you would otherwise have had to ring the engineer to get. One update, tapped once, serves the office, the customer and the invoice.

The habit to build

Getting there is mostly cultural. Agree with the team that the taps replace the calls: if the status is moving, the office does not ring, and in return the office trusts the status. It takes a couple of weeks for everyone to believe the loop is really broken. Once they do, the phone goes quiet in the best possible way.

Callout360 is built around exactly this flow for roadside repair agents — dispatch that reaches the engineer, one-tap statuses that push back, and a live dashboard so you can see the whole board without dialling a single number. Stop chasing. Start watching it come to you.