Torque Fleet Dispatch Automation

Torque Logistics matched loads to trucks the way most mid-sized fleets do: a dispatcher on the phone, working off intuition and a whiteboard's worth of driver availability. Delivery confirmations, fuel logs, and invoices lived in disconnected spreadsheets that nobody updated at the same time, which meant billing lagged deliveries by days and maintenance windows got missed because nobody was watching mileage in one place.

Torque Logistics runs a fifty-truck regional fleet where dispatch decisions and paperwork had grown around one dispatcher's memory rather than a system. That works until volume grows or that person takes a day off. Torque asked us to make the process survive without depending on any one person holding it all together.

When a load is confirmed, the automation matches it against real-time truck availability and location, and sends the assigned driver their route and manifest by text within seconds. The dispatcher now reviews the match instead of building it from scratch, and only steps in when the automated pairing does not make sense.

The workflow watches Torque's ELD feed for delivery events and mileage as they happen. A confirmed delivery triggers the next steps automatically, and mileage crossing a maintenance threshold raises a flag before a truck develops a real problem on the road, not after.

The moment a delivery confirms through the ELD feed, the invoice generates and goes out, no one has to remember to bill for a completed job days later. That single change closed most of the gap between delivery and payment that had been dragging on Torque's cash flow.

We rolled the automation out route by route, running it alongside the manual process until the numbers matched consistently. Nothing about daily dispatch operations broke during the switch, and the full system was live across the fleet within a month.

Dispatch time fell by roughly eighty percent, invoices now go out same-day instead of within a week, and the fleet ran six full months without a single missed maintenance window. The automation is wired into Torque's own internal systems, so there is no public link, but the fleet's numbers speak for themselves.

The dispatcher role shifted from constant manual matching to handling the exceptions the system flags, which is a fundamentally different, less exhausting job. Invoices now go out the same day a delivery completes instead of within a week, and missed maintenance windows dropped to zero in the six months following launch. Because the automation is wired directly into Torque's internal dispatch and billing systems, there is no public demo to point to, but the fleet's own numbers carry the case.

Every Devyst engagement follows a structured process: discovery, architecture, build, and handoff. This project was no different. We aligned on scope, reviewed existing systems, delivered iteratively, and handed off with documentation and runbooks.