Live today
Run the trip in huntTMS
Dispatch puts driver updates on the load in huntTMS today. The driver layer is designed to land on that same record.
Give drivers one clearnext action — and dispatch the outcome
A focused driver layer for updates, documents and trip actions, connected to the office workflow.
Planned: in the development plan, no release date yet.
One action on the road,one outcome in the office
A status update or a document lands on the same record dispatch is already watching, so the office learns the outcome without asking for it.
01
One action at a time
The driver view puts the action required now first, with the trip context needed to complete it.
Planned02
The office sees the outcome
Updates become operational state on the load record. Where a step still needs a person, the screen says so.
Planned03
Documents on the load
Take it, confirm it arrived, and deal with the case where it is wrong or missing.
Planned
Know what is realtoday
The Telegram workflow and the native app are both in the development plan; neither is available today and there is no release date yet. Driver updates reach huntTMS by hand until then.
LoadHunter
Finds the load
LivehuntTMS
Runs the trip
LivehuntDRIVE
You are here
PlannedhuntPAY
Invoicing and payroll
PlannedhuntOS
One command layer
Planned
Commonquestions
Not yet. huntDRIVE is Planned, which is the ledger’s word for a product that sits in the development plan with no date attached. The Telegram workflow is the first path drivers would be onboarded onto if it is built.
Nothing through huntDRIVE, because it is Planned and not offered. Today a driver sends what they send — a message, a photo — and dispatch puts it on the load in huntTMS by hand. This page describes the workflow huntDRIVE is planned to carry, not one you can install.
That is the design: driver activity landing on the huntTMS load record, where dispatch is already looking. The connection is Planned, like the product, and it is labeled that way wherever it appears on this site.
In the plan: taken on the driver’s device, confirmed as received, stored against the load and visible only to people on that company’s account. None of it runs today, because huntDRIVE does not.
For a product that does not exist yet, the honest answer is that it has not been tested. The intent is a retry when the signal returns, and no claim of full offline operation until it has been tried to that standard.
Two waysto start today
Planned · no date
Tell us about your drivers
How many drivers are active, what devices they carry, how you reach them today and what you need back from them.