Automated LigoLab Pending Case Follow-Up
Every morning, WebRun opens LigoLab, identifies cases that have been in a pending status longer than their workflow target, and posts a prioritized Slack digest so lab staff can investigate and move each stuck case forward before client inquiries arrive.
How do I automatically identify and follow up on pending LigoLab cases that have stalled?
WebRun reviews LigoLab every morning for cases stuck in pending status beyond their expected completion window, then posts a prioritized Slack digest ranked by elapsed overage. Lab staff start each day with a clear follow-up list, catching stalled cases before clients call to ask about them.
- Stalled cases surfaced every morning before client calls arrive
- Oldest overdue cases ranked first so the most urgent work is done first
- No manual worklist review needed, saving supervisors time each morning
Built for pathology lab supervisors · lab operations managers · clinical laboratory directors
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.ligolab.comin a real browser with your saved login - no setup, no API keys. -
1
LigoLab - find cases stuck in pending status
WebRun opens LigoLab to find cases stuck in pending status. - Open LigoLab and filter for cases with a pending or in-progress status
- Calculate elapsed time for each case and compare it to the expected completion window by case type
- Flag cases that have exceeded their target window by more than 25 percent
- Sort by elapsed overage, listing the oldest stalled cases first
Done when All cases that have stalled beyond their completion target are identified and sorted by urgency.
-
2
Slack - post stalled-case follow-up list
WebRun opens Slack to post stalled-case follow-up list. - Post the stalled-case list to the lab follow-up Slack channel
- Include accession number, case type, ordering client, elapsed time, and expected completion window
- List the oldest overdue cases first for immediate attention
Done when The lab team has a morning follow-up list in Slack with every stalled case ranked by 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 contact the ordering client or patient about a delay?
No. The Slack list is internal only. Any client or patient communication about a pending case must be drafted and approved by a human staff member before sending.
How does it determine which cases are stalled?
WebRun compares each case's elapsed time against the expected completion window for that case type as configured in LigoLab. Cases exceeding the target by more than 25 percent are flagged.
What if a case is pending because it is awaiting additional clinical information?
WebRun flags it based on time elapsed, not the reason. The lab team uses the Slack list as a starting point and can investigate each case to determine the actual cause of the delay.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.