Deliveright Automated Damage Issue Logging
As crews close out stops, WebRun reads the damage photos and notes captured at handoff in Deliveright Grasshopper, opens a numbered issue row per affected order in a Google Sheet, and posts the claims channel in Slack a short summary with the photo links.
How do I automatically log delivery damage photos into an issue tracker?
WebRun reads the damage photos and crew notes captured at handoff in Deliveright Grasshopper, opens a numbered issue row per affected order in a Google Sheet with the photo links, and posts a short summary to your claims channel in Slack. Damage gets documented and routed to claims within minutes of the crew closing the stop.
- Every damaged order gets a numbered issue within minutes of handoff
- Photos and crew notes live in one searchable log, not scattered
- Claims see new damage in Slack the moment a crew flags it
Built for white glove delivery teams · claims coordinators · furniture retailers · final mile carriers
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 - read handoff damage photos
deliveright.com
WebRun opens Deliveright to read handoff damage photos. - Open Deliveright Grasshopper and find stops closed with a damage or exception flag
- Collect the photos, the crew's note, and the item or SKU affected
- Skip orders already logged as an issue this run
Done when Every flagged handoff has its photos and notes gathered.
-
2
Google Sheets - open a numbered issue row
google.com
WebRun opens Google Sheets to open a numbered issue row. - Add a row to the damage log with a new issue number, order, item, and crew note
- Paste the photo links into the row
- Set the status to Open and stamp the delivery date
Done when Each damaged order has one Open issue row with photos attached.
-
3
Slack - alert the claims channel
slack.com
WebRun opens Slack to alert the claims channel. - Post the issue number, order, and a one-line damage summary to the claims channel
- Attach the photo links for a fast first look
Done when The claims team sees every new damage issue in Slack as it opens.
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 contact the customer or retailer about the damage?
No. It only logs the issue internally in a Google Sheet and posts your claims channel in Slack. Any message to a customer or retailer is authored separately by a person who reviews the photos first.
Where do the damage photos come from?
From the handoff record the crew captures in Deliveright Grasshopper. WebRun reads those exact photos and notes, so the issue log matches what happened at the door.
Will the same order get logged twice?
No. It checks each order against the existing issue rows before writing, so a stop already logged this run is skipped rather than duplicated.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.