Most of it you can fix in five minutes.

1. 1. Check whether it stopped mid-trip or between shifts. Stopping between shifts is almost always a unit that lost power — a disconnected battery, a pulled fuse, or a workshop visit nobody logged.
2. 2. Open the vehicle and look at Last seen against Last ignition. If the last position is at a known dead zone, the unit is buffering and will backfill on reconnect. Nothing is lost and no action is needed.
3. 3. For an OBD unit, confirm it is still in the port. They get knocked out by feet more often than they fail. Reseat it and it reports within two minutes.

Still silent after the vehicle has run a full shift: raise a ticket with the unit reference and we will check the network side before sending anyone.

1. 1. Compare a full-to-full refuelling against the reported consumption. A consistent percentage error across every vehicle of one model is a calibration curve, which we correct centrally once you tell us.
2. 2. Check whether the error only appears on slopes. Tank-probe readings swing on a gradient. We smooth this, but a yard on a slope can still show a phantom drop at rest.
3. 3. Confirm the alert fired against a stationary vehicle. Theft alerts only trigger on drops while stationary and away from a known refuelling point. A drop under load is consumption, not loss.

One vehicle wrong while identical ones are right usually means the probe, not the software. Raise a ticket and we will book a fitter.

1. 1. Confirm which identifier they were issued. Drivers sign in with the mobile number on their record, not an email. A number changed by HR without updating the fleet record is the usual cause.
2. 2. Check the driver is still assigned to a vehicle. An unassigned driver can sign in but sees an empty screen, which reads as a failed login to them.
3. 3. Have them check the app language. The app defaults to Arabic. A driver expecting Urdu may believe they are on the wrong screen entirely.

Ticket with the driver's record reference. We can send a one-time sign-in link that bypasses the number.

1. 1. Check the plate against the istimara exactly. Wasl matches on the plate as registered, including the Arabic characters. A Latin transliteration will be rejected without a useful message.
2. 2. Confirm the sequence number matches the vehicle, not the trailer. Registering a trailer's number against a tractor is the single most common rejection we see.
3. 3. Check the operating card is current. An expired card fails registration even when every other field is correct.

If all three match and it still fails, send us the vehicle reference — rejections without a reason are usually upstream and we chase them for you.