Field Service lifecycle architecture.
Plan
Beat plans written from territory & visit frequency
Dispatch
The day's journey assigned to a rep, stop by stop
Travel
Route followed on the road, GPS trail recorded live
Execute
Check-in, activities & the order captured at the outlet
Prove
Photos, signature & geofence stand behind the visit
Close
Day reconciles & syncs — nothing left in a notebook
The field, run like an operation.
Optimization on real roads, not straight lines
Multi-vehicle route optimization with shift windows, service times and workload balance over road-network travel times; beats generate visit plans automatically on schedule.
Map, Gantt, Board — same backlog
Live positions and travelled paths on the map; drag-to-schedule with “Optimize day” on the Gantt; drag-to-assign on the board. Jobs, cases, visits — one console.
The trail is the timesheet
Geofenced check-in with server-checked gates (radius, hours, holidays, leave), background GPS trails from check-in to check-out, manager replay on the map — disclosed to the tech, visible to the manager.
The dispatch board is a map.
One day. Three ways to run it.
The allocation console shows the same day three ways. A map with live resource positions, travelled paths and unassigned work in geographic context. A timeline of intraday lanes where dropping a job schedules it — and an Optimize day action fills the unassigned backlog into free slots. A board with an unassigned rail and a column per resource, drag to assign. Scope it to a branch, a partner, a resource group or the whole operation — and allocate any entity: visit plans, cases, service orders.
Work routes by queue, required skill, capacity and presence, with accept, decline, transfer and reassign as first-class operations and a supervisor snapshot of queue backlog and per-resource load. Scheduling covers more than people: demo vehicles, service bays and equipment are bookable resources with appointment types, slot templates, eligible-and-free search, and holds that expire.
Optimize day fills unassigned work — it does not rearrange assignments a person has already made.
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Field Service |
|---|---|
| Map, Gantt and board dispatch | Native |
| One-click day optimisation over real roads | Native |
| Skills-based assignment | Native |
| Structured work catalog, thirteen visit types | Native |
| Geofenced, selfie-verified attendance | Native |
| Background GPS trails, captured offline | Native |
| Appointment slots with real capacity | Native |
| Full visit execution without connectivity | Offline |
| Proof of delivery — photos and signatures | Native |
| Capability | xMatix Field Service |
|---|---|
| Billing on site | Native |
| Map / timeline / board dispatch | Native |
| Optimize day (fill unassigned) | Native |
| Skills-based routing | Native |
| Capacity and presence routing | Native |
| Appointment slots and holds | Native |
| Bookable equipment and facilities | Native |
| Offline job execution | Offline |
Everything in Field Service.
Map/Gantt/board dispatch
The whole field on one screen.
Live technician positions, travelled paths and unassigned jobs, viewed as map, timeline or board — dispatch by dragging.
"Optimize day" scheduling
One click untangles the day.
The scheduler re-sequences the day's jobs over real roads with one button. The planner approves; the math obeys.
Road-network routing
Travel time from real roads, not straight lines.
Routes compute over the actual road network, across vehicles — arrival promises you can keep.
Learned route sequences
The route that actually works, remembered.
Planned, optimized and actually-driven sequences are kept and versioned — the system learns the way your best techs already go.
13-type work catalog
Every kind of field work, structured.
Installations to inspections, each visit type carries its own steps — parts flow to the job card, hours to the timesheet.
Geofenced attendance gates
On site means on site.
Check-in passes five server-checked gates, selfie included. Time on site becomes a fact, not a claim.
Background GPS trails
When a customer disputes the visit, replay it.
The route a technician actually drove, check-in to check-out, on a map — captured even offline, disclosed to the tech, and there when you need to prove the work happened.
Appointments & slot capacity
Promise a window you can keep.
Bookings draw from real slot capacity with holds — the calendar can't overpromise what the team can't deliver.
Skills-based assignment
The right tech, first time.
Work routes by skill, capacity and who's actually available — fewer repeat visits, faster closes.
Offline execution & outbox
The job doesn't care about the signal.
Techs work the visit fully offline — photos included — and everything syncs safely when coverage returns.
Lock-screen session timer
The running job, on the lock screen.
A live timer sits on the phone's lock screen from check-in to check-out — the tech always knows the clock is honest.
Proof of delivery
Proof captured at the doorstep.
Signatures and photos attach at the moment of completion — the dispute that never starts.
Bill on site
Invoice before the van door closes.
The tech raises the invoice at the customer's door — work done, billed, and collected in the same visit.
The questions evaluators ask.
Where the work happens. xMatix Service runs work that comes to you — check-in inspections, job cards, bays, warranty and AMCs at your own locations. xMatix Field Service dispatches work to the customer's site — scheduling, road-network routing, geofenced attendance and on-site proof of work. Both run on the same job card and the same data model, so a case can move between the workshop and the field without being retyped. Explore xMatix Service.
Yes — technicians execute the whole visit fully offline, photos included. Work captured with no coverage queues in a durable outbox and syncs safely when the signal returns, even if the phone restarts first. Geofenced check-in, the activity steps, proof-of-delivery signatures and on-site invoicing all run from the device — the job does not care about the signal, and nothing is lost or retyped.
From one live screen. Dispatchers see technician positions, travelled paths and unassigned jobs as a map, a Gantt timeline or a board, and assign by dragging. "Optimize day" re-sequences a technician's jobs over real roads with one click — the planner approves, the math obeys. Work routes by skill, capacity and actual availability, and appointment bookings draw from real slot capacity so the calendar cannot overpromise.
Yes, end to end. Claims raise from the job card with the evidence attached, validate against each principal's configured warranty terms before submission, and then track through approval to settlement — so recoverable money stops dying in a drawer. Settlements reconcile to claim lines individually, which means the short-paid line shows itself instead of hiding in a lump sum.
Yes — several layers of it. Check-in passes server-checked geofence gates, selfie included, so time on site is a fact rather than a claim. Photos and checklists capture condition on arrival, signatures and photos attach at the moment of completion, and background GPS trails record the route actually driven — captured even offline and replayable on a map when a customer disputes the visit.
Yes. Case-level SLAs run in xMatix Support on the same data model: response and resolution targets track milestone by milestone, against business-hours clocks, with automatic escalation before the breach rather than a report after it. On the scheduling side, appointment bookings draw from real slot capacity — the promise made to the customer is one the team can physically keep.
Three ways, all off the same records. Condition-based rules auto-stamp an owning resource on matching records as they arrive. Routed work finds people by queue, required skill, capacity and presence — with accept, decline, transfer and reassign as first-class operations. And a dispatcher can assign by hand on the map, the timeline or the board, where dropping a job schedules it. A supervisor snapshot shows queue backlog with per-resource presence and load, so overloading is visible before it happens.
Yes — bookable resources cover people, physical assets and facilities: a demo vehicle and a service bay are scheduled the same way a technician is. Appointment types and slot templates define what can be booked and when; an eligible-and-free search finds resources that both qualify and have the slot; and holds reserve a slot with an expiry while the booking wizard runs on web and mobile, and every resource keeps its own availability calendar.
The console is built for it. The map shows live positions and unassigned work in geographic context; the timeline lets a dispatcher drag work between lanes; the board moves jobs between resources in one gesture. Optimize day fills the unassigned backlog into free slots — deliberately leaving assignments a person has already made untouched, so a dispatcher's judgment is never silently overridden. Field execution keeps working offline and syncs when coverage returns.
By assuming the network is optional. Check-in and check-out carry geo-stamps regardless of signal, background route trails record with zero connectivity and are disclosed to the technician, and the console shows live positions whenever coverage exists — with the full travelled path replayable on a map afterwards. Tracking that only works online loses exactly the rural runs where it matters most.
Yes — offline is the default, not a fallback. Every screen reads from a local store first, so the day's jobs, checklists, asset history and parts open with no signal. Photos, signatures and readings queue in a durable outbox and sync when coverage returns. An engineer can work a full basement or rural site day and lose nothing.
Yes — bookable resources cover people, physical assets and facilities: a demo vehicle and a service bay are scheduled the same way a technician is. Appointment types and slot templates define what can be booked and when; an eligible-and-free search finds resources that both qualify and have the slot; and holds reserve a slot with an expiry while the booking completes. The booking wizard runs on web and mobile, and every resource has an availability calendar.
