When your dispatch software vendor stopped shipping
A system that has not changed in years is not stable — it is abandoned. What matters is whether a feature request becomes a feature, or just another support ticket nobody answers.
The problem
Every dispatch system was new once. The one still running at a lot of transfer and shuttle operators was built years ago, by a vendor who sold enough licenses to live off the renewals and stopped there. The interface still looks like the year it shipped, the code underneath is older than some of the drivers using it, and every feature request goes into the same queue: nowhere.
The team routes around it instead. Bookings the system cannot handle move to WhatsApp. A schedule the software cannot build gets rebuilt in a spreadsheet every morning. None of this is a failure of the staff — it is what happens when the tool stops growing and the job does not. The pattern is the same one behind replacing WhatsApp and Excel dispatch: manual work fills the gap a stalled platform leaves open.
How 8Move handles it
8Move ships new capability on a running basis, and it is not a claim you have to take on faith — the product updates log lists what shipped and when, publicly, as it happens.
A missing feature is not a dead end either. Operators tell us what their week needs, and a real request from a real operator is how most of what is on that log got built in the first place.
A fair test of a new platform is not a demo booking. Flight delays, driver reassignment, changed pickup details, and a full day with every booking in the system at once are what actually break a legacy platform, so that is what a replacement should be tested against before the switch, not after.
What this looks like by industry
The same problem reads differently depending on the work. These are the segments it hits hardest.