…but when the system trips during a Monday morning surge it feels like the whole plan evaporates. Most days TMW Suite handles dispatch and rating the way you'd expect - routes update, drivers get their loads, settlements mostly reconcile - but the handful of outages we've had are disruptive and often require manual shuffling. Support eventually digs us out, which is why I'm torn; they do get us back, but fixes take hours and sometimes create follow-up problems that eat the rest of the day. I've been running an 85-truck fleet in the Pacific Northwest for 16 years and for routine workloads it's fine; for high-volume windows or after updates you need a contingency. If you count reliability as the single priority, plan on a backup.
Emory Rolfson
Member since January 2026
Activity
Reviews89
Helpful0
Reviews
89 reviews · average 3.9
I've used Navisphere for three years in our Pacific Northwest fleet. When you have 85 trucks to watch, quick support matters; sometimes their reps jump on a call, untangle a gnarly EDI mapping or late-carrier update in under an hour and everything hums. Other times it's a different story - tickets sit open for days, emails bounce between teams with no clear owner, and a promised callback never comes. That inconsistency is maddening because the platform itself actually gives the visibility we need, but the customer service rhythm doesn't match the tempo of live freight. I’m torn: it's worth keeping for the dashboard and milestone feeds, but be ready to push hard for escalation when things go sideways.
Bottom line: getting Shippeo live was faster than I expected, largely because they gave us a single onboarding rep who owned the whole process. He handled the messy telematics ID mapping, walked us through API keys, and fixed the odd data mismatch during a one-hour screenshare - that one session saved us days. After 16 years running an 85-truck operation in the Pacific Northwest, I really value that kind of hand-holding when rolling something new out. There were a few noisy default alerts that needed tuning, but once dialed in the ETAs were reliable and our customers stopped calling as much. The start-up pain was small and short-lived, which made the platform worth the switch for us.
I've used FourKites for about eleven months. Two months ago an AI Digital Worker automatically overrode a manual reroute we set up after a mudslide shut I-5, directing a loaded trailer back toward the closure and leaving it stuck for eight hours; that one mistake triggered a missed delivery window for a major parts customer and roughly $6,800 in chargebacks and overtime. We run 85 trucks across the Pacific Northwest, so that single automated decision cascaded into three days of reshuffles and an avoidable stockout at a steel supplier. The platform’s timeline and reasoning were maddeningly opaque - support took over a day to respond and the log just showed a bot decision with no useful justification or clear manual-override trail. I’ve disabled automatic execution on mission-critical moves; the idea of 24/7 digital workers sounded good on paper, but after this incident I won’t let it make high-stakes calls without a human in the loop.
When a Saturday storm knocked out our EDI feed and shipments started piling up, support answered on the first ring and didn’t hand us off. They took a remote session, dug into our custom mapping, and kept working through crummy connectivity until we could test each fix. The rep asked for log files I didn’t even know existed, stayed on the line for three hours, and had us back moving in about 90 minutes. Saved us from drivers sitting in the rain at the Portland yard and probably paid for the subscription that week alone. That sort of persistence and knowledge makes me comfortable running 85 trucks on this system.
What sold me was the push notifications for ETA changes - no digging through emails, just a quick ping that tells me which load is slipping. After sixteen years managing an 85-truck fleet in the Pacific Northwest, that heads-up has probably eliminated a couple hours of phone tag every day. Day-to-day the mobile UI is practical: drivers can snap a photo and send an exception code in two taps, so I get context without the usual back-and-forth. It hiccups in dead zones - map tiles can lag - but the alerts still come through and let me reroute before things cascade. Four stars because it genuinely smoothed our daily operations, though offline performance could be tighter.
After sixteen years steering an 85-truck fleet through the unpredictable roads of the Pacific Northwest, I needed a system that actually held up when things went sideways. Infios did exactly that during last winter's storm stretch - when a terminal flooded the platform automatically rerouted loads and reassigned drivers so customers still got deliveries within the promised windows. What really made me happy was the automatic reassignment feature; it flipped jobs between terminals without me being pulled off the floor to play dispatcher. We saw no system outages during our busiest weeks and the exception alerts were useful, not noise. If reliability is the metric that matters to you, Infios kept our operations moving when everything else was falling apart.
Half the time their support actually saves my day - a senior engineer jumps on a call and untangles some horrid mapping issue within an hour. Other times it's like shouting into a ticket void: tier-one reps take ages to escalate and we sit with scheduling errors for days. We run 85 trucks in the Pacific Northwest and when yard-management glitches block check-ins it's not just annoying, it costs real hours and pay. They eventually fixed a recurring appointment bug after three escalations, but getting to that engineer required a ton of follow-up from my side. I'm honestly torn - when support shows up they're capable and helpful, but the inconsistency makes me cautious about relying on them for mission-critical problems.
Bottom line: getting OTM up and running was far less painful than I expected. The one thing that made me genuinely glad was the import/mapping wizard - I dumped our messy carrier and route spreadsheets in and it auto-matched fields and corrected date formats that normally take forever to clean. Onboarding support was surprisingly hands-on; a rep walked us through API keys and carrier mappings in two calls and we had live shipments moving after a week. Our 85-truck operation in the Pacific Northwest has weird seasonal routes and odd carrier IDs, and the system handled those quirks without forcing me to rewrite everything. If you want a TMS where the initial data migration doesn't wreck your schedule, OTM's tooling and support make that stage way easier.
I've used Track-POD for about three years. What sold me was that the app never ate signatures when drivers lost signal on the coast; every time a driver finished a run in dead zones, the photo and signature synced up perfectly once back online. We run 85 trucks around the rains and mountains of the Pacific Northwest, and having that confidence - that proof won't vanish - is huge on days when customers demand answers. It's not flashy, but notifications and status updates have been dependable enough that our dispatchers stop calling drivers to confirm deliveries, which saves hours each week. Few hiccups in 36 months; when something did go wrong the support team fixed a sync bug within a day.
And then the I-5 was shut down mid-morning and all our planned ETAs went out the window. Routific's live GPS tracking let me see which driver was actually nine miles north of the closure, so I could reassign a priority medical courier within minutes and keep a hospital delivery on time. I've been running a fleet of 85 trucks for 16 years in the Pacific Northwest, so I know how fast a small delay can become a disaster - that one feature saved us a client that day. The app hiccuped a couple times and the mobile UI could use tidying, which is why this is a four-star, but when the highway collapsed around our schedule that tracking was the thing that mattered.