Verify MC Automated Eligibility Intake Triage
Every morning, WebRun opens Verify MC, reviews new patient enquiries received overnight, checks each one's state of residence and stated qualifying condition against your eligibility rules, records the outcome in a Google Sheet, and posts your front desk a triaged intake queue in Slack that separates ready-to-book patients from those still missing information.
How do I automatically triage new medical cannabis certification enquiries by state eligibility?
WebRun opens Verify MC every morning, reviews overnight patient enquiries, and checks each one's state and stated qualifying condition against your eligibility rules. It logs the outcome to a Google Sheet and posts your front desk a triaged Slack queue of ready-to-book, needs-documents, and not-eligible patients, so the team schedules the right people first.
- Front desk starts the day with a ready-to-book list instead of a raw inbox
- Ineligible enquiries are flagged before a slot is wasted on them
- Only initials and a reference number ever appear in Slack
Built for medical cannabis clinics · MMJ certification doctors · telehealth cannabis practices · clinic front desk staff
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
verifymc.comin a real browser with your saved login - no setup, no API keys. -
1
Verify MC - read new patient enquiries
verifymc.com
WebRun opens Verify MC to read new patient enquiries. - Open Verify MC and review patient enquiries and portal registrations added since the last run
- For each, read the state of residence, stated qualifying condition, and whether required documents were uploaded
- Flag enquiries whose state you are not licensed to certify in, or whose stated condition is not a qualifying one
Done when Every new enquiry has an eligibility outcome and a reason recorded.
-
2
Google Sheets - log eligibility outcome per enquiry
google.com
WebRun logs each eligibility outcome in Google Sheets. - Append one row per enquiry with initials, state, stated condition, eligibility outcome, and any missing item
- Mark each row ready to book, needs documents, or not eligible
- Keep only initials and a patient reference number in the sheet, never full contact details
Done when The intake sheet holds a labelled row for every new enquiry.
-
3
Slack - post the triaged intake queue
slack.com
WebRun posts the triaged intake queue to Slack. - Post a short intake digest to the front desk channel grouped by ready to book, needs documents, and not eligible
- List each patient by initials and reference number only, with the single item they are missing
- Put ready-to-book patients at the top so the team schedules them first
Done when The front desk has this morning's triaged intake queue in Slack.
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 reject patients on its own?
No. WebRun only labels each enquiry ready to book, needs documents, or not eligible and posts the queue for your staff. A person makes every scheduling and eligibility decision, and no patient is contacted by the workflow.
Does patient health information leave your systems?
No. The Slack digest and Google Sheet carry only initials, state, and a reference number, never names, contact details, or clinical notes, so no protected health information is exposed in an internal channel.
How does it decide who is eligible?
It compares each enquiry's state and stated qualifying condition against the licensed states and condition list you configure. Anything outside those rules is flagged not eligible with a reason, and you can adjust the rules any time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.