Automated Onfleet Delivery Exception Alerts
Every morning, WebRun opens Onfleet, pulls all tasks marked Failed from the previous day, captures each exception reason, recipient address, and driver note, then posts a ranked reattempt worklist to Slack so dispatchers can reroute before the next run.
How do I automatically track and action failed delivery exceptions in Onfleet?
WebRun opens Onfleet each morning, collects every task marked Failed from the prior day, and ranks them by failure reason. It then posts a prioritized reattempt list to Slack, giving your dispatch team a clear action list before the next route window opens, so no failed stop slips through unworked.
- Every failed stop is visible to dispatch before the next route window
- Ranked by failure type so address errors get fixed first
- No manual log-checking - exceptions surface in Slack automatically
Built for last mile delivery operators · courier companies · food delivery fleets · e-commerce fulfillment 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
onfleet.com/dashboardin a real browser with your saved login - no setup, no API keys. -
1
Onfleet - pull failed tasks from prior day
onfleet.com
WebRun opens Onfleet to pull failed tasks from prior day. - Open Onfleet and filter Tasks to Completed status Failed from the prior calendar day
- Capture the task ID, recipient name, address, failure reason code, and any driver note for each
- Sort by failure type: address issue first, then access problem, then refused delivery
Done when Every failed task from the prior day is listed with its reason and recipient details.
-
2
Slack - post ranked reattempt worklist
slack.com
WebRun opens Slack to post ranked reattempt worklist. - Post the ranked reattempt list to the dispatch Slack channel
- Lead each line with failure reason so the team knows what action is needed
- Include the original task ID so dispatchers can reopen and reroute directly in Onfleet
Done when Dispatchers have a ranked reattempt list in Slack before the next route run.
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 notify the recipient about the failed delivery automatically?
No. Customer-facing messages are drafted for human review, never sent automatically. The Slack digest is internal only, so dispatchers decide when and how to contact the recipient.
How does it rank the reattempt list?
Address errors and access problems appear first because they need dispatcher action before rerouting. Refused deliveries and other reason codes follow in order of age so the oldest exceptions get cleared first.
What if the same address fails two days in a row?
Each run pulls the prior day's failures fresh from Onfleet, so repeat failures appear again automatically. Your team can use the task ID to annotate the Onfleet record with escalation notes.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.