One board.
Every install,
every day.
A dispatch board that closes its own loop. The technician's phone app posts the photo, the signature, the signal reading — and the same minute, the subscription activates and the install fee posts to the invoice.
A real install-to-activation workflow.
Field isn't an afterthought bolted onto a billing system. It's a first-class module, with a mobile app the technicians actually open.
Skill + area dispatch
Assign the right technician by skill set, vehicle, and service area. Auto-assign with a manual-override toggle for the awkward installs that need the senior pair of hands.
Mobile-first install app
A PWA the technician installs once. GPS check-in, photo capture, signal-strength entry, customer signature, completion — works offline and syncs the moment it gets a bar.
Auto-activate on close
Completed install closes the ticket, activates the subscription, posts the install fee — RADIUS auth ACKs before the technician has driven away.
Reason-coded fail flow
Failed visit captures the reason (no-access, equipment-missing, weather), re-queues automatically with the right next-step assignment.
SLA + ETA SMS
Customer gets a confirmation SMS with the window, an "on the way" SMS at dispatch, and a post-install survey link — without ops dispatching anything by hand.
Per-customer job history
Every visit becomes part of the customer record forever: photos, notes, signal levels, who serviced it, what was replaced.
Same data on both ends, in real time.
The dispatcher reassigns a job — the technician's phone updates. The technician completes the install — the dispatcher's board flips a card to "Done". No status calls, no Whatsapp follow-up.
< 1s
Numbers ops actually wants tomorrow.
- 1 JK James Karanjaavg 2h 04m5jobs
- 2 AW Amina Wereavg 2h 12m4jobs
- 3 PO Peter Otienoavg 2h 38m3jobs
Issue your first work order today.
Dispatch board and technician phone app go live the same hour. Techs install the PWA once and it stays on the home screen.