Dispatch board
A live view shows every engineer, job and van location, so reschedules happen before a client is kept waiting.
A technician dispatch app for managed IT providers fits how engineers really split their day between remote fixes, onsite visits and a van full of spare parts. SIZ Group designs and builds a staff operations app that puts each job, its checklist and the proof photos on the engineer's phone.
Remote monitoring alert triage starts when alerts from a tool such as NinjaOne or Datto RMM arrive in a shared inbox, and a dispatcher turns the important ones into tickets in a professional services platform, which is the gap that field service dispatch software should close. From there, the work splits. A remote fix stays at the desk, but an onsite job becomes a text thread, a voicemail and a sticky note about which door code to use at the dental office.
The breakdown points are predictable. Engineers take photos on personal phones that never reach the ticket. A swapped switch is recorded from memory, so the asset list drifts out of date. The invoice is built from a notebook two days later, and the client hears about the missed step on the next visit. Each of those gaps can be closed in the app.
The operations manager needs to see that a job closes with the same evidence every time. That means a checklist for each job type, required photos at the steps that matter, and a handover note that a second engineer can read on the way to the site. If the record is complete on the day of the visit, the manager has the proof a client asks for.
They also need the app to protect the dispatch board from chaos. Onsite technician scheduling in a live view shows who is on which job, where the van is and which visits are running late lets the dispatcher move work early rather than apologize later. The first demo should show a reschedule being made without a single phone call.
An engineer opens the app before leaving the depot and sees a firewall replacement at a small accounting office. The job card lists the old model, the new unit, the change window and the contact who will meet her at the door. She checks the spare parts list against the van and starts the drive.
On site, the IT field service checklist guides the work in order. She exports the current configuration, labels each cable, and photographs the rack before and after the swap. Each photo attaches to its own step, so nothing is lost in a camera roll. The VPN test is marked complete only after she confirms the remote user can connect.
Before she leaves, the client signs on the phone and the handover note goes to the next engineer who checks the site. The asset record updates with the new serial number, and the invoice draft is built from the job record. The next morning, the operations manager sees a closed job with every step and photo in place.
A live view shows every engineer, job and van location, so reschedules happen before a client is kept waiting.
Checklists follow the job type, with required steps that must be ticked before the job can close.
Photos attach to the step they document, with restricted access for sensitive client sites.
Serial numbers and configuration exports update the asset record as the job progresses.
Short notes travel with the job, so the next engineer arrives knowing what changed and what remains.
The client signs on the phone at the end of the visit, and the signed record goes straight into the job file.
Client site visit documentation carries the biggest risk, because photos are the usual form it takes. A picture of a clinic's server screen or a patient intake desk can capture protected health information, and under HIPAA that image becomes a record the provider must protect. The app should warn engineers before they photograph a screen, and it should restrict who can open photos from health-sector clients.
Device disposal is another point to get right. When a drive or old firewall is retired, the job record should capture the disposal method and the certificate from the disposal partner. Client admin passwords should never be written into a job note. Those details are routine for a good provider, and the app makes them easy to get right every time.
The build needs a current asset inventory export, the checklist for each service type and the list of technician skills, so the dispatcher can match the right person to a job. It also needs the site access notes for each client, which are usually the most valuable and most scattered details in the whole business.
Access rules should follow the job. Engineers see their own visits and the sites they are cleared to enter, while the dispatcher and manager see the full board. Billing rates stay with the finance role, and nobody in the field sees another client's network details.
Measure the numbers the business already tracks, then compare them with the months before launch. The useful ones are the share of onsite visits completed on the first attempt, the number of repeat visits caused by a missing step, the time between a visit and its invoice, and the number of client complaints about missed handovers.
Keep the baselines honest by pulling them from the existing ticket and invoice records, not from memory. If repeat visits do not fall after the checklists have been used for a full season, the checklist content needs work before the software does.
Mobile apps start at $4,500, and the final figure depends on the number of checklist types, the photo rules and the link to the professional services platform. The operations manager receives a written scope and price before the build begins, with later phases priced separately.
The job, checklist and photos are saved to the phone and sync automatically when a connection returns. The engineer can see a clear saved state, so nobody re-does a step thinking the first attempt failed. We test these flows in the places where signal is weakest.
Not on day one. The app reads tickets from the platform the provider already uses and writes back the time, notes and asset changes. Once the team trusts the job record, the provider can decide whether any further work should move across.
Photos are encrypted on the device and in storage, and access follows the client and the job. Health-sector photos can be restricted to a smaller group, and every view is logged. Retention periods are set by the provider and the client contract.
Not always. Engineers can use their own phones if the provider's device policy allows the app, and the app can enforce a screen lock and remote wipe. Companies that already issue phones can use those devices instead.
Book a call and SIZ Group will review how your engineers work today, then agree a written scope before any design begins.