Live Call Analytics: Coaching Dispatchers From the Conversations They're Already Having

The communication channel nobody measures

A dispatcher books a load by phone. Negotiates rate. Coordinates a pickup delay. Walks a driver through a breakdown. Calls a customer about a detention dispute. By end of shift they've spent 4 to 6 hours on calls.

What was said in those calls is the single largest unmeasured surface in trucking operations. Customer commitments, driver promises, rate agreements, dispute concessions — all happen on the phone, almost none of it captured. The next time the topic comes up, both sides remember it differently.

Centrix's live call analytics turns the phone — historically a black box — into structured operational signal.

The architecture

Three components, integrated:

Twilio — phone infrastructure

Inbound and outbound calls route through Twilio's SIP/PSTN network. Dispatchers use a WebRTC client in the Centrix dashboard, or their cell phone via Twilio Forwarding. Drivers' inbound calls land on a routing tree (by terminal, by department) that knows which dispatcher owns them.

Deepgram — real-time transcription

Calls are transcribed live via Deepgram's Nova-3 model. Latency is sub-200ms so the dispatcher can see the transcription as the call happens. Accuracy is 92-95% on a clean line, 86-90% on a CB-relayed driver call, which is high enough to be useful even on noisy connections.

live_call_analyzer — semantic scoring

The transcript flows through Centrix's call analyzer, which extracts:

• Talk-time ratio (dispatcher vs caller)
• Sentiment trajectory (improving, deteriorating, flat)
• Topic detection (rate, detention, breakdown, complaint, etc.)
• Commitment detection (any "I'll get back to you on X by Y")
• Escalation signals (raised voices, profanity, repeated complaints)
• Outcome classification (resolved, escalated, follow-up needed)

What dispatchers see

While on the call:

• Transcript in real time
• The customer / driver record opens automatically based on caller ID
• Any commitments the dispatcher makes flag for follow-up after the call

After the call:

• Auto-generated summary (3-5 bullets) that gets saved to the relevant

object's thread (load, truck, driver, customer)

• Action items extracted and added to the dispatcher's task list
• The full transcript is searchable for the next time the topic comes up

This is the part dispatchers love. The "I told her I'd send her the rate sheet" commitment doesn't slip because it's now a task. The "he said he'd have the truck ready by 10" commitment is documented for the breakdown conversation that follows.

What managers see

Beyond the call-by-call view, managers see aggregated patterns:

• Talk-time ratio per dispatcher — strong dispatchers tend to listen

more than they talk on customer calls and talk more than they listen on driver calls. The opposite pattern is a coaching signal.

• Sentiment trajectory across customers — a customer whose call

sentiment is deteriorating across calls is a churn signal that volume data lags by 60-90 days.

• Topic distribution — what dispatchers are spending phone time on.

Most carriers find 25-40% of dispatcher phone time goes to a small set of recurring problem topics (often detention disputes or recurring customer service issues) that could be addressed at the workflow level.

• Escalation rate per dispatcher — calls that go from calm to angry

vs calls that go from angry to calm. Coaching opportunity for the former; promote the latter.

After-hours audit trail

A specific use case where call analytics pays for itself: after-hours coverage. The on-call person handles 12-18 events per shift, each with some commitment to a driver, customer, or vendor. Without recording, the morning team has no idea what was promised. With Centrix's after-hours call analytics, the morning brief includes:

• Every call from overnight with caller, duration, outcome
• Any commitments made and to whom
• Any escalations the on-call person handled
• Any escalations the on-call person should have handled but didn't

This single capability has saved managed carriers from situations where the on-call person committed something the morning team didn't know about and the customer felt blown off. Communication continuity across the shift seam is the highest-impact use of the audit trail.

Coaching, not surveillance

The line between "useful coaching data" and "surveillance" is real, and Centrix's design is conservative:

• Dispatchers see their own analytics. Managers see aggregated patterns.
• Specific call review requires a documented coaching reason; ad-hoc

manager listening on individual calls without cause is locked off.

• Call retention is configurable — most carriers retain 30-90 days for

coaching and 24 months on customer-dispute calls only.

• Drivers and customers are told (during the IVR or by an opt-in greeting)

that calls may be recorded for quality. Compliance is built into the workflow — Centrix doesn't ship the recording capability without the notification.

Replacing the call center

For carriers running 50+ trucks, the dispatch and after-hours call volume is enough that some have separate call-center seats — at $80-$150/seat/ month for the phone system alone. Centrix's call infrastructure runs at roughly $0.0085/minute on Twilio + $0.0043/minute on Deepgram = $0.013/minute fully loaded. A dispatcher on the phone 4 hours a day, 22 days a month, 11 months a year = 5,808 minutes/year × $0.013 = $76/year in carrier infrastructure cost vs $1,200-$1,800 for a traditional call- center seat.

Most carriers running Centrix's call analytics drop their separate call- center / hosted PBX subscription within 60 days of going live. Annual savings: $15K-$45K per dispatcher seat consolidated, plus the analytics capability the legacy systems didn't have.

A2P 10DLC compliance, handled

The 2023 FCC rules around A2P 10DLC (application-to-person SMS) caught many carriers off-guard. Centrix's SMS path is registered as A2P 10DLC, the campaign types are documented, and the throughput limits are respected automatically. Dispatchers don't think about 10DLC; the system handles it.

Where to start

If you're 25+ trucks and have never structured your phone communications:

• Connect Twilio first. Dispatchers can dial out from the Centrix

dashboard without changing their workflow.

• Run transcription only for 30 days — see how dispatchers use the

transcript and whether the auto-summaries are useful. Most carriers decide to keep them after the first week.

• Add the analytics layer after 30 days of transcript history. Patterns

need data to surface.

Book a call analytics review — bring last week's call log and we'll show you what the analytics would have surfaced.