Assemble a proof-of-delivery packet for each hospital
Every Monday, WebRun opens CXT Software, pulls the signed proof-of-delivery records for each hospital account from last week, compiles a clean per-hospital packet in Google Sheets, and drafts the delivery email in Gmail for your team to review and send.
- No credit card
- Under $0.01 per run
- Cancel anytime
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
www.cxtsoftware.comin a real browser with your saved login - no setup, no API keys. -
1
CXT Software - gather signed proof-of-delivery records
WebRun gathers each hospital's signed proof-of-delivery records from CXT Software. - Open CXT Software and filter last week's completed deliveries by hospital account
- For each delivery, capture the signature capture, the delivery timestamp, and the barcode custody record
- Group the records under each hospital
- Note any delivery missing a signature so it can be resolved before the packet goes out
Done when Every hospital has its complete set of signed proof-of-delivery records for the week.
-
2
Google Sheets - compile the per-hospital packet
WebRun compiles a clean proof-of-delivery packet per hospital in the workbook. - Open the Proof of Delivery Packet workbook
- Build a clean tab per hospital listing each delivery, its timestamp, signer, and custody reference
- Add a summary line with the total deliveries and any records still missing a signature
- Format it so the packet is presentable to the hospital
Done when A tidy proof-of-delivery packet exists per hospital in the workbook.
-
3
Gmail - draft the delivery email for approval
WebRun drafts each hospital's POD delivery email and leaves it unsent. - Draft a short cover email to each hospital contact linking or attaching its packet
- Keep the note limited to delivery records, with no patient identifiers beyond what the hospital already holds
- Leave every email as an unsent draft for your team to review and send
Done when A delivery email is drafted per hospital and left unsent for review.
How do I compile a weekly proof-of-delivery packet for each hospital?
Every Monday WebRun pulls each hospital's signed proof-of-delivery records from CXT Software, capturing signatures, timestamps, and barcode custody references. It compiles a clean per-hospital packet in Google Sheets, flags any delivery missing a signature, and drafts the delivery email in Gmail for your team to approve, so accurate POD packets go out reviewed, never automatically.
- Each hospital gets a tidy weekly POD packet
- Deliveries missing a signature are flagged before sending
- Every delivery email is reviewed before it goes out
Built for medical courier operations · lab logistics billing · hospital account managers · courier compliance teams
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 the packet be emailed to the hospital automatically?
No. WebRun compiles the packet and drafts the cover email, then leaves it as an unsent Gmail draft for your team to review and send. Nothing reaches a hospital until a human approves it.
How does it handle deliveries missing a signature?
It flags any delivery without a captured signature in both the CXT Software pull and the packet summary, so your team can resolve the gap before the proof-of-delivery packet goes out.
Does the packet expose patient data?
No. The packet is built from delivery records: timestamps, signers, and custody references. WebRun keeps it limited to logistics detail and does not add patient identifiers beyond what the hospital already holds.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.