CEDX Field · Customer Service
Field scores the day before it happens: every job carries a first-time-fix risk, every route carries a load score and drive minutes, and every technician carries utilization and overtime risk as two different numbers.
The technicians table settles an argument every dispatch board has: one tech at 48% utilization carries an overtime risk of 91 — because travel is 45% of his day. Busy and overloaded are not the same column.
Runs on demo data. Technicians, vans and sites in the captures are the demo region's rows.
What it is
The jobs table carries type, priority, status, technician, FTF risk and SLA-left on every row. The top of the risk sort is instructive: the first fourteen rows are all callbacks, sitting at 95–99 — yesterday's fixes are today's riskiest work.
Routes show zone, stops, drive minutes, load and status. The heavy ones — load ≥85 — are counted at 11; the delayed ones show why: six stops and 140 minutes of drive on a 97 load is a day that was never going to fit.
Utilization and travel are separate columns, so the overtime-risk column can be honest: 59% average utilization with 32% of the day in vans, 7 overloaded at util ≥85 or in OT — and 12 with room to pull capacity from.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/field.
01 — Overview
Dispatch health reads 63: 225 open, 45 clocks tight, 7 overloaded. The alerts carry causes — a callback at FTF risk 86 with skill match 55% and two parts missing; a van stock-out blocking two open jobs; a critical SLA under one hour with skill match 70%.
02 — Jobs
Three hundred twenty jobs with 225 open, 116 at high FTF risk and 42 inside two hours of SLA. Sorting by risk puts callbacks on top — the repair that failed yesterday is the row most likely to fail today.
03 — Routes
Sixty routes with dates, technicians, zones, stops, drive minutes and load. Two delayed routes sit at loads of 97 and 95 — the difference between a plan and a wish is printed in the load column.
04 — Technicians
Twenty-eight technicians with status, zone, utilization, travel, today's jobs, open jobs and OT risk. The travel column reframes the roster: a tech at 48% utilization and 45% travel is not idle — he is driving.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Lives in the route: stops, drive time, van stock. The 32% travel column is his day, and the parts bins in the photograph are why stock-outs block jobs.
travel · 32% of dayOwns the 63 dispatch score: 225 open, 45 clocks tight, 7 overloaded — and keeps the board honest when the day goes sideways.
open · 225Watches first-time fix and the callback catalog. Sixty typed callbacks do not argue back.
FTF · 78.6%The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Jobs arrive typed — callback, repair, install — with SLA clocks already running; 42 have under two hours left.
Van stock is part of dispatch: one missing IR module on one van is blocking two open jobs today, and the alert says which van.
The day becomes 60 routes with drive minutes and load scores; 11 run heavy at ≥85 and two are already delayed.
First-time fix is the scoreboard — 78.6% trailing 60 days — and every return visit is typed as a callback, so the list leads tomorrow's risk sort.
One record
Dispatch touches money, machines and the queue. The estate keeps those in one place — same day, same Ask AI button.
The job is done; the cash is not. Field AR picks up at completion — 49 completed jobs sit unbilled in its demo ledger.
CEDX RemoteSome truck rolls are avoidable. Remote sessions fix the ones that never needed a van — with the tape running.
CEDX InventoryVan stock is inventory on wheels. Inventory tracks the shelves the vans restock from.
CEDX CopilotAsk AI — ⌘J — sits on every Field screen, versioned and traced by the Copilot console behind it.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your jobs, your zones
Field with the rest of it
Questions
Yes. Every screenshot is a capture of the running build, open at /app/field. It runs on demo data — the region on the chrome is the demo tenant’s.
A first-time-fix probability per open job, 116 of them currently at ≥55. The alerts show the inputs: skill match percentage, parts missing, callback history. The riskiest rows are typed callbacks — work that already failed once.
Because the data says they should: the first fourteen rows of the risk sort are all callback jobs at 95–99. A return visit carries the original fault's uncertainty plus the customer's patience spent.
Not utilization. The technicians table shows a tech at 48% utilization with OT risk 91 because travel is 45% of his day — busy and overloaded are separate columns on purpose.
No certification has been issued. What we can evidence about hosting, encryption and access is on the security page.
Live build, demo data, no card. Then count your callbacks — they are already at the top of the list.