Delivered engagementAI & Agents · $25k – $35k
NorthLane Freight

Logistics & supply chain

Delivered engagement. Coralsoft designed and built this product end to end; figures below retain their evidence level.

WebBackendAutomationNext.js (ops dashboard)Postgres + pgvectorRedis
agentic-ai-logistics-dispatcher.example / dashboard
Dispatcher exception queue — live loads, severity, agent confidence, and autonomy controls
The situation

What was in place before we started.

An autonomous AI agent — not a chatbot, but an agent that takes real actions in external systems — built for a mid-sized US freight brokerage to resolve dispatch exceptions across the TMS, ELD, email, SMS, and carrier portals.

The client runs a dispatch operation where a team of 14 dispatchers manually tracks shipment status and reacts to delays, carrier ELD silence, driver no-shows, and rate disputes. On average, 38% of loads per week required manual dispatcher intervention — calling the carrier, sending an email, updating the TMS, notifying the customer.

This wasn't a job for a conventional chatbot: the solution needed to act across multiple systems at once (TMS, ELD provider, email, SMS, carrier portals), not just answer questions. The team had already tried no-code automation (Zapier workflows), but exception logic was too conditional — every case required judgment calls about “how critical is this” and “who should this escalate to,” which no-code tooling couldn't sustain.

Constraint

A wrong autonomous action — calling the wrong carrier, or mistakenly approving a rate increase — costs the client money and reputation, so strict guardrails and confidence thresholds were required before any human escalation.

Timeline
6 months reconstructed
Team
5 people reconstructed
Budget
$25k – $35k reconstructed
Platforms
3
Stackrecorded
Next.js (ops dashboard)Postgres + pgvectorRedisDocker / KubernetesLangGraphClaude 3.5 SonnetGPT-4o miniTwilioCustom TMS adapters
Challenges

Each constraint, and what we did about it.

Constraint

A wrong autonomous action — calling the wrong carrier, or mistakenly approving a rate increase — costs the client money and reputation, so strict guardrails and confidence thresholds were required before any human escalation.

What we did

The agent runs on a planner-executor loop (LangGraph) with a per-load state machine and a “propose → execute → confirm” mode at a configurable autonomy level. Claude 3.5 Sonnet handles exception classification and communication generation, while GPT-4o mini does fast triage filtering of the incoming event stream. Typed function-calling reaches into the TMS API, an email/SMS gateway (Twilio), carrier-portal adapters (REST with headless fallback), and Slack notifications to dispatchers.

Results

Outcome, with the source of every figure.

91%
of exceptions resolved fully autonomously, with no dispatcher involvement
self-reportedCoralsoft's own figure for its own delivery, stated in cases.ts. No third-party attestation in the sources.
4.6 min
average exception response time (down from 41 min)
self-reportedCoralsoft's own figure for its own delivery, stated in cases.ts. No third-party attestation in the sources.
3.4×
dispatch team throughput, with no headcount increase
self-reportedCoralsoft's own figure for its own delivery, stated in cases.ts. No third-party attestation in the sources.
Showcase

How the system fits together.

3 of 3 views
agentic-ai-logistics-dispatcher.example
Agent trace — propose, execute, and confirm steps for a load exception
agentic-ai-logistics-dispatcher.example
Escalation review — agent proposal with full context for human approval
agentic-ai-logistics-dispatcher.example
Agent architecture — LangGraph planner-executor loop with guardrails
Roadmap

How it was sequenced.

6 monthsreconstructed delivery
Month 1

Discovery & architecture

Monitors every load's status in real time (ELD + TMS webhooks), flagging anomalies — ETA slippage, GPS silence >2 hours, route deviation.

  • Real-time monitoring
Months 2–3

Core build

Classifies exceptions by type and severity through LLM-based analysis of load context: value, customer tier, freight type, carrier history.

  • Exception classification
Month 4

Integrations & data

Acts autonomously within defined authority limits: drafts and sends personalized email/SMS status requests to carriers, updates TMS records, logs all communication, and generates customer-facing updates.

  • Autonomous action
Month 5

Hardening & QA

Escalates to a human only the cases where model confidence falls below threshold or financial risk exceeds a set limit — with full context and a proposed resolution, rather than a raw alert.

  • Human escalation
Month 6

Launch & handover

Dispatcher decisions (approve / override the agent's action) feed back as a reward signal for weekly prompt fine-tuning and intent-classifier retraining.

  • Feedback learning

More work like this.

Every case study is a Coralsoft delivery story, with the evidence behind each figure kept visible.