Send drivers their route details before every morning dispatch
Each morning before dispatch, WebRun opens Encompass, pulls finalized delivery routes for the day, and sends each driver a Twilio SMS with their route number, stop count, first stop address, and estimated departure time, then posts a dispatch summary to your logistics Slack channel confirming all drivers have been notified.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically send drivers their delivery route details each morning?
WebRun opens Encompass each morning, pulls every finalized delivery route, and sends each driver a Twilio SMS with their route number, stop count, first stop address, and departure time. It then posts a dispatch confirmation to Slack listing every driver notified and flagging any SMS delivery failures for immediate manual follow-up by the logistics team.
- Every driver has their route details on their phone before they reach the warehouse
- Failed SMS alerts flagged in Slack so no driver goes out uninformed
- Logistics team gets a full dispatch confirmation with stop counts before routes depart
Built for foodservice distributors · broadline distributors · logistics managers · dispatch 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
app.encompasstech.comin a real browser with your saved login - no setup, no API keys. -
1
Encompass - pull finalized delivery routes for the day
WebRun opens Encompass to pull finalized delivery routes for the day. - Open Encompass and navigate to today's delivery route plan
- Confirm which routes are finalized and ready for dispatch
- Capture route number, assigned driver name, driver mobile number, stop count, first stop address, and scheduled departure time for each route
Done when All finalized routes for today have driver details and route summaries captured.
-
2
Twilio - send each driver their route SMS
WebRun opens Twilio to send each driver their route SMS. - Send each driver an SMS with their route number, stop count, first stop address, and departure time
- Keep the message under 160 characters for single-part SMS delivery
- Log the delivery status (sent, failed) for each driver message
Done when Every driver on a finalized route has received their route SMS, or a failure is logged for manual follow-up.
-
3
Slack - post dispatch confirmation to logistics channel
WebRun opens Slack to post dispatch confirmation to logistics channel. - Post a dispatch confirmation to the logistics channel listing all routes and their drivers
- Flag any drivers whose SMS failed so dispatch can call them directly
- Include the total number of routes, stops, and departure time window
Done when Logistics team has a full dispatch confirmation in Slack including any SMS delivery failures.
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
What if a driver's phone number is missing or wrong in Encompass?
WebRun logs that driver's SMS as failed and flags it in the Slack dispatch summary so the logistics team can call the driver directly before their route departs.
What if a route is not yet finalized when the run starts?
WebRun only sends confirmations for routes marked as finalized in Encompass. Unfinalized routes are listed in the Slack summary as pending so dispatch knows to finalize and follow up manually.
Can the SMS message include more than one stop's address?
The default message includes only the first stop to stay within 160 characters for reliable single-part delivery. For multi-stop details, the Slack summary includes the full stop count and route context.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.