Catch every head-count change a driver logs in the field
Every few minutes, WebRun opens M2X, compares the booked head count on each load to the quantity a driver has edited in the app, logs any difference to a Google Sheet with the load and reason, and sends a running list of head-count adjustments to the office on Telegram to reconcile.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically flag head-count changes drivers make in the field?
Every few minutes WebRun opens M2X, compares each load's booked head count to the quantity a driver edited in the app, and captures any difference with the driver's reason. It logs each adjustment to a Google Sheet and sends a running list to the office on Telegram, so the office reconciles real field counts, not paperwork after the run.
- Every field head-count change is captured with its reason, not lost
- The office reconciles from one running log instead of scattered notes
- Loads that match the booking never clutter the adjustment list
Built for livestock haulers · cattle transporters · hauling office staff · feedlot logistics teams
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 - compare booked head to driver-edited quantity
m2xgroup.com How to Automate M2X
WebRun opens M2X to compare booked head to driver-edited quantity. - Open M2X and review loads where a driver has edited the animal quantity in the app
- Compare the driver-entered head count to the originally booked count
- Capture the load, customer, booked count, actual count, and any note the driver left
- Skip loads whose count matches the booking
Done when Every load with a driver head-count edit is captured with its booked and actual counts.
-
2
Google Sheets - log each head-count adjustment
google.com How to Automate Google Sheets
WebRun opens Google Sheets to log each head-count adjustment. - Open the Head Count Adjustments sheet
- Add a row per mismatch with the load, customer, booked count, actual count, and difference
- Include the driver's note or reason where one exists
- Mark large differences in a separate review column for the office
Done when The sheet holds every head-count adjustment with the booked count, actual count, and reason.
-
3
Telegram - send adjustments to the office
telegram.org How to Automate Telegram
WebRun opens Telegram to send adjustments to the office. - Send the day's head-count adjustments to the office Telegram channel
- List the load, the change in head, and the reason for each
- Highlight the largest discrepancies for follow-up
Done when The office has a Telegram list of today's head-count adjustments with reasons.
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
Does it change the head count in M2X or on the invoice?
No. WebRun only reads the booked and driver-edited counts in M2X and records the difference to a Google Sheet and Telegram. Your office decides how to reconcile each adjustment, so no count or invoice is changed automatically.
Where does the driver's head count come from?
It comes from the M2X driver app, where drivers edit the animal quantity on a load in the field. WebRun compares that entry to the originally booked count and logs any gap with the driver's note.
Will it flood the office with every load?
No. Loads whose driver count matches the booking are skipped entirely. Only genuine head-count adjustments reach the Google Sheet and the Telegram summary, with the largest gaps highlighted first.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.