Catch product and trailer mismatches before they ship
Every few minutes, WebRun opens BeyondTrucks, reviews each newly planned load, checks the product against the assigned trailer's prior contents, wash status, and compartment specs, logs any incompatibility to a Google Sheet, and warns dispatch on Telegram so a bad match is caught before the load ships.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I catch product and trailer incompatibility before a load ships?
WebRun reviews every load planned in BeyondTrucks every 10 minutes, checking the product against the assigned trailer's prior contents, wash status, and specs. It logs any conflict to a Google Sheet and warns dispatch on Telegram with the exact rule that failed, so a bad product-to-trailer match is caught before the load ever leaves the yard.
- Bad product-to-trailer matches are caught before the load leaves, not after
- Every conflict is logged with the exact rule it failed for audit
- Dispatch gets a Telegram warning within minutes of a risky load being planned
Built for tank truck dispatchers · bulk chemical carriers · food-grade tanker fleets · safety and compliance leads
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
app.beyondtrucks.comin a real browser with your saved login - no setup, no API keys. -
1
BeyondTrucks - check product against trailer
WebRun opens BeyondTrucks to check product against trailer. - Open BeyondTrucks and read each load planned but not yet departed
- Read the product being loaded and the assigned trailer's specs, prior contents, and wash status
- Apply your compatibility rules: prior-product carryover, coating and gasket limits, and any food-grade or hazmat restriction
- Mark each load as clear or conflicted with the reason
Done when Every planned load is marked clear or conflicted with a specific reason.
-
2
Google Sheets - log each conflict
WebRun opens Google Sheets to log each conflict. - Open the Compatibility Log sheet
- Append a row for each conflicted load with the order number, product, trailer, prior contents, and the rule that failed
- Mark a previously flagged load as resolved once its trailer or product changes
Done when Every conflict is recorded in the log with the rule it failed.
-
3
Telegram - warn dispatch before ship
WebRun opens Telegram to warn dispatch before the load ships. - Send any conflicted load to the dispatch Telegram channel right away
- Show the order, product, trailer, and the exact rule that failed so dispatch can reassign
- Post a follow-up once the conflict clears on the next check
Done when Dispatch has an immediate Telegram warning for every conflicted load.
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 reassign the trailer on its own?
No. WebRun only flags the conflict and warns dispatch on Telegram with the failed rule. A dispatcher reassigns the trailer or product in BeyondTrucks. It never changes a load assignment unattended.
What kinds of mismatch does it catch?
Prior-product carryover, missing or overdue wash for the required grade, coating and gasket limits, and food-grade or hazmat restrictions. You define the compatibility rules and WebRun applies them to every planned load.
How current is the trailer status it checks?
It reads the live trailer record in BeyondTrucks on every run, so a fresh wash or a trailer swap is reflected within minutes and a load that now passes drops off the warning list.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.