Miami dispatchers lose the same three calls every week, and they lose them at the hours nobody is at the desk. This is the logistics agent built for the Miami-Fort Lauderdale-Pompano Beach metro: it answers, qualifies, and books across Miami-Dade without anyone in Miami picking up.
Check-calls, detention starts and load status handled so dispatch only touches the exceptions. The agent answers every call from across the Miami-Fort Lauderdale-Pompano Beach metro in under two rings, applies your logistics pricing rules, and books against your live calendar. Miami dispatchers run the same escalation policy at 2am that they run at 2pm, which is the part a carrier or brokerage cannot staff for.
Every Miami build starts from the same question — what does this carrier or brokerage lose in a week, and which of those losses is recoverable. The three above are the ones that show up in FL again and again. The agent is scoped against them rather than against a feature list.
McLeod, TMW, Trucker Tools and Truckstop are named on our logistics page and Samsara is in our integration catalog for fleet data, so check-call logging, status updates and detention timestamps write into those. A different TMS gets confirmed on the scoping call rather than listed as if it already existed.
Yes. It detects the language on the open and continues in it, and the check-call is written into your system in one consistent format regardless of which language the call happened in, so dispatch reads one thing.
No, and that is deliberate. Rate is a judgment call that belongs to your broker, so the agent captures the lane, the equipment, the dates and the commodity and routes it to whoever prices it — with the details already filled in, so the callback takes a minute instead of ten.