ERIK SORTINO← Portfolio home
Project 01 · Operate

AI Dispatch &
Network Operations

An operations command-center case study built around 30,000 synthetic mobility service events. The objective is to detect where automation requires human intervention, separate network-coverage problems from peak-capacity and capability problems, and turn those signals into management action.

Synthetic portfolio data. No HONK, customer, or provider records are used. The model mirrors operational concepts I worked with—automated dispatch, human-dispatch “panics,” provider assignment, SLA, ETA/ATA, partner type, cost and NPS—without exposing proprietary data.
30,000Service events
—Panic rate
—Affiliate mix
—Avg TTFD
—SLA attainment
>80NPS design target
Geographic signal

Where does automation break down?

Management interpretation

Three different problems require three different interventions.

Phoenix and Oakland point to partner-network coverage and affiliate dependence. Los Angeles Friday evenings point to peak-capacity and dispatch-rule pressure. Las Vegas tow events point to capability/equipment constraints.

Root-cause framework

Don't solve every panic by “adding providers.”

Network coverage

Provider density, rates, distance and acceptance can create geographic failure even when overall supply looks healthy.

Phoenix: 23.5% panic
41.6% affiliate

Peak capacity

A mature market can still fail during demand spikes. LA Friday evenings averaged about 14.0 minutes TTFD with roughly 40.4% SLA attainment in the modeled scenario.

Capability

Las Vegas tow panics were deliberately seeded so capability is the leading failure reason (~39%), demonstrating targeted equipment/capability recruiting rather than generic supply growth.

Partner economics

Signed-versus-affiliate mix is treated as an operating signal. High panic plus high affiliate dependence triggers rate, coverage, acceptance and provider-density review.

Provider 360

Move from market signal to accountable operating review.

Provider lensQuestionAction
Assignment shareIs volume concentrated?Protect capacity / diversify risk
AcceptanceAre offers being declined?Inspect rate, distance, ETA
SLA / TTFDIs speed deteriorating?Adjust routing / capacity
CapabilityCan the provider serve the job?Recruit equipment-specific supply
Cost / NPSIs service economically and experientially healthy?Balance cost, quality and retention
Executive takeaway

Detection → diagnosis → intervention → measurement.

My operating approach is to identify the hotspot, compare automation and partner mix, inspect failure reasons, isolate the root cause, choose the intervention, then measure the effect on TTFD, SLA, cost and customer experience.

Erik Sortino · Project 01 — AI Dispatch & Network Operations · Synthetic portfolio case study