Automated Zoobook Diversion Risk Alerts
Every morning, WebRun opens Zoobook Systems, checks each take-home patient for diversion risk signals such as missed callbacks, refused screens, and reported dose selling, logs every flagged patient to a Google Sheet with the signal and date, and texts the diversion control officer through Twilio when a patient crosses your risk threshold.
How do I track diversion risk signals for take-home patients?
WebRun checks Zoobook Systems each morning for diversion risk signals, missed callbacks, refused screens, and reported dose selling, logs every flagged take-home patient to a Google Sheet with the signal and date, and texts your diversion control officer through Twilio when a patient crosses your risk threshold. Nothing reaches the patient directly, and low risk days stay quiet.
- Diversion risk signals are logged the same day instead of at a periodic audit
- Only patients over your risk threshold generate an alert
- A full risk history is visible in one running log instead of scattered notes
Built for OTP diversion control officers · methadone clinic medical directors · OTP compliance teams · take-home review committees
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.zoobooksystems.comin a real browser with your saved login - no setup, no API keys. -
1
Zoobook Systems - check diversion risk signals
zoobooksystems.com
WebRun opens Zoobook Systems to check diversion risk signals. - Open Zoobook Systems and pull take-home patients with a recent flag
- Check for missed callbacks, refused or no show screens, and any reported dose selling or sharing
- Score each patient's combined risk signals for the past 30 days
- Note the patient's take-home level and current dosing status
Done when Every take-home patient with a risk signal in the past 30 days is identified and scored.
-
2
Google Sheets - log every flagged patient
google.com
WebRun opens Google Sheets to log every flagged patient. - Open the Diversion Risk log
- Add a row for each flagged patient with the signal, date, and risk score
- Keep a running history so repeat signals are visible over time
Done when The diversion risk log reflects every flagged patient and signal to date.
-
3
Twilio - alert the diversion control officer
twilio.com
WebRun opens Twilio to alert the diversion control officer. - Text the diversion control officer only when a patient's score crosses your threshold
- Include the patient's take-home level and the signals driving the score
- Send nothing for patients below the threshold
Done when The diversion control officer is texted the same day for any patient over threshold.
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
Does it change a patient's take-home privileges automatically?
No. WebRun only logs risk signals and alerts your diversion control officer. Any change to take-home level, dosing, or discharge stays a clinical decision made by staff.
What counts as a diversion risk signal?
Missed random callbacks, refused or no show drug screens, and any reported dose selling or sharing. Each is logged individually and combined into a rolling risk score.
Will it text or contact the patient directly?
No. The Twilio alert only goes to your internal diversion control officer. It never contacts the patient, and no detail leaves your logged systems without staff review.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.