The whole day, from the first job to the proof it was done
One object moves from booked to dispatched to on site to complete to paid. The office sees it, the technician sees it, the customer sees a window, and the proof is attached before anyone leaves.
What the field operation gets
The point is that the office and the truck are looking at the same thing at the same time.
-
Jobs with a real record
Customer, service, technician, time window, price, duration, notes, photos and signature on one object.
-
A dispatch map
Today's work and every technician's last known position on one map, so a late job is visible before it becomes a call.
-
Day routes that make sense
Sequence a technician's stops, with the total distance stated and the option to re-optimise before the day starts.
-
Proof of work
Photo, signature, timestamp and location captured at the job, attached to the record and available to the customer.
-
Technicians as real people
Skills, home base, schedule and availability, so work is assigned to someone who can actually do it.
-
Check in and out
A technician checks in when they arrive and out when they leave, which is what makes the mileage and the time on site real numbers.
The job lifecycle, and what is enforced at each step
Status is not a label someone types. It is a state the platform checks, and a transition that is not allowed is refused with the ones that are.
A technician view built for one hand and bad signal
The field view runs in the phone's browser and installs to the home screen. It is designed for a technician standing in a crawlspace, not for someone at a desk.
Today's jobs, in order, with the address and the customer's notes. One button to check in, one to check out, one to attach a photo, one to take a signature. The next job is one tap away and the driving directions open in the phone's own maps.
Status changes made without a signal are queued and applied in order when the connection returns, so a technician in a basement does not lose the arrival time or the completion.
Nothing on the screen needs two hands, and nothing needs reading at arm's length in the sun. That is the whole design brief for this view.
-
The day, in order
Stops sequenced, addresses and customer notes attached, and the next stop one tap away.
-
Capture from the phone
Photos and signatures taken on the device and attached to the job rather than texted to the office.
-
Location, when it helps
Check in and check out report a position, which makes arrival times and distance travelled real rather than reconstructed.
-
Offline that recovers
Changes made with no signal are held and applied in order, so the record stays correct even from a basement.
Why the routing numbers say straight line
Route sequencing measures straight line distance between stops, and the interface says so. That is not a limitation to be embarrassed about, it is a decision about honesty: a dispatcher who catches a system claiming road accuracy it does not have stops trusting every other number it produces.
Straight line ordering gets a day of eight to fifteen stops very close to the right sequence, which is the part that saves the fuel. Where road distance genuinely changes the answer, the platform supports a road based routing engine as a configuration rather than pretending.
The same rule applies to arrival estimates. An estimate is labelled as an estimate, and the platform would rather show a range it can stand behind than a precise time it cannot.
A job is not finished when the work is done. It is finished when the record, the proof and the invoice agree.
Field operations by plan
| Free | Starter | Growth | Scale and above | |
|---|---|---|---|---|
| Jobs and customers | 20 customers | 250 customers | 1,000 customers | 5,000 and above |
| Technicians | 1 | 3 | 10 | 25 and above |
| Dispatch map | Not included | Basic | Yes | Yes |
| Day route sequencing | Not included | Not included | Yes | Yes |
| Proof of work | Not included | Not included | Yes | Yes |
| Technician mobile view | Yes | Yes | Yes | Yes |
| Service agreements | Not included | Yes | Yes | Yes |
Questions people ask before signing up
Can I assign the same technician to two jobs at once?
The platform will let you if you force it, but it will tell you first. Booking is checked against the capacity rules you set at the office, the area and the individual level, and an override is recorded so it is visible later rather than invisible forever.
Does the technician need a company phone?
No. The field view is a web page that installs to the home screen of whatever phone the technician carries, including a personal one. Nothing needs to be installed from an app store.
How does the platform handle a job that runs long?
The remaining stops for that day can be re-sequenced, and the affected customers can be notified with a new window. Because the customer's window comes from the same record the dispatcher is moving, there is no second list to keep in step.
Is there a paper option?
A completed job can be printed or exported with its photos, signature and notes, which is what most companies need when a customer or an insurer asks for documentation.
Can customers see where the technician is?
Yes, on the plans that include tracking. The customer receives a link that shows their own job and nothing else, and the link expires when the job is done.
Start on the free plan
Twenty customers, one location, every core module, free permanently. Move up when the work outgrows it.