CEDX 2026 Service Release: Predictive SLA triage, omnichannel queues, and live contract context on one record Explore the CEDX Field architecture ->
CEDXSystems
EnglishTalk to sales
CUSTOMER SERVICE CEDX Field
Overview Jobs Routes Workflow & Tour Operators TCO Model 14-Day Sandbox Live build ↗
CUSTOMER SERVICE CEDX Field · Customer Service · field.cedxsystems.com

Dispatch is a forecast, not a whiteboard.

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.

Open live CEDX Field -> Inspect 4-screen build tour
225 open jobs 45 SLA clocks tight 42 parts stock risks on vans Zero-ETL Shared Postgres Record
CEDX Field Enterprise Architecture Briefing
CEDX Field · 225 open jobs

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation fro..."

Marcus Vance · Chief Revenue Officer · Meridian Systems · 0.01s Canonical Sync
CEDX Field reads and writes the exact same canonical Postgres record as CEDX Field AR, CEDX Remote, and CEDX Inventory with zero third-party webhooks.
🔒 https://field.cedxsystems.com/workspace/live
CEDX Field · Overview (The day, with its exceptions named)
field.cedxsystems.com · 01 Overview · Live Canonical Dataset
● Overview Active · 0.011s Sync Open /app/field ↗
OPEN JOBS
225
of 320 in the day view
SLA CLOCKS TIGHT
45
3 criticals already at 0.0h
PARTS STOCK RISKS ON VANS
42
one stock-out blocking 2 jobs
OVERLOADED TECHS
7
util ≥85 or in overtime
Ticket / Incident ID Customer & ARR Tier Assigned Queue & Pod SLA Breach Clock Root-Cause Context Resolution Score
INC-49201 · API Webhook LagCEDX Field · Record #1040 Meridian Corp · $420K ARR Tier-3 Platform Pod 18m remaining ● Linked to PR #4812 98% Confidence
TCK-88310 · Billing Seat SyncCEDX Field · Record #1041 Harbor Retail · $640K ARR Enterprise Billing Ops 1h 42m remaining ● Auto-Resolved via Books 100% Verified
INC-49209 · SSO SAML RotationCEDX Field · Record #1042 Atlas Logistics · $285K ARR Identity & Access Queue 44m remaining ● Cert Runbook Attached 95% Confidence
TCK-88344 · Field Dispatch RMACEDX Field · Record #1043 Cedar Foods · $310K ARR Field Service Dispatch 3h 15m remaining ● Parts Reserved in WMS 94% Confidence
✦ CEDX Field Copilot · INC-49201 · API Webhook Lag
Overview Verified
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%.
CEDX Field operator workspace in natural daylight
FIELD DOCUMENTARY · CUSTOMER SERVICE

320 jobs, each with a fix-risk score

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.

CAMERA: CANON EOS R5 · 35MM F/1.4 · NATURAL DAYLIGHT ESTATE ROUTE: /APP/FIELD
CORE CAPABILITIES · CEDX FIELD

Three architectural jobs CEDX Field gets right on one record.

Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.

01 · CUSTOMER SERVICE FOUNDATION

320 jobs, each with a fix-risk score

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 to 99. Yesterday's fixes are today's riskiest work.

✓ FTF risk and SLA-left on every rowVerified
✓ Callback, repair and install as job typesVerified
✓ Six states, scheduled through cancelledVerified
02 · LIVE EXECUTION

60 routes with load scores and drive time

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.

60 routes with load scores and drive time
CEDX Field Live Telemetry ● 225 open jobs
03 · DETERMINISTIC GOVERNANCE

28 technicians, two kinds of busy

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.

✓ Util % and travel % as separate columnsActive
✓ OT risk ≠ utilization. The table proves itActive
✓ Available through OT as status chipsActive
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Field build looks like when you open /app/field.

Every figure below is directly inspectable in the running CEDX Field application workspace with zero synthetic projections.

OPEN JOBS
225
of 320 in the day view
SLA CLOCKS TIGHT
45
3 criticals already at 0.0h
PARTS STOCK RISKS ON VANS
42
one stock-out blocking 2 jobs
OVERLOADED TECHS
7
util ≥85 or in overtime
4-SCREEN RUNNING BUILD TOUR

Four screens captured from field.cedxsystems.com, in the order operators run them.

Click any screen below to inspect how CEDX Field moves from initial intake to verified cross-estate completion.

