Brokers hand the load to whoever confirms first. Our agents answer before your desk can.
A dispatch agent that triages broker calls, parses rate sheets, quotes back inside 30 seconds, and logs everything to McLeod, AscendTMS or Truckstop while your dispatchers sleep.
Three problems every freight operator is paying for, whether they know it or not.
Dispatch lag on broker calls and load offers
Mid-size brokers lose attractive loads because the carrier-side dispatch is too slow to confirm. On a hot lane the broker does not wait — the load goes to whoever picks up first, and the margin goes with it. It leaks load by load, and nobody is tracking it line-by-line.
Email triage on 4-party threads (carrier, broker, shipper, receiver)
Your dispatchers spend the day reading and replying to 4-party email chains instead of moving freight. Some are status-update boilerplate. The rest bury one real decision in a wall of CC'd reply-all. Zapier-built classifiers misread the CC field and route to the wrong party.
Rate-sheet chaos, no historical lane intelligence
Every broker has a folder of rate sheets in formats that do not talk to each other (PDF, XLSX, copied into email body). Quoting a new load means a dispatcher opening sheet after sheet, then guessing on lane history. No real-time historical lane benchmark surfaces inside your TMS at the point of the quote.
Dispatch Agent for Freight & Logistics
A dispatch agent that picks up the load-offer call in seconds, pulls the relevant rate sheet and historical lane data in real time, confirms or counters with the broker, and logs the resulting booking straight to McLeod, AscendTMS or Truckstop. Your human dispatchers handle exceptions and relationships, not data entry.
- Voice agent picks up broker calls in seconds, 24/7
- Parses rate sheets in any format (PDF, XLSX, email body, scanned image) into a unified lane database
- Quotes against real historical lane data (your own + FreightWaves SONAR if subscribed)
- Books into McLeod, AscendTMS, Truckstop, or Tailwind TMS via API
- Hard-routes anything off-spec (oversize, hazmat, refrigerated cold-chain) to a human dispatcher
Built in three layers. Buy them together, or ship one at a time.
Voice Dispatch Agent
Live broker call handling, sub-30-second response on every load offer.
- Inbound voice agent on your dispatch line, 24/7 coverage including overnights
- Real-time rate-sheet and historical lane lookup during the call
- Confirms, counters or declines based on your configured margin rules
- Logs every call with audio + transcript to the TMS shipment record
Email & EDI Triage
4-party thread parsing, CC-aware routing, voice-locked auto-replies.
- Reads multi-party email threads, identifies the actual decision-maker
- CC-field gate (the missing piece that broke every prior Zapier attempt)
- Drafts voice-locked replies in your dispatcher's tone
- Auto-sends only the safest 30% of replies; drafts the rest for human review
Lane Intelligence & Rate History
Real-time historical lane data at the point of every quote.
- Ingests rate sheets in PDF, XLSX, email body, or scanned image (we OCR the scans)
- Builds unified lane database with rolling 90-day rate history per lane
- Surfaces lane benchmark inside the TMS at quote time
- Optional integration with FreightWaves SONAR, DAT RateView, Truckstop RateAnalysis
Proof, not pitch decks.
EU logistics group (mining + freight)
Built an automated email triage system. Routine response time collapsed from 6 hours to 6 minutes, dispatcher hours dropped sharply.
Why I'm the right person to fix this for your dispatch desk
The Lyon mining-logistics engagement is the proof point. We modeled freight email as a 5-variable problem (intent, sender role, thread depth, attachment posture, CC topology) instead of a one-step classify-and-reply, and the same approach is what makes the Dispatch Agent actually book loads instead of just transcribing calls.
Waseem Nasir · founder · SkynetLabs · Bali (GMT+8)
Three tiers, tuned to your freight stage.
Starter
Small carrier (3-10 trucks) or single-desk broker.
- Voice dispatch agent on your main line
- Email triage with CC-aware routing
- Integration with one TMS (McLeod, AscendTMS, Truckstop or Tailwind)
- 7-day ship, 30-day post-launch tuning
Freight Pro
Mid-size broker or carrier (10-50 trucks), full dispatch stack.
- Everything in Starter
- Rate-sheet OCR + unified lane database
- Historical lane intelligence at quote time
- FreightWaves SONAR or DAT RateView integration (if subscribed)
- 14-day ship, 60-day tuning, monthly report
Multi-terminal
Multi-terminal carrier or 3PL, per-terminal reporting.
- Everything in Freight Pro across all terminals
- Per-terminal dispatcher scorecards
- Cross-terminal load-balancing logic
- Quarterly tuning + new-feature roadmap
- Priority response: 1 business hour
Questions freight owners ask before booking.
Does this integrate with McLeod, AscendTMS and FreightWaves?+
Yes. McLeod LoadMaster has a stable SOAP + REST surface (older API but reliable). AscendTMS exposes a modern REST API. Truckstop has both a partner API and EDI options. Tailwind TMS is the cleanest of the four if you have a choice. FreightWaves SONAR and DAT RateView integrate as data sources for lane intelligence (you supply the subscription, we wire the lookup).
How does the voice agent handle hazmat, oversize or refrigerated loads?+
Hard-routes to a human, every time. The agent is configured to recognize the keywords (placard class, dimensions over LTL standard, temperature-controlled requirements) and instantly hand off to your on-call human dispatcher. Hazmat and oversize have too many regulatory edge cases for any AI to handle responsibly in 2026.
What if the agent quotes a bad rate?+
Three safeguards. First, margin rules are configured per lane and per trailer type before go-live; the agent cannot quote below your floor. Second, every quote logs to the TMS with the rationale (which rate sheet, which historical comparable). Third, the dispatcher gets a morning digest with every quote from the prior 24 hours flagged for spot-check.
Can it handle inbound calls and outbound calls?+
Both. Inbound is the default (broker calls in with a load offer, agent picks up). Outbound covers status updates to shippers and receivers, driver check-in calls, and load-confirmation outreach. We do not run cold-outreach calling from this agent; that is a separate engagement and a different regulatory surface (TCPA).
What about driver-side: Samsara, Geotab, KeepTruckin integrations?+
Read-side integrations available with Samsara, Geotab and Motive (formerly KeepTruckin). The agent can pull current driver HOS, current position, and ETA from these platforms at quote time to make accurate commitments. Write-side (dispatching to driver app) routes through your TMS, not direct to the ELD platform.
How long until I see ROI?+
Off-hours load capture shows up inside week 1 (the calls that land after your desk goes home get answered instead of going to a competitor). Email-triage time savings show up immediately. Margin gains from lane intelligence compound over 60 to 90 days as the unified rate-history database fills in.
Stop losing loads to dispatch lag.
Message us for a freight-specific audit. We pull a week of your dispatch logs, model the off-hours capture rate and the margin lift from lane intelligence, and tell you honestly whether this earns out inside 60 days.
Message us on WhatsAppWhatsApp or email · Bali hours: 1-hour reply · otherwise within 6 hours