Automated AfterShip Carrier Scorecards
Every Monday, WebRun opens AfterShip, reads the last seven days of trackings, groups them by courier and destination, works out average transit time and exception rate for each, sends the scorecard to your operations WhatsApp, and opens a Trello card for the courier and lane performing worst.
How do I compare courier delivery performance each week?
WebRun scores your couriers every Monday. It reads the last seven days of AfterShip trackings, groups them by courier and destination, calculates average transit time and exception rate for each, sends the scorecard to WhatsApp, and opens a Trello card for the worst performing lane.
- The next carrier conversation has a week of numbers behind it
- Slow lanes show up as lanes, not as a courier-wide average
- Exception rates are tracked weekly instead of felt anecdotally
Built for operations managers · ecommerce merchants · logistics teams · 3PL partners
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 - score every courier
WebRun opens AfterShip to score every courier. - Open AfterShip and filter trackings to the last seven days
- Group them by courier and by destination country or region
- Work out average transit time from pickup to delivery for each group
- Count exceptions and failed attempts per courier and turn them into a rate
Done when Every courier has an average transit time and an exception rate for the week.
-
2
WhatsApp - send the scorecard
WebRun opens WhatsApp to send the scorecard. - Send the scorecard to your operations chat, one line per courier
- Show transit time and exception rate next to last week's figures
- Call out any courier whose exception rate moved by more than your threshold
Done when The operations chat has this week's courier scorecard.
-
3
Trello - card the worst lane
WebRun opens Trello to card the worst lane. - Open a Trello card for the courier and destination pairing with the worst week
- Put the transit time, exception rate, and the affected order count on the card
- Attach the previous four weeks so the trend is on the card for the carrier conversation
- Never contact a courier or a customer: WebRun prepares the numbers, a person raises the issue
Done when The worst-performing lane has a card with the numbers behind it.
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 contact couriers or customers?
No. WebRun reads trackings and reports the numbers to your own team. Raising a claim with a courier or updating a customer stays with your operations team.
How is this different from chasing a stuck parcel?
It aggregates instead of reacting. Stuck-parcel chasing works one shipment at a time. This reads a whole week and scores each courier and destination so patterns show, not single incidents.
Can it split the scorecard by destination?
Yes. Every courier is scored per destination country or region, so a carrier that is fine domestically and slow on a specific lane shows up as that lane rather than an average.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.