Skip to content
Kavell
Phase 2 · Transport & Logistics AI

Freight, dispatch, and workforce — one operations surface.

Carrier voice AI replaces the check call. TMS integrations replace the spreadsheet. The same workforce engine — AI dispatching, time keeping, work orders, dispatch automation — runs for trucking fleets and port terminals alike.

Transport and logistics operations team monitoring dispatch, route intelligence, and workforce scheduling across wall-mounted dashboards.
Carrier voice AI, dispatch, and workforce management — applied to freight brokerages, 3PLs, and port terminals.
Who this is for

Freight brokerages, 3PLs, drayage operators, carriers, port authorities, and marine terminal operators.

Freight brokerages & 3PLs

50–500 loads per day. Check calls burn night-shift hours. Rate confirmation volume is outpacing the ops team.

Carriers & drayage operators

40–400 trucks. Dispatch, HOS, and work orders live across too many systems. Every missed appointment is a fee.

Port authorities & terminals

Gang scheduling, TWIC, union pay rules, and OSHA reporting running on spreadsheets and legacy applications.

Freight & dispatch services

Carrier voice, load dispatch, appointment, and freight audit.

Carrier Voice AI

Vapi-powered outbound calls for load coverage, check-calls, and rate negotiation within guardrails. The check-call replacement is a category-defining differentiator.

Load Matching & Dispatch AI

EDI and API integration with major TMS platforms (McLeod, Turvo, MercuryGate), exception routing, and multi-modal coverage.

Appointment & Terminal Scheduling AI

Dock, terminal, and berth appointment booking with automated drayage coordination — common surface for trucking fleets and port terminals.

Freight Audit & Claims AI

Invoice reconciliation, OS&D tracking, and first-draft claim packages with evidence attached.

Document Intelligence

BOL, POD, rate confirmation, work order, and port manifest parsing — feeds directly into your TMS, TOS, or dispatch board.

Workforce engine · Four pillars

Dispatching, time keeping, work orders, and end-to-end dispatch automation.

The workforce engine runs for trucking fleets and port terminals on the same platform. What changes is the ruleset — DOT and HOS for drivers, TWIC and ILA / ILWU for port labor.

Specialty · Ports & terminals

Port & terminal workforce specialty

The four pillars above are the same engine we deploy for port and terminal operators. TWIC credentialing, ILA / ILWU pay rules, grievance-defensible time keeping, and OSHA trail are all first-class. If you run a marine terminal or a stevedoring firm, the workforce module is configured for your environment.

  • TWIC credential reconciliation
  • ILA / ILWU pay-rule compliance
  • Gang scheduling & vessel arrival coordination
  • OSHA 300 / 301 trail
  • HRSA-referenceable operations
Port terminal control room monitoring shift assignments, time & attendance, and work-order management across dashboards.
The same four-pillar engine, configured for port and terminal operators.
Integrations

Systems we already speak.

McLeodTurvoMercuryGateDATTruckstopTerminal Operating SystemsPayroll gatewaysTWIC readersEDI 204 / 210 / 214 / 990
Compliance posture

Controls baked in, not bolted on.

  • DOT / FMCSA alignment
  • Auditable voice transcripts
  • SOX-ready financial trails
  • TWIC credential validation
  • ILA / ILWU pay-rule compliance
  • OSHA 300 / 301 trail
Modeled · 40-truck pilot
63% of check calls

Modeled auto-handled rate for carrier check-calls in a pilot with a 40-truck fleet.

Engagement model

Audit → Pilot → Production → Scale

Two-week scoping, 4–6 week pilot, then a 60–90 day production rollout. No multi-year big-bang programs.

Pricing guidance

Starts at $3K–$15K per month (freight) · $10K–$50K per month (port/terminal) · $50K–$500K implementation

Fit, scope, and integrations drive the final quote. Book a call to walk through your stack and get a written scoping proposal.

FAQ

Questions buyers ask us first.

The honest answers. If your question is missing, book a fit call and we will answer it live.

Is this one product for fleets and ports, or two?
One engine, two configurations. The freight services (voice, dispatch, audit) and the workforce pillars (dispatching, time keeping, work orders, dispatch automation) run on the same platform. What changes is the rule set — DOT and HOS for fleets, TWIC and ILA / ILWU for ports.
Will the voice AI work inside our TMS?
Yes. Carrier voice AI integrates with McLeod, Turvo, MercuryGate, and most major TMS platforms via API or EDI. Call outcomes write back to the load record automatically.
Can Kavell respect ILA and ILWU rules for port labor?
Yes. Union rules are configurable at the seniority-tier, rotation, skill-restriction, and pay-code level. The dispatch engine applies the rules before a human sees the assignment.
Is this a TOS or TMS replacement?
No. Kavell sits alongside your Terminal Operating System and TMS. Both stay in place as systems of record; Kavell handles labor, time, work orders, and the orchestration between them.
How does auto-dispatch handle exceptions?
Auto-dispatch proposes assignments against your criteria. Exceptions (no eligible driver or worker, rule violation, low-confidence match) route to a supervisor with the reasoning attached. You never get silent failures.
Does time keeping integrate with our payroll system?
Yes. Time keeping produces clean payroll files in your required format. Union and HOS pay-rule interpretation happens on the Kavell side so payroll receives a ready-to-process file.
Is TWIC credential reconciliation automated?
Yes. TWIC expirations, revocations, and reader events reconcile into worker eligibility automatically. A worker whose credential lapsed cannot be auto-dispatched.
Can we start with just one pillar or service?
Yes. Many engagements start with carrier voice or AI dispatching alone, then layer in the other pillars and services over 90 days.

Ready to see it on your own lane or terminal?

A 30-minute call is enough for us to know whether Kavell fits. If it does not, we will say so.