Compile a daily damage and rejection digest
Each evening, WebRun reads the day's deliveries in Deliveright Grasshopper, tallies damages, rejections, and refusals by cause and route, writes the numbers to a running Google Sheet, and posts a plain-English digest to Slack so ops can see problem patterns at a glance.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically compile a daily delivery damage and rejection report?
Each evening WebRun reads the day's deliveries in Deliveright Grasshopper, tallies damages, rejections, and refusals by cause, route, and crew, and appends the totals to a running Google Sheet scoreboard. It then posts a plain-English digest to Slack with the top causes and any outlier route, so ops spots problem patterns the same night they happen.
- Ops sees the day's damage and rejection totals every evening
- Problem routes and crews surface against the trailing week
- The scoreboard builds a trend line without manual tallying
Built for final mile operations · white glove carriers · quality managers · furniture logistics
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
deliveright.comin a real browser with your saved login - no setup, no API keys. -
1
Deliveright - tally damages and rejections
WebRun opens Deliveright to tally damages and rejections. - Open Deliveright Grasshopper and pull today's completed and exception stops
- Count damages, rejections, and refusals, grouped by cause and route
- Note the orders and crews behind each exception
Done when Today's exceptions are counted by cause and route.
-
2
Google Sheets - update the scoreboard
WebRun opens Google Sheets to update the scoreboard. - Append today's totals to the running damage and rejection scoreboard
- Break the numbers out by cause, route, and crew
- Compare against the trailing week so trends are visible
Done when The scoreboard holds today's totals alongside the recent trend.
- 3
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 this message customers or retailers?
No. The digest is a purely internal summary posted to your own Slack channel and a Google Sheet. It never contacts a customer, retailer, or crew member directly, so it is safe to run unattended.
Can it show whether damage is trending up?
Yes. It appends each day's totals to a running scoreboard and compares against the trailing week, so the Slack digest can flag when a route or crew climbs above its usual exception rate.
Where do the numbers come from?
From the completed and exception stops in Deliveright Grasshopper for the day. WebRun counts the actual damage, rejection, and refusal flags rather than any manual tally.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.