Automated Intermodal Cargo Claim Tracking
Every Monday, WebRun reviews open cargo claims in Rail Command and the claims tracker in Google Sheets, identifies any claim without a carrier response in over 30 days, drafts a follow-up letter in Gmail for your review, and updates the tracker with the latest claim status.
How do I track intermodal cargo claims and follow up on unresolved ones automatically?
WebRun reviews open intermodal cargo claims in Rail Command and a Google Sheets tracker every Monday, flags any claim without a carrier response in over 30 days, and drafts a follow-up letter in Gmail for your review. The claims tracker is updated each run so your team has a live view of every open claim.
- Every open claim is reviewed weekly and overdue ones are flagged immediately
- Follow-up letters are pre-drafted so chasing takes seconds, not an afternoon
- The claims tracker gives management a live view of total exposure at any time
Built for intermodal claims managers · freight loss and damage teams · logistics finance departments · rail operations coordinators
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
railinfo.rsilogistics.comin a real browser with your saved login - no setup, no API keys. -
1
RSI Logistics Rail Command - pull open cargo claim records
rsilogistics.com
WebRun opens RSI Logistics Rail Command to pull open cargo claim records. - Open Rail Command and navigate to freight or cargo claim records
- Pull all claims with an open or pending status
- For each claim, capture the claim number, carrier, filed date, claimed amount, and last response date
Done when All open cargo claims are listed with their carrier, filed date, and last response date.
-
2
Google Sheets - update claims tracker with latest status
google.com
WebRun opens Google Sheets to update claims tracker with latest status. - Open the cargo claims tracker sheet and update the status row for each open claim
- Add a new row for any claim not yet in the tracker
- Flag any claim filed more than 30 days ago with no carrier response as overdue
Done when The Google Sheets tracker reflects the current status of every open claim.
-
3
Gmail - draft follow-up letter to unresponsive carriers
gmail.com
WebRun opens Gmail to draft follow-up letter to unresponsive carriers. - Draft a follow-up letter to the carrier for each claim marked overdue in the tracker
- Reference the claim number, filed date, claimed amount, and shipment details in the letter
- Leave every draft in Drafts for your review. Do not send without approval
Done when A review-ready follow-up draft exists in Gmail for each overdue cargo claim.
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 send follow-up letters to carriers automatically?
No. Every follow-up letter is saved as a Gmail draft for your review. Nothing is sent to a carrier until you approve it, which is important given the legal nature of cargo claims.
How does it know whether a carrier has responded?
It reads the last response date field in Rail Command and in the Google Sheets tracker. Your team should update the tracker when a carrier responds so the next run correctly skips resolved claims.
Can it track claims against multiple carriers at the same time?
Yes. It processes each open claim independently, so claims against different carriers are tracked and followed up separately with the correct carrier contact for each.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.