Automated Low Reefer Fuel Alerts
Every hour, WebRun opens Wireless Links Fleet.Net, checks each reefer unit's fuel level against the remaining trip, logs any trailer below your threshold to a Google Sheet, and drafts a Telegram message to the driver so a low reefer fuel tank is caught before the load warms, held for dispatch to approve.
How do I warn a driver before a reefer runs out of fuel mid trip?
WebRun checks each reefer unit's fuel level in Wireless Links Fleet.Net every hour against the remaining trip. It logs any trailer likely to run low to a Google Sheet and drafts a Telegram heads up to the driver, held for dispatch approval, so a low reefer fuel tank is caught and topped up before the load starts to warm.
- Low reefer fuel is caught before the unit shuts down and the load warms
- Drivers get a heads up in time to fuel at a planned stop
- The driver message stays under dispatch approval, never auto sent
Built for reefer carriers · long haul fleets · cold chain fleets · fleet dispatchers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.wlius.com/fleet-management-systemin a real browser with your saved login - no setup, no API keys. -
1
Wireless Links Fleet.Net - check reefer fuel levels
WebRun opens Wireless Links Fleet.Net to check reefer fuel levels. - Open Wireless Links Fleet.Net and read each active reefer unit's fuel level
- Compare the remaining fuel to the distance and hours left on the current load
- Flag any trailer likely to run low before the delivery or next fuel stop
- Capture trailer, driver, fuel level, and estimated hours of runtime remaining
Done when Every reefer at risk of running low on fuel is captured with its runtime estimate.
-
2
Google Sheets - log low fuel trailers
WebRun opens Google Sheets to log low fuel trailers. - Open the Reefer Fuel Watch sheet
- Append a row per low fuel trailer with driver, fuel level, and estimated runtime remaining
- Update an existing row rather than duplicating if the trailer is still low
- Clear the row once the trailer is refueled above the threshold
Done when The fuel watch sheet reflects every reefer currently below threshold.
-
3
Telegram - draft driver message for approval
WebRun opens Telegram to draft a driver message for approval. - Draft a short Telegram message to the driver naming the trailer and its low reefer fuel level
- Suggest fueling before the estimated runtime runs out to protect the load
- Leave the message for dispatch to approve before it reaches the driver. Do not send it automatically
- Hold a repeat draft for the same trailer until the first is actioned
Done when A driver heads up is drafted and queued for dispatch approval for each low fuel trailer.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it message the driver without dispatch checking first?
No. WebRun drafts the Telegram message and leaves it for dispatch to approve before it reaches the driver. The internal fuel watch sheet updates automatically, but the driver message always waits for a human.
How does it know a reefer will run low?
It compares the live fuel level in Fleet.Net to the distance and hours left on the current load, then flags any trailer likely to run out before delivery or the next planned fuel stop.
What if the driver already refueled?
It reads the live fuel level each hour, so a trailer topped back above the threshold is cleared from the watch sheet and any pending draft for it is withdrawn automatically.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.