Automated Proof of Delivery Chaser for Carriers
Every morning, WebRun cross-references completed loads in J. J. Keller Encompass against your delivery records, identifies every load missing a signed proof of delivery, logs the gap to a Google Sheet, and drafts a POD chase email in Gmail for your dispatcher to review and send.
How do I automatically chase missing proof-of-delivery documents after loads are delivered?
WebRun checks J. J. Keller Encompass every morning for completed loads with no signed proof-of-delivery document, logs each gap to a Google Sheet chase tracker, and drafts a POD request email in Gmail for your dispatcher to review before sending, so missing documents are chased promptly and invoices are not held up.
- Missing PODs are caught and chased within 24 hours of delivery
- Dispatcher sees a daily list of outstanding documents before billing runs
- POD requests only go out after dispatcher review and approval
Built for carrier dispatchers · transportation operations managers · fleet compliance coordinators · trucking company owners
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
encompass.jjkeller.comin a real browser with your saved login - no setup, no API keys. -
1
J. J. Keller Encompass - find completed loads missing a signed POD
jjkeller.com
WebRun opens J. J. Keller Encompass to find completed loads missing a signed POD. - Open the compliance and load records in Encompass and filter for deliveries completed in the last 48 hours
- Identify any load with a delivered status but no scanned or uploaded proof-of-delivery document
- Capture load number, driver name, broker or shipper contact, delivery date, and destination
Done when Every load delivered in the last 48 hours with a missing POD is listed with contact details.
-
2
Google Sheets - log each missing POD to the chase tracker
google.com
WebRun opens Google Sheets to log each missing POD to the chase tracker. - Open the POD Chase Tracker sheet and append a row for each missing POD
- Record load number, driver, delivery date, broker contact, and chase status
- Mark loads more than 24 hours past delivery with no POD as urgent
Done when The POD chase tracker is updated with all new missing documents.
-
3
Gmail - draft POD chase email for dispatcher review
gmail.com
WebRun opens Gmail to draft POD chase email for dispatcher review. - Draft a polite POD request email to the driver or broker for each missing document
- Include the load number, delivery date, and a request to upload or email the signed POD
- Leave every draft unsent for your dispatcher to review and approve before sending
Done when Gmail drafts are ready for dispatcher review for every missing POD older than 24 hours.
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 the POD chase emails to drivers or brokers automatically?
No. WebRun drafts all chase emails in Gmail and leaves them unsent. Your dispatcher reviews each draft and decides which ones to send, keeping outreach under human control.
How far back does it look for missing PODs?
WebRun checks deliveries completed in the last 48 hours by default, so each morning it catches anything missed yesterday or the day before. The lookback window can be adjusted.
What happens once the POD is received and uploaded?
WebRun reads the live document status in J. J. Keller Encompass each morning, so any load where the POD has been uploaded is removed from the chase list automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.