You already have Wialon. This is the screen your dispatcher was missing.
Wialon is a very good telematics platform and a poor dispatch board, which is not a criticism: it was never trying to be one. It knows where the truck is. It does not know that the truck is on its way to a customs stop in Nădlac that closes at six, that the driver has ninety minutes of driving left, or that the load has not been invoiced.
The whole setup.
There is no hardware step, because there is nothing to install. Your units stay exactly where they are and Wialon keeps running as it does today.
An afternoon
You generate an API token in Wialon and paste it into VIGILFleet. The token is encrypted at rest. Nothing in the cabs is touched and nothing is uninstalled.
The same day
Your units appear as trucks, with trailers, drivers and tachograph cards mapped across. A dispatcher can open a real order and watch a real truck move on it.
Within a week
The day is being run on the board, your customers have tracking links, and the finished orders are arriving in accounting with the fuel and toll costs already on them.
What we read out of Wialon.
A poll runs every minute, per company, and turns the raw feed into operations rather than into a second map. Sessions are pooled so we are not re-authenticating against your account on every request, and the token lives encrypted rather than in a settings field in plain text.
- Live position, heading and speed for every unit
- Fuel level, used both for cost and for the fuel theft detector
- Odometer, snapshotted so cost per kilometre does not depend on a manual reading
- Tachograph driver identification, so the driver on the board follows the card in the vehicle
- Daily distance and driving statistics, kept as history on our side
What Wialon does not do, and this does.
The point of the integration is not a nicer map. It is everything that becomes possible once the position feed is sitting next to the order, the driver's hours and the invoice.
- Multi-stop orders: loading, customs, ferry, rail and offloading in one job
- Arrival within 500 metres of a stop proposes the status change for the dispatcher to confirm
- EU 561 driving time, breaks and rest computed from the tachograph data
- A live tracking link per order for the customer, and a translated one for the driver
- Fuel and toll transactions matched to the order, and an invoice with the right VAT at the end of it
If your Wialon connection goes stale or starts erroring, the map says so. An outage nobody noticed is worse than an outage.
Questions people actually ask.
- Do we have to leave Wialon?
- No, and we would rather you did not. VIGILFleet reads Wialon over its API and adds the dispatch, compliance and invoicing layer on top. Your Wialon account, your units and your existing reports carry on unchanged.
- What do you need from us to connect it?
- One Wialon API token with read access. It is stored encrypted, and you can revoke it from Wialon at any time.
- Does it work with a Wialon hosting partner, or only with the main service?
- It talks to the Wialon API, so a hosted or partner-run account works the same way. Tell us on the call which host you are on.
- How much of our fleet data has to be re-entered?
- Very little. Trucks come across from your units, and drivers follow the tachograph cards as the shifts rotate, so the board keeps up with who is in which vehicle without anyone typing it.
- How often does the position update?
- Every minute. Fuel, odometer and driver data arrive on the same cycle.
Read next
Bring your Wialon token to the call.
Thirty minutes, your own trucks on the board while you watch, and an honest answer about whether this is worth it for a fleet your size.