MIKE NANTO
Case file 02 · full record · Field-service entitlement engine

Manual triage,
made code.
Seconds, not hours.

A field-service company received warranty jobs all day, and every one sat in a queue until a person read it, looked up the warranty, and made a judgment call. Here is the full story of writing that judgment down as rules and letting software make the call in seconds.

6warranty payors, one system: two major manufacturers and four third-party administrators, all handled the same way
secsfrom claim arriving to dispatch-ready, a step that used to wait hours for a person
100operations that actually work, distilled from two contradictory 500+-entry vendor references
0passwords sitting in files: every credential is locked in a secure vault
§1 · The situation

A queue that only moved as fast as a person could read

Warranty jobs arrived from six different payors: manufacturers and administrators, each with its own portal, its own codes, its own quirks. Every job waited for a person to open it, look up the warranty status in the payor's system, decode what the flags meant, and decide how to route and bill it. The knowledge lived in a few experienced heads. And the field-service platform itself (the foundation any automation would have to be built on) came with no reliable manual: the two references the vendor supplied contradicted each other.

The mandate: take the judgment call the experts were making by hand, write it down as rules, and let software make it the same way, every time, the moment a job lands.

§2 · What was done

The judgment call, written down and wired live

  • Every inbound job now advances to dispatch-ready without a human in the loop. Software matches each job to its payor, pulls the warranty details straight from the payor's own system, applies the written-down rules, and moves it forward.
  • One system now talks to all six payors, connecting straight into the manufacturers' and administrators' own systems, instead of six separate manual lookups.
  • The expert knowledge can no longer walk out the door: tribal know-how was codified as rules, covering brand identified from model-number prefixes, warranty status decoded from cryptic vendor flags, billing rules hidden inside authorization codes.
  • The automation stands on solid ground because two contradictory 500+-entry vendor references were untangled into one verified manual of roughly 100 operations that actually work, each tested against the live system.
  • Decisions land in seconds instead of hours. Instead of checking for new work on a timer, the system reacts the moment a job arrives, running on cloud services that only run (and only cost money) when there's work to do.
  • Go-live carried no leap of faith: a side-by-side trial run ran the new system next to the old process and compared every decision, line by line, before it was trusted with real dispatches.
  • Every run is defensible: the system rehearses before it acts, double-checks that every change it made actually took, and keeps a full log of every run. Every credential stays locked in a secure vault, so nothing sensitive ever sits in a file.

The result in one line: the entitlement decision is now automated, consistent, logged, and seconds behind the event instead of hours behind a queue.

§3 · What the client gained

In plain terms

Cost

Triage hours given back

The lookup-and-decide work that consumed skilled staff all day is done by software. Those hours now go to customers and exceptions, not routine reading.

Speed

Seconds, not hours

A job that once waited in a queue for a person is dispatch-ready moments after it arrives. Faster triage means technicians scheduled sooner and customers served sooner.

Visibility

Every decision on the record

Each run leaves a full log: what came in, what the rules decided, what was sent back and double-checked. No more reconstructing a judgment call from memory.

Security

Zero secrets on disk

Every payor credential lives in a locked vault, never in a file. The system rehearses before it acts and double-checks its own work, so it can't silently do the wrong thing at scale.

Growth

Adding payor number seven is routine

Adding a payor used to mean training people on another portal. Now it means plugging one more into a system that already knows the job.

Continuity

Knowledge that can't retire

The rules the veterans carried in their heads are written down, versioned, and tested. The business no longer depends on who happens to be at a desk, or still employed.

§4 · A note on names

This client, like every client here, is not named: confidentiality is part of what they pay for. Every figure comes from the engagement's own records, and a reference who'll take your call is available on request.

Is a judgment call your bottleneck?

Thirty minutes is enough for me to tell you honestly whether the decision your team makes by hand all day can be made by code, and roughly what it would take.