Automated OPIE Software Proof of Delivery Collection
Every morning, WebRun opens OPIE Software, finds every device marked as delivered in the past 30 days that is missing a signed proof-of-delivery document, and posts a prioritized collection worklist to Slack so billing staff can gather the signatures needed before submitting claims.
How do I automatically track missing proof-of-delivery documents in OPIE Software?
WebRun checks OPIE Software every morning for device deliveries in the past 30 days that are missing a signed proof-of-delivery document, then posts a prioritized collection worklist to Slack sorted by days outstanding. Billing staff see which PODs to chase that day and which are blocking a queued claim, before a single claim goes out incomplete.
- No claim goes out missing a proof-of-delivery because the gap is surfaced every morning
- Oldest missing PODs appear first so billing staff work in priority order
- Queued claims with missing PODs are flagged as critical before submission
Built for O&P billing coordinators · practice managers · prosthetics and orthotics front-office teams
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.opiesoftware.comin a real browser with your saved login - no setup, no API keys. -
1
OPIE Software - find deliveries missing proof-of-delivery documents
opiesoftware.com
WebRun opens OPIE Software to find deliveries missing proof-of-delivery documents. - Open OPIE Software and filter delivered device records from the past 30 days
- Identify any delivery without a completed proof-of-delivery document attached
- Capture patient name, device type, delivery date, clinician, and days since delivery
- Sort by days since delivery so the oldest missing PODs appear first
Done when Every delivered device missing a signed POD is listed with days outstanding and responsible clinician.
-
2
Slack - post POD collection worklist
slack.com
WebRun opens Slack to post POD collection worklist. - Post the POD collection worklist to the billing channel
- List each case with patient, device, delivery date, and days missing
- Flag any item with a claim already queued as critical so it is resolved before submission
Done when Billing staff have a daily POD worklist in Slack showing every missing signature and its urgency.
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 document requests to patients automatically?
No. WebRun posts an internal worklist to Slack for billing staff to action. Any outreach to a patient to gather a signature requires a staff member to initiate it.
How does it know a proof-of-delivery is missing?
It checks whether a signed POD document is attached to the delivery record in OPIE. Any delivery without a completed attachment is added to the worklist.
What if the POD was collected but not yet uploaded to OPIE?
Once a staff member uploads the document to the OPIE record, it will no longer appear on the next morning's worklist. The list is always based on what is in OPIE at run time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.