Stay on top of every open carrier claim for returned shipments
Every Monday, WebRun checks ReverseLogix for returns flagged as damaged in transit, cross-references open claim IDs in your Google Sheet, and posts a Slack update showing which claims are still open, recently closed, or overdue for follow-up.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically track open carrier claims for damaged returned shipments?
WebRun checks ReverseLogix every Monday for returns flagged as damaged in transit, logs each one to a Google Sheets claim tracker, and posts a Slack summary of open, overdue, and newly identified claims. Teams recover value from carrier damages faster because no claim sits untracked for weeks.
- Every transit-damage claim is logged and tracked from the day it is received
- Claims overdue for follow-up are flagged before the value window closes
- Logistics team sees a weekly claim status digest without building it manually
Built for logistics operations teams · returns managers · 3PL providers · e-commerce brands shipping high-value goods
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
app.reverselogix.comin a real browser with your saved login - no setup, no API keys. -
1
ReverseLogix - pull transit-damaged return flags
reverselogix.com How to Automate ReverseLogix
WebRun opens ReverseLogix to pull transit-damaged return flags. - Open ReverseLogix and filter returns with a disposition reason of damaged-in-transit
- Capture the return ID, SKU, carrier, declared value, and date received for each
- Identify any new damaged returns not yet assigned a claim ID
Done when All transit-damaged returns are listed with carrier, value, and claim assignment status.
-
2
Google Sheets - cross-reference open claim IDs
google.com How to Automate Google Sheets
WebRun opens Google Sheets to cross-reference open claim IDs. - Open the carrier claim tracker sheet
- Add new rows for any unassigned transit-damaged returns flagged in ReverseLogix
- Update the status column for claims whose age exceeds your follow-up window
Done when The claim tracker sheet is updated with all known transit-damaged returns and their current status.
-
3
Slack - post claim status update
slack.com How to Automate Slack
WebRun opens Slack to post claim status update. - Post a weekly carrier claim status update to the logistics Slack channel
- List open claims with value at risk, claims needing follow-up, and any new claims opened this week
Done when The logistics team has a current claim status summary in Slack.
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 file a carrier claim on my behalf?
No. Filing a claim with the carrier is an action WebRun leaves to your team. It identifies which returns need a claim opened and logs them to the sheet for follow-up.
Which carriers does it track?
It tracks whatever is recorded in ReverseLogix as the inbound carrier for damaged returns. As long as the carrier name is in the return record, WebRun can surface it.
How old does a claim need to be before it is flagged as overdue?
You set the follow-up window during setup, for example 10 business days with no status update. WebRun flags anything older than that threshold in the sheet and in the Slack post.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.