SolutionsSolution 04

Field Service & Parts

Machines earn the invoice once. Service earns for fifteen years — if the technician arrives with the right part.

We build service tools on top of what your workshop already owns: years of work orders and hundreds of pages of documentation per model. Diagnosis support before the drive, the manual answering in seconds at the machine, and parts recommended with odds computed from your own history.

Book a discovery call

Prototype on your service history in 14 days

  • 1 visit, not 2

    First-time fix is the entire economics of field service. The second trip burns the margin of the first — and the customer’s patience with it.

  • 100s of pages

    Documentation per model family. The answer is almost always in there. Nobody has time to find it standing at a dead machine.

  • 30 years

    Of diagnostic pattern in your best mechanic’s head. Today it retires when he does. It doesn’t have to.

Where the money moves

A service call is decided before the van leaves.

By the time the technician is on site, the expensive decisions — who goes, with what parts, prepared for which fault — have already been made. Usually on a two-line ticket.

  1. Ticket“It won’t lift”Two lines from a stressed operator
  2. TriageRemote checksSix questions rule out the trivial before anyone drives
  3. PrepVan packedParts with the best odds, by history for this model and hours
  4. On siteDocs at handTorque value, diagram, error code — answered in seconds, page cited
  5. CloseFixed, first visitReport dictated, parts logged — the history gets smarter

The deliverable

Two modes. Checks first, parts second.

A vague ticket gets Mode A: a short list of things to check and report — the cheap, frequent causes first. No database, no guessing, no wasted drive.

With answers in hand, Mode B names the likely fault and the parts that resolved similar cases — with the odds and the sample size shown, computed from your closed work orders. The model explains; it is not allowed to invent percentages.

Split by cost of being wrong

Cheap-to-carry parts ride along on moderate odds. Expensive or heavy items wait for confirmation. The van is packed by expected cost, not by superstition.

Honest about thin evidence

Rare model, unusual symptom, small sample — the system says so and widens the checklist instead of faking confidence.

Diagnosis assistant · job #7314Mode B · history-backed

Technician · voice note

2.5-tonne diesel, about 4,200 hours. Lifts empty, stalls under load. Drive fine, no error code. Oil level OK, pump doesn’t whine.

System · from 48 similar cases

Pattern points to relief valve or pump wear. Take to the van:

  • Relief valve + seal kit62% · low risk
  • Hydraulic filter set34% · carry anyway
  • Main pump (order only if valve test fails)18% · confirm first

Confirm on site: pressure at the test port under load — manual p. 214, section 6.3.

Illustrative exchange. Percentages are counted from closed work orders for this model and hour range — with the sample size always visible.

Applied AI

Six places AI changes service economics.

  1. 01

    Documentation that answers, with the page cited

    Retrieval

    “Torque for the mast tilt cylinder bolts?” — answered in seconds from the right manual, with the page reference, even when the source PDF is in German or Chinese. The citation matters: the technician verifies, not trusts.

  2. 02

    Parts before the drive

    History

    The two-mode diagnosis above, run from the dispatcher’s desk at triage. Its output is a packing list — the difference between one visit and two, decided while the van is still in the yard.

  3. 03

    Reports from voice notes

    Capture

    The technician dictates ninety seconds in the van; the system drafts the structured work order — symptom, cause, parts used, hours. Paperwork stops eating evenings, and the case base the odds are computed from grows with every job instead of decaying.

  4. 04

    Warranty claims that don’t expire in a drawer

    Drafting

    A warranty-eligible repair is recognized at closing, drafted in the manufacturer’s claim format from the work order, and tracked to its deadline. Recovered warranty money is the quietest profit line in a service department.

  5. 05

    Statutory inspections, watched

    Calendar

    Every machine you service carries inspection deadlines (UDT in Poland) and maintenance intervals. The system watches all of them, bundles what is due in the same region into one route — and turns compliance into planned, recurring revenue.

  6. 06

    The retiring expert, kept on payroll

    Knowledge

    Your senior diagnostician’s cases, corrections, and rules of thumb accumulate in the same system the juniors ask. His pattern recognition keeps working the vans long after his farewell cake.

Management layer

The service manager’s console.

Diagnosis helps the technician. The rest of the system helps the person responsible for thirty technicians and every SLA they carry.

  • Dispatch with context

    Jobs, skills, geography, and contract priorities on one board — the morning puzzle solved in minutes, not on a whiteboard.

  • Customer kept in the loop

    Automatic status messages — scheduled, en route, repaired — and a clean approval flow for paid repairs before the work, not after the argument.

  • Contracts & SLA visibility

    Which agreements make money, which machines burn hours, where response times are drifting — per customer, per model, per month.

  • Parts stock that follows demand

    Van and branch stock aligned with what the history says actually gets used — fewer dead shelves, fewer “we have it, but in the other city.”

  • First-time-fix, measured

    The one number that summarizes the department, tracked per crew and model family — so improvement is visible, not anecdotal.

  • Your data, your walls

    Service history and licensed manuals stay in your environment, role-gated and audited. Nothing trains public models.

Industrial warehouse with organized parts storage

Engagement

Piloted by one crew. Rolled out on evidence.

  1. Discover01

    Two weeks on your service history

    We take a slice of real work orders and one model family's documentation. You get a working diagnosis-and-parts prototype your service manager can interrogate with real cases.

  2. Design02

    Fit to the workshop, not the other way

    Technician workflow designed with technicians: what they ask, how they dictate, what a useful answer looks like on a phone in the rain. Jargon-free by construction.

  3. Build03

    One crew pilots

    A pilot crew runs the tool on live jobs for a measurement window with explicit criteria — first-time-fix, second visits, time per job. Rollout follows evidence.

  4. Operate04

    The flywheel turns

    Every closed job feeds the same history the diagnosis draws on, so the odds sharpen with use. Retainer covers new model families, manuals, and integrations.

Frequently asked

Questions service managers ask first.

  • Our technicians are mechanics, not computer people. Will they use it?

    It is built for a phone held in one hand: ask by voice, read a short answer, tap to confirm parts. The pilot crew decides the interface details — and in practice the feature that wins mechanics over is not typing the service report at 6 p.m., because the system drafted it from their voice note at the job.

  • Our service history is years of terse work-order notes. Is that usable?

    That is exactly the raw material. AI normalizes model names, groups fault descriptions, and links parts consumed to symptoms — building the case base the probabilities are computed from. Terse is fine; mechanics are consistent in their own shorthand, and the system learns it.

  • Where do the parts percentages come from?

    From arithmetic over your closed jobs, never from a language model's imagination. For a given model, hour range, and symptom class, the system counts which parts actually resolved similar cases and shows the sample size alongside the percentage. Thin evidence is labeled thin — a 62% on 48 cases reads differently than a 62% on 6.

  • Manufacturer documentation is licensed. Can it go into the system?

    It stays inside your environment, access-controlled like the paper originals — the system indexes and cites it for your technicians, which is the use the license anticipates. Nothing is republished, and nothing trains anyone's public model.

  • Does this replace our senior diagnostician?

    It copies his availability, not his judgment. The point is that a second-year technician standing at a machine 200 km away gets the checks and the likely parts your best person would have named — while your best person handles the cases that genuinely need him.

Talk to us

Bring one model’s manual and a month of work orders.