TL;DR
The AI Tracking Agent is context-aware automation that proactively and reactively manages check calls, reads chats, uses live tracking plus time-and-distance ETAs, and updates your TMS stops and alerts.
Autopilot (static rules) is a deterministic rule engine (if/then triggers + templates). It’s great for narrowly defined SOPs and one-off requirements, but it does not “think,” read context, or back off when humans are talking.
Key differences (at a glance)
Area | AI Tracking Agent | Autopilot (Static Rules) |
Decision-making | Context-aware (chat + tracking + stops) | If/then triggers only |
Messaging | Dynamic, conversational; backs off for humans | Templated; always sends when triggered |
Data inputs | Breadcrumbs, ETA-to-next-stop, appointments, chat | Trigger event/time only |
Exceptions | Detects and alerts automatically | Must be explicitly encoded |
TMS updates | Auto-parses chat to set arrivals/departures and alerts | Typically tied to specific trigger points |
Compliance | Persuades, follows up, fixes permissions; multi-channel | Reminder pings only |
Configuration | Start with sample agent; override per customer/carrier | Many discrete rules to cover scenarios |
Best use | Core tracking/comms at volume | Narrow SOPs and customer-specific requirements |
