The New Benchmark: Zero-Touch Exception Resolution

For most of the past decade, healthcare logistics performance has been measured primarily through on-time delivery rate (OTD). It is a useful metric. It is also a lagging indicator that tells you what happened, not how efficiently your team handled what happened.

OTD obscures the hidden cost of exception management. A shipment that was technically on time may have required two hours of coordinator time, three calls to the courier, and a documented deviation, none of which appear in an OTD report. Two operations teams can post identical OTD rates with radically different operational costs, service consistency, and compliance risk profiles.

The metric that separates dashboards from operating systems

The zero-touch exception resolution rate is the percentage of shipment exceptions that are identified, actioned, resolved, and documented without any human intervention. In first-generation platforms this number was meaningless: the platform could not resolve exceptions, so every exception required human action by definition. Teams optimized for response time instead, i.e. how fast a coordinator noticed the alert.

AI-native platforms change the denominator. Even the most sophisticated pre-AI operations, including Uber Freight's platform where zero-touch rate on routine exceptions was a primary KPI, hit a ceiling of roughly 10 to 15% on complex exception categories. Voice AI that can conduct live conversations with courier operations lines, interpret responses, and take follow-on action has changed what is achievable. Early results in pharmaceutical logistics suggest zero-touch rates of 50% or higher for the most common exception types: incorrect addresses, pickup confirmations, delay notifications, temperature excursion documentation, and carrier escalations for overdue deliveries.

Four metrics that complete the picture

1. Zero-touch exception resolution rate: Of the exceptions your team handles monthly, what percentage is resolved without any human action? If a vendor cannot give you a zero-touch rate by exception type, the AI layer is likely cosmetic.

2. Time-to-resolution by exception type: For exceptions that need human intervention, how long from alert to close? This exposes where the bottlenecks actually live: carrier communication, QA documentation, or recipient coordination.

3. Coordinator hours per exception: When looking at hours spent per exception fully loaded, what was the time spent on response, communications, analysis, documentation, and follow up. Most teams cannot say, because the work is scattered across email, phone, and spreadsheets. If you cannot measure cost per exception, you cannot tell whether a platform is improving it.

4. Chain-of-custody completeness rate: For regulated shipments, what percentage have a complete, auditable record of every event? An incomplete chain of custody is both a compliance and a service risk.

What typical baselines look like

Across the pharmaceutical logistics teams we have worked with: 50 to 70% of coordinator time goes to manual communication and exception management; zero-touch rates are effectively 0%; time-to-resolution for common exceptions averages 24 to 60 hours, driven by queuing and communication latency rather than decision complexity; and chain-of-custody completeness often falls below 80%, with gaps concentrated in the final mile. These baselines are not signs of poor management. They are the predictable output of tools designed for aggregation, not action.

Next week: your zero-touch rate is almost certainly zero, and the reason is structural. Part 3 looks at why a decade of control towers made problems visible without fixing them. Read the full white paper at zoomlogi.com/white-paper/not-another-control-tower.