All templates

Automated Clinisys Result Delivery Failures

Every hour, WebRun opens Clinisys, finds results that failed to deliver to the ordering provider's EMR, portal, or fax, texts your client services rep to call the practice, drafts a backup email for review if the failure is still open after two hours, and logs every failure to a Google Sheet until it's resolved.

Runs on WebRun · Strict Lockdown policy
Every hour, around the clock WebRunorchestrates each step
1 Clinisys find results that failed to deliver
2 Twilio text client services to call the practice
3 Gmail draft a backup notice if unresolved
4 Google Sheets log every failure until resolved
In short

How do I catch a failed lab result delivery before the provider notices it's missing?

WebRun checks Clinisys every hour for results that failed to reach the ordering provider's EMR, portal, or fax, and texts your client services rep to call the practice. If a failure is still open two hours later, it drafts a backup notice in Gmail for review, and logs every failure to a Google Sheet until Clinisys shows it delivered.

  • Client services is paged before the practice ever notices a result is missing
  • A backup notice is ready to send if a failure lingers past two hours
  • Every failure is tracked to resolution instead of getting lost in the interface queue

Built for lab client services teams · interface and IT support · hospital outreach lab managers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.clinisys.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Clinisys - find results that failed to deliver
    clinisys.com
    WebRun in Clinisys: find results that failed to deliver
    WebRun opens Clinisys to find results that failed to deliver.
    • Open Clinisys and filter results marked as a failed or pending delivery to the ordering provider
    • Check whether the delivery method was EMR interface, portal, or fax
    • Note how long the result has been undelivered

    Done when Every undelivered result from this run is listed with its delivery method and how long it's been stuck.

  3. 2
    Twilio - text client services to call the practice
    twilio.com
    WebRun in Twilio: text client services to call the practice
    WebRun opens Twilio to text client services to call the practice.
    • Text your internal client services rep the order, the provider, and how long delivery has failed
    • Send only to your internal client services line, never to the practice directly
    • Mark the page sent so it isn't repeated for the same failure

    Done when Client services has been paged for every result failing delivery.

  4. 3
    Gmail - draft a backup notice if unresolved
    gmail.com
    WebRun in Gmail: draft a backup notice if unresolved
    WebRun opens Gmail to draft a backup notice if unresolved.
    • If a result is still undelivered two hours after the first page, draft a short notice to the practice's office manager
    • Leave the draft unsent in Gmail for your client services rep to review and send
    • Never send the notice, or the result itself, automatically

    Done when A backup draft exists for every delivery failure still open after two hours.

  5. 4
    Google Sheets - log every failure until resolved
    google.com
    WebRun in Google Sheets: log every failure until resolved
    WebRun opens Google Sheets to log every failure until resolved.
    • Log the order, provider, delivery method, and time first flagged
    • Mark a row resolved once Clinisys shows the result delivered
    • Keep a running count of failures by delivery method to spot a pattern

    Done when Every failure from this run has a row, open or resolved, in the tracking log.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.clinisys.com
ScheduleRuns automatically on this cadence
Every hour, around the clock
DeliveryHow each run's result reaches you
Failure log · Google Sheets
OutputWhat each run produces - A tracked list of results stuck in delivery, how long they've been stuck, and whether a backup notice has been drafted.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it email the practice about a failed result on its own?

No. WebRun drafts the backup notice and leaves it unsent in Gmail. Your client services rep reviews and sends it, and the result itself is never included in the draft.

Who gets contacted first when a delivery fails?

Your internal client services rep, by text, so a person can call the practice directly. The practice only hears from WebRun's draft if the failure is still open two hours later.

How does it know a failure is resolved?

It reads the live delivery status in Clinisys every run, so a result that goes through is marked resolved automatically and drops off the active list.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.