01 OVERVIEW
The day, with its exceptions named
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
The work, riskiest first
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
The day as driven, not as drawn
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
Capacity you can argue with
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.
01 OVERVIEW · FIELD.CEDXSYSTEMS.COM

The day, with its exceptions named

● Live Screen Capture

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%.

✓ Three critical jobs already at 0.0h of SLAVerified in /app/field
✓ A tech at 52% utilization flagged “pull capacity”Verified in /app/field
✓ Job status: 59 en route · 56 held · 42 doneVerified in /app/field
The day, with its exceptions named
OPERATING CADENCE · CUSTOMER SERVICE

How CEDX Field runs across the week, in the exact order work happens.

Every support agent sees the customer ARR, overdue invoices, active renewal date, and linked engineering sprint issue without switching tabs.

STAGE 01

Capture & Ingest

Records land in CEDX Field already linked to the canonical customer, employee, or vendor ID.

STAGE 02

Score & Triage

Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.

STAGE 03

Execute & Approve

Operators resolve work in one click with role-based guardrails and instant cross-app writeback.

STAGE 04

Reconcile & Report

Every completed action updates live executive dashboards and the immutable audit log automatically.

OPERATOR WORKSPACES · WHO RUNS CEDX FIELD

Three roles open CEDX Field every day. Each sees the exact surface they own.

Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.

Field technician using CEDX Field

Field technician

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 day
Dispatcher using CEDX Field

Dispatcher

Owns the 63 dispatch score: 225 open, 45 clocks tight, 7 overloaded, and keeps the board honest when the day goes sideways.

● open · 225
Service operations lead using CEDX Field

Service operations lead

Watches first-time fix and the callback catalog. Sixty typed callbacks do not argue back.

● FTF · 78.6%
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

Support Queues That Read the Live Revenue & Engineering Graph

CEDX Field is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.

CONNECTED MODULE 01 Open /field-ar/ ->

CEDX Field AR

The job is done; the cash is not. Field AR picks up at completion: 49 completed jobs sit unbilled in its demo ledger.
CONNECTED MODULE 02 Open /remote/ ->

CEDX Remote

Some truck rolls are avoidable. Remote sessions fix the ones that never needed a van, with the tape running.
CONNECTED MODULE 03 Open /inventory/ ->

CEDX Inventory

Van stock is inventory on wheels. Inventory tracks the shelves the vans restock from.
CONNECTED MODULE 04 Open /copilot/ ->

CEDX Copilot

Ask AI (⌘J) sits on every Field screen, versioned and traced by the Copilot console behind it.
ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Field.

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."

Marcus Vance
Marcus Vance
Chief Revenue Officer · Meridian Systems

"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."

Elena Rostova
Elena Rostova
Chief Financial Officer · Northline Group

"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production data with zero synthetic clutter."

David Okafor
David Okafor
VP of Enterprise Systems · Harbor Holdings
LIVE TCO & CONSOLIDATION MODEL · CUSTOMER SERVICE

Stop paying five vendors to re-sync the same customer service record.

Drag the seat slider to compare your current stitched stack (ServiceNow CSM + Zendesk Enterprise + Intercom + PagerDuty) against running CEDX Field natively on the unified CEDX estate.

Organization Seats 250 seats
25 seats 500 seats 1,250 seats 2,500 seats
Legacy Stitched Stack
ServiceNow CSM + Zendesk Enterprise + Intercom + PagerDuty
$1,380,000 / yr
CEDX Field + Full Estate Bundle
All 132 applications · Canonical Postgres · Unlimited Copilot
$267,000 / yr
Verified Annual Hard Savings
Plus 0 middleware sync failures
$1,113,000 / yr
TECHNICAL & PROCUREMENT FAQ · CEDX FIELD

Questions operators and architecture teams ask before piloting CEDX Field.

01 Is the software on this page real? +
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.
02 What is FTF risk? +
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.
03 Why do callbacks top the risk list? +
Because the data says they should: the first fourteen rows of the risk sort are all callback jobs at 95 to 99. A return visit carries the original fault's uncertainty plus the customer's patience spent.
04 What does the overtime-risk column read? +
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.
05 Is Field audited or certified? +
No certification has been issued. What we can evidence about hosting, encryption and access is on the security page .
LIVE SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

CEDX Field is running right now. Open it and inspect the record.

Explore the live CEDX Field workspace on canonical demo data at /app/field, or book a 30-minute architecture session to map your first entity rollout.

Open live CEDX Field (/app/field) -> Book an estate architecture map