Work orders, dispatch and technicians on the same records as your stock
Most field service tools sit beside your inventory and your customer list, and you pay in integrations. Here the job, the parts it consumes, the customer it belongs to and the invoice it produces are one record set.
A dispatch board that reflects the day
Jobs are raised, scheduled and tracked from one board, so the state of the day is visible without a phone round.
- Board, job list and per-job detail — raise a job, schedule it and move it through its states
- Schedule a job with a start time, job type and the van it runs from
- A My Day view for the technician, built for a phone in a van rather than a desk
The parts a job consumes come from your stock
This is the part that is normally an integration project. Jobs draw on the same item records as inventory — including lot and serial tracked parts — so what left the van is what left the warehouse.
- One item catalogue behind inventory, purchasing and jobs
- Lot and serial tracking carries through to the parts fitted on site
- No sync job, no nightly export, no second source of truth to reconcile
Job costing that admits what it does not know
A job's cost is materials plus labour. Where a figure is estimated rather than captured, the screen says so instead of presenting it as fact.
- Materials and labour rolled up per job
- Estimated figures are marked as estimated, and say they will not tie back to the ledger
- Revenue, cost and margin by customer, job, item or cost centre through the profitability report
Return visits, so first-time fix means something
A revisit can be linked to the job it repeats, with a reason. Without that link a first-time-fix rate reads a flat 100% forever — technically true and useless.
- Book a return visit from the completed job it belongs to
- A required reason, so "unrecorded" is never mistaken for "not rework"
- The link can be corrected or cleared afterwards, because rework is usually known later
Common questions
Is route optimisation included?
No — it is a separate module you can add. Routes themselves are part of dispatch; optimising them is an add-on, and we would rather say so than let you find out after signing.
Do I have to take the whole platform to use field service?
No. Modules are subscribed to individually, and you pay per person for each app you turn on. Field service is most valuable next to inventory, because that is where the parts live, but it does not require it.
Can it handle work that is not a customer visit — internal maintenance, for example?
Property maintenance work orders are handled by our property module rather than field service. If your work is internal maintenance across sites, tell us on a call and we will point you at the right one rather than sell you this.
What if our dispatch process does not look like this?
That is the normal case, and it is the reason we exist. Start on the commercial product and tell us what should be different, or bring your requirements and we build to them — either way you are not starting from a blank page.
See it against your own jobs
Bring a week of real work orders to a call and we will walk it through the product rather than a slide.