The live ETA feed was night-and-day compared to our old spreadsheet-and-calls routine. On my ten-truck operation in the Northeast it cut morning phone-tag in half, though every so often a carrier update lagged - still a big step up from what we used before.
I've used Overhaul for about nine months. Before this we were living in carrier portals and spreadsheets - constant phone tag and guessing ETAs - so the shift felt like finally getting a clear head when everyone else was yelling. The one thing that genuinely made me happy was the alert logic: tuned geofence and ETA-change alerts cut our dispatchers' check-in calls by at least 70% and stopped most of the panic over minor delays. Running fifty trucks across the Northeast and with 18 years in the business, I hate false alarms; being able to filter noise so only real issues hit our team was a relief. Fewer surprises, less late-night scrambling, and quicker decisions when something actually goes wrong.
Bottom line: onboarding Overhaul was a nightmare and set us back weeks. Their documentation was thin and the carrier integrations that were listed as supported required custom APIs and endless field mapping - what should have been a few days turned into six weeks of developer time. My 120-truck fleet in the Midwest, with 25 years in the business, ate the cost: we hired an outside consultant and ended up with missed delivery windows and detention fees while ETAs bounced around. Customer support was slow and procedural - ticket after ticket with canned responses and no one owning the problem until I escalated multiple times. I wanted better visibility, but the onboarding friction and hidden costs mean I can’t justify rolling this out company-wide until they simplify integrations and actually test carrier connections first.
Rate it, and the next carrier reading this page sees what you found.
