Field service's oldest dispute is one sentence long: "your technician never came." The second oldest: "the work wasn't done properly." xMatix ends both with evidence collected as a by-product of doing the job: geofenced arrival, guided execution, proof you can replay.
Arrival that proves itself
Check-in is geofenced with server-checked gates — radius, working hours, holidays, leave — and background GPS trails run from check-in to check-out, replayable on the map, visible to managers and disclosed to the technician. The disputed visit becomes a look at the trail, not a standoff.
Typed work, not free-text heroics
The job runs on typed activities that land on the right record with no custom development: parts consumption onto job-card lines, time and expense into timesheets, meter readings, safety checklists, proof of delivery, bill-on-site. Guided checklists carry photos and signatures; the job stays live on the phone's lock screen with the timer running.
Offline is the designed-for case
The field app assumes the basement plant room has no signal: the day's jobs, asset histories, checklists and parts data are on the device; every capture writes to a durable local queue and reconciles later through delta sync. Nothing rides on connectivity being polite. (The engineering: offline sync architecture.)
Evidence that compounds
Every completed job enriches the asset's biography — readings, parts, photos, outcomes — which is what makes the next visit smarter, the claim defensible, and first-time-fix a number you can manage per technician and per failure code.
Common questions
How does proof of presence work?
Geofenced check-in with server-side gates, then a background GPS trail from check-in to check-out that can be replayed on the map. Managers see it; technicians know it's collected — symmetric honesty by design.
What can technicians capture on a job?
Typed activities out of the box: parts consumption, time and expense, meter readings, safety and work checklists with photos, customer signatures, bill-on-site — each landing on the correct record automatically.
Does everything work without connectivity?
Yes — offline-first: the day's work and reference data sync down in advance, captures queue durably on the device, and reconcile when the network returns. A dead zone doesn't produce a paper day.
How does field evidence feed billing and claims?
The job card's parts, hours, readings and photos flow directly into the invoice or the warranty claim — the same capture serving execution, billing and dispute-proofing at once.