Chase missing proof of delivery so your invoices never sit unpaid
Every morning, WebRun opens PortPro, finds all loads marked as delivered but missing a proof of delivery document, notes the driver, customer, and load details for each, and posts a follow-up worklist to your billing Slack channel so PODs are collected before invoices are issued.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically find and chase missing proof of delivery in PortPro?
WebRun opens PortPro every morning, finds every delivered load that is still missing a proof of delivery document, and posts a Slack worklist to your billing team sorted by delivery date so the oldest outstanding PODs are chased first and invoicing is never held up by missing paperwork.
- Billing team chases PODs every morning, not when invoices are overdue
- Oldest missing PODs surfaced first so the longest delays are cleared first
- Invoicing delays from missing paperwork reduced to near zero
Built for drayage carriers · port trucking billing teams · drayage operations managers · intermodal logistics 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
app.portpro.ioin a real browser with your saved login - no setup, no API keys. -
1
PortPro - find delivered loads missing POD
portpro.io How to Automate PortPro
WebRun opens PortPro to find delivered loads missing POD. - Open PortPro and filter loads to status Delivered with no POD document attached
- Read the driver name, customer, container number, and delivery date for each missing POD
- Flag loads where delivery was more than 48 hours ago as overdue for immediate follow-up
Done when Every delivered load missing a POD is listed with driver, customer, and delivery date.
-
2
Slack - post POD follow-up worklist to billing team
slack.com How to Automate Slack
WebRun opens Slack to post POD follow-up worklist to billing team. - Post the missing-POD worklist to the billing Slack channel
- Sort by delivery date ascending so the oldest missing PODs appear first
- Flag overdue items (48 hours without POD) as high-priority
Done when Billing team has today's missing-POD follow-up worklist 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 send a reminder directly to the driver to submit the POD?
No. WebRun posts an internal worklist to your billing team. Any driver-facing follow-up message is drafted for your review before it is sent.
What if the POD was uploaded but not attached to the load in PortPro?
The worklist flags loads where no POD document is attached in PortPro. Your team can then check the driver app or email and attach it manually so the load clears the list on the next run.
How many days back does it look for missing PODs?
By default it looks back 7 days. Tell WebRun a different window and it will adjust the lookback period to match your invoicing cycle.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.