Catch livestock loads before they hit the time-in-transit limit
Every hour, WebRun opens M2X, reads each active load's departure time and route progress, works out time-in-transit for the animals aboard, posts a Slack alert for any load nearing its welfare limit, and drafts a driver check-in text for a dispatcher to review and send.
- No credit card
- Under $0.01 per run
- Cancel anytime
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.m2xgroup.comin a real browser with your saved login - no setup, no API keys. -
1
M2X - track time-in-transit on active loads
WebRun opens M2X to track time-in-transit on active loads. - Open M2X and list loads currently in transit
- Read each load's loaded time, animal type, and route progress
- Work out how long the animals have been aboard against the welfare time limit
- Flag any load within the warning window before that limit
Done when Every active load has a current time-in-transit reading against its welfare limit.
-
2
Slack - alert dispatch on loads nearing the limit
WebRun opens Slack to alert dispatch on loads nearing the limit. - Post an alert to the dispatch channel for each load nearing its welfare limit
- List the truck, driver, animals aboard, and hours remaining before the limit
- Put the load with the least time remaining at the top
Done when Dispatch has a Slack alert for every load approaching its time-in-transit limit.
-
3
Twilio - draft a driver check-in text
WebRun opens Twilio to draft a driver check-in text. - Draft a short check-in text to the driver of each flagged load asking for status and any needed rest stop
- Include the hours remaining before the welfare limit
- Leave every text unsent for a dispatcher to review and send. Do not text the driver automatically
Done when A driver check-in text is drafted for each flagged load, waiting for a dispatcher to send.
How do I get alerted when a livestock load nears its time-in-transit limit?
Every hour WebRun opens M2X, reads each active load's loaded time and route progress, and works out how long the animals have been aboard against the welfare limit. It posts a ranked Slack alert for loads nearing that limit and drafts a driver check-in text in Twilio for a dispatcher to send, so no load runs long unnoticed.
- Dispatch hears about a long load hours early, not after the limit
- Loads are ranked by time remaining so the tightest one is handled first
- Driver texts are drafted and ready, but never sent without approval
Built for livestock haulers · cattle transporters · fleet dispatchers · animal welfare officers
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 text my drivers on its own?
No. The driver check-in text is drafted in Twilio and left unsent for a dispatcher to review and send. The hourly Slack alert to your own dispatch channel posts automatically, but no message reaches a driver without human approval.
How does it know a load is close to the welfare limit?
It reads each active load's loaded time and route progress in M2X and compares elapsed time-in-transit against the welfare limit you set, flagging any load inside the warning window you choose.
What if a load has already been delivered?
It reads live load status in M2X each hour, so any load already unloaded drops off the watch list automatically and never triggers an alert or a driver text.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.