Automated AfterShip Delivery Exception Alerts
Every morning, WebRun opens AfterShip, finds shipments sitting in exception or with no tracking movement past your stall threshold, writes each one to a Google Sheet with its carrier and last scan, and drafts a plain Gmail update to the customer that waits in Drafts for your approval.
How do I find stuck shipments before customers start complaining?
WebRun opens AfterShip each morning and finds shipments in exception or with no carrier scan past your stall threshold. It logs each one to Google Sheets with the carrier, last scan, and days stalled, then drafts a plain Gmail update to the customer that waits in Drafts for your approval.
- Stalled parcels surface days before a complaint arrives
- Every customer update is approved by a human before sending
- Carrier-wide delays are visible in the daily per-carrier count
Built for ecommerce stores · 3PL teams · customer support · operations managers
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
aftership.comin a real browser with your saved login - no setup, no API keys. -
1
AfterShip - find stalled and exception shipments
aftership.com
WebRun opens AfterShip to find stalled and exception shipments. - Open AfterShip and filter shipments to exception and in transit
- Capture anything with no new tracking scan for longer than your stall threshold
- Note the tracking number, carrier, destination, last scan date, and order reference
- Group by carrier so a single carrier problem is obvious
- Skip shipments already flagged and chased this week
Done when Every stalled or exception shipment is listed with its carrier and last scan.
-
2
Google Sheets - log the problem parcels
google.com
WebRun opens Google Sheets to log the problem parcels. - Open your delivery exceptions sheet and add today's rows
- Write one row per shipment with order, customer, carrier, last scan, and days stalled
- Sort by days stalled so the oldest problem sits at the top
- Add a small per-carrier count so a systemic delay is visible
Done when Today's stalled shipments are logged and sorted by age.
-
3
Gmail - draft the customer update
gmail.com
WebRun opens Gmail to draft the customer update. - Draft a short, honest update to each affected customer with the order and tracking link
- Say what the carrier last reported and what happens next
- Leave every message in Drafts for a human to read and send. Nothing is emailed on its own
- Skip customers who already received an update about the same order
Done when A customer update is drafted and waiting for every stalled shipment.
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 email customers without me?
No. Every update sits in Gmail Drafts until a human reads and sends it, so no customer hears anything about their parcel unless you approve the wording first.
What counts as a stalled shipment?
Any shipment AfterShip marks as an exception, plus anything in transit with no new carrier scan for longer than the number of days you set, commonly 3 to 5 days.
Will the same order be chased twice?
No. WebRun checks the log before drafting and skips any order already flagged and updated that week, so a slow parcel produces one message, not five.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.