All templates

Automated Porter Dispatch Queue Digest

Every hour, WebRun opens Patient Focused Systems, counts how many trips are pending, assigned, and in progress, logs the snapshot to a Google Sheet queue log, and posts your charge nurse a Slack digest naming the longest-waiting requests so nothing sits forgotten in the queue.

Runs on WebRun · Strict Lockdown policy
Every hour, on the hour WebRunorchestrates each step
1 Patient Focused Systems snapshot the dispatch queue
2 Google Sheets log the hourly queue counts
3 Slack digest the longest waits
In short

How do I get an hourly digest of the porter dispatch queue?

WebRun opens Patient Focused Systems every hour, counts how many transport trips are pending, assigned, and in progress, and logs the snapshot to a Google Sheet queue log. It then posts your charge nurse a Slack digest naming the longest-waiting requests, so dispatch always has a quick read on queue health without watching the live board all day.

  • Charge nurse gets a queue health check every hour without watching the live board
  • 30 days of queue history logged automatically for trend review
  • Requests waiting more than 20 minutes are flagged the same hour

Built for charge nurses · patient transport supervisors · hospital dispatch coordinators · transport department 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 patientfocussystems.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Patient Focused Systems - snapshot the dispatch queue
    patientfocussystems.com
    WebRun in Patient Focused Systems: snapshot the dispatch queue
    WebRun opens Patient Focused Systems to snapshot the dispatch queue.
    • Open the dispatch queue and count trips by status: pending, assigned, in progress
    • Find the request that has been waiting longest in each status
    • Capture the requesting unit and wait time for the longest-waiting requests

    Done when This hour's queue counts and longest waits are captured.

  3. 2
    Google Sheets - log the hourly queue counts
    google.com
    WebRun in Google Sheets: log the hourly queue counts
    WebRun opens Google Sheets to log the hourly queue counts.
    • Open the Porter Queue Log sheet
    • Append a new row with the hour, and the pending, assigned, and in-progress counts
    • Keep a rolling 30-day history for trend review

    Done when The queue log sheet has this hour's row added.

  4. 3
    Slack - digest the longest waits
    slack.com
    WebRun in Slack: digest the longest waits
    WebRun opens Slack to digest the longest waits.
    • Post the hourly counts to the dispatch channel
    • List the top 3 longest-waiting requests with unit and wait time
    • Flag the digest if any request has waited more than 20 minutes

    Done when Charge nurse has this hour's queue digest in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
patientfocussystems.com
ScheduleRuns automatically on this cadence
Every hour, on the hour
DeliveryHow each run's result reaches you
Queue digest · Slack
OutputWhat each run produces - An hourly row in the queue log sheet plus a Slack digest of queue counts and the longest-waiting requests.
Spreadsheet + digest
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

Does this replace the live dispatch board?

No. It supplements it, WebRun's Slack digest is a quick hourly check, the full live queue always stays in Patient Focused Systems for real-time work.

How far back does the queue log go?

It keeps a rolling 30 day history in the Google Sheet by default, so you can spot patterns like which hours or units run the longest waits.

Will it alert anyone about a specific stuck request?

It flags any request waiting more than 20 minutes right in the hourly Slack digest, though for a single trip that needs a faster alert, pair this with a real-time delay-alert workflow.

Put this on autopilot.

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