Automated Super Dispatch Load Status Digest
Every morning, WebRun opens Super Dispatch, counts loads in each status bucket (dispatched, in transit, delivered, pending), and posts a clean summary digest to your Slack ops channel so the whole team starts the day knowing exactly where every vehicle stands.
How do I get an automatic daily load status digest from Super Dispatch?
WebRun opens Super Dispatch every morning, counts loads in each status bucket (pending, dispatched, in transit, and delivered), flags any load with no update in 24 hours, and posts a clean digest to your Slack ops channel so the entire team starts the day with a complete fleet snapshot.
- The whole ops team gets a fleet snapshot before the workday begins
- Stale loads with no update are flagged automatically for follow-up
- No one needs to log in to Super Dispatch just to check overall status
Built for auto transport dispatchers · car hauling fleet managers · vehicle shipping operations 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
carrier.superdispatch.com/tms/loadsin a real browser with your saved login - no setup, no API keys. -
1
Super Dispatch - count loads by status
superdispatch.com
WebRun opens Super Dispatch to count loads by status. - Open Super Dispatch and navigate to the load management view
- Count loads in each status: Pending, Dispatched, In Transit, Delivered, and any exception states
- Note the total open load count and flag any loads with no status update in the past 24 hours
Done when A complete status count and stale-load flag list is ready.
-
2
Slack - post daily digest to ops channel
slack.com
WebRun opens Slack to post daily digest to ops channel. - Post a formatted digest to the ops Slack channel showing counts per status bucket
- List the stale loads (no update in 24 hours) by load ID and carrier so the team can chase them
- Include the total vehicles in motion and total delivered today
Done when The Slack digest is posted and the ops team can see the full fleet status at a glance.
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 message drivers or customers with status updates?
No. The digest goes only to your internal Slack ops channel. Driver or customer notifications are not sent by WebRun automatically.
What counts as a stale load?
Any load with no status change in Super Dispatch for more than 24 hours is flagged as stale. You can adjust this threshold when configuring the workflow.
Can it break down the digest by driver or lane?
Yes. Ask WebRun to group the summary by driver, region, or origin-destination lane when you set up the workflow and it will reshape the digest accordingly.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.