Dispatch a job and know it landed
Callouts, installations, maintenance visits and site surveys all have the same problem: the person doing the work is somewhere else. TaskIt replaces the check-in call with an acceptance timestamp, a progress figure and a reason when something is stuck.
Works in a phone browser, on the van’s device.
What usually goes wrong
Written from how this kind of business actually runs, not from a generic template.
How it goes today
Dispatch is a phone call, and then another one
One call to send the job, one to check it was received, one to ask how it is going. That is the coordinator’s whole day, and none of it is recorded.
Site details arrive incomplete
The technician gets there and the access code is wrong, the equipment is a different model, or nobody is on site. The information existed; it just was not captured at intake.
A job stalls and nobody upstream knows
A missing part turns a two-hour visit into a return trip. If that is only in the technician’s head until the evening, the second visit is already a day later than it needed to be.
Two technicians dispatched to the same job
A message to the team is claimed by whoever answers first — twice, because a chat message cannot be claimed exclusively.
Proof of what happened on site
When a customer disputes what was done, the only evidence is a technician’s recollection and possibly a photo on a personal phone.
With TaskIt
Job intake as a real form
Capture site, contact, access notes, equipment, fault description and a photo as typed fields. The person who goes out reads them instead of phoning to ask.
Dispatch to a queue, claimed exclusively
Raise the job for the field department. Everyone eligible is notified, and the accept is a single conditional write — so two technicians cannot both take it, however close together they tap.
The notification reaches the phone
Pair your own WhatsApp number and send the job to the technician, the team group, or both — with the code, title, priority and your captured fields in the message.
Stuck on site? Record it there and then
Unable to Complete with a reason such as material not available or waiting for customer moves the job to Blocked and puts it on the coordinator’s queue immediately, not at 18:00.
Return visits keep the first visit’s findings
A handover records what was diagnosed, what was done and what is outstanding on the same job — so whoever goes back does not start from scratch.
Evidence attached to the job
Photos and documents uploaded to the task are authenticated on upload and download, validated by type and never publicly served — a link alone is not access.
A callout, from phone ringing to closed
Eight technicians, one coordinator, no check-in calls.
- 1
09:05 — logged
The coordinator raises the callout on the service form: site, contact, access notes, equipment, reported fault.
- 2
09:06 — dispatched
Raised for the field department. Every technician gets it on WhatsApp with the site and equipment in the message.
- 3
09:11 — claimed
The nearest technician accepts. The claim locks the job; the others see it is taken and carry on.
- 4
11:20 — blocked
Wrong part in the van. Unable to Complete with "material not available". The coordinator sees it immediately and orders the part before lunch.
- 5
14:40 — handed back out
A second technician takes it with the diagnosis already recorded — no re-diagnosis on site.
- 6
16:15 — closed
Submitted with photos, reviewed and approved by the coordinator who raised it.
The result
The part was ordered three hours earlier than it would have been, and the return visit was informed rather than exploratory.
The result
No percentages, because nothing here has measured yours — these are the changes the mechanism produces.
Fewer coordination calls per job
Acceptance, progress and blocked reasons answer the questions the calls were for, without interrupting someone mid-job.
Faster response to blocked work
A part ordered at 11:20 rather than at 18:00 is often the difference between a same-week and a next-week return visit.
No duplicate dispatch
The exclusive claim removes an entire class of wasted journeys.
Defensible records for customer disputes
Timestamps, photos, blocked reasons and handover notes reconstruct a visit nobody in the office witnessed.
Frequently asked questions
No. There is no map, no route optimisation, no location tracking and no drag-and-drop dispatch board. Jobs are raised as tasks and either assigned to a person or offered to a department queue that technicians claim from.
Yes. It runs in a phone browser with nothing to install, and the notifications arrive over your own WhatsApp number so the job reaches an app they already have open.
Photos and documents can be attached to the task, and the activity timeline records accepts, progress updates, comments, handovers and reviews with timestamps. Uploads are authenticated in both directions and are never publicly served.
Use a handover. The job keeps its ID and the second technician reads what was already diagnosed, what was completed and what is outstanding rather than repeating the first visit.
Where to go next
The capabilities behind this page, and the neighbouring situations they also cover.
The features behind it
All featuresDispatch a week of jobs through it
Build one service intake form, put your callouts through a department queue, and count the calls you did not make.