Automated Courier SLA Breach Alerts
Every few minutes, WebRun opens Onfleet, checks all active tasks against your configured SLA windows, identifies any that are at risk or already in breach, and immediately posts a structured alert to your dispatch Slack channel so the team can intervene.
How do I automatically get alerted when a delivery is about to breach its SLA?
WebRun checks every active Onfleet task against your SLA windows every few minutes, flags deliveries approaching or past their committed window, and posts a structured Slack alert with the driver, zone, and delay details. Dispatchers see a live SLA risk board without logging into Onfleet manually.
- SLA risks surface in Slack within minutes, not at end-of-day reporting
- Dispatchers see a live board of breached and at-risk deliveries without checking Onfleet manually
- No SLA breach goes unnoticed before the customer complains
Built for courier dispatch managers · last-mile logistics operators · fleet supervisors · delivery SLA compliance 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 - check tasks against SLA windows
onfleet.com
WebRun opens Onfleet to check tasks against SLA windows. - Open Onfleet and review all active and in-progress tasks
- Compare the current time and task progress against each task's committed delivery window
- Classify each at-risk task as: approaching SLA (within 30 minutes of window end) or breached (past window end)
- Capture the task ID, recipient, driver, zone, and the extent of delay for each flagged task
Done when Every at-risk or breached task is identified and classified with its delay details.
-
2
Slack - post breach alert
slack.com
WebRun opens Slack to post breach alert. - Post a structured alert to the dispatch Slack channel, separating breached tasks from at-risk tasks
- List each flagged task with the driver name, recipient, zone, and minutes late or at risk
- Repeat the alert if a previously at-risk task transitions to breach in a subsequent run
Done when Dispatchers have an up-to-date SLA risk board in Slack that refreshes every few minutes.
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
How far in advance does it flag a delivery that is approaching the SLA window?
By default, WebRun flags tasks within 30 minutes of their committed window end. You can adjust this threshold to match your operation, for example 15 or 45 minutes.
Does it contact the customer when an SLA is breached?
No. WebRun only posts internal Slack alerts to your dispatch team. Any outreach to the customer is handled separately, using the draft-and-review workflow.
Will it alert me about the same breach multiple times?
Once a task is flagged, it continues to appear in Slack alerts until it is marked complete in Onfleet. Separate categories for approaching and breached help dispatchers track what is newly flagged versus ongoing.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.