Verify MC Automated ID Verification Queue
Every morning, WebRun opens Verify MC, reviews patients with an upcoming or recent visit, checks whether each has a verified photo ID and proof of state residency on file, records any missing or mismatched document in a Google Sheet queue, and posts your intake staff a Slack shortlist of who to chase before their certification can proceed.
How do I track which medical cannabis patients still need ID verification?
WebRun opens Verify MC each morning, checks whether patients with upcoming or recent visits have a verified photo ID and proof of residency, and records any missing or mismatched document in a Google Sheet. It posts intake staff a Slack shortlist ranked by urgency, so no certification proceeds on unverified documents and staff know exactly what to chase.
- No visit proceeds on unverified ID or residency documents
- Staff see exactly which item each patient is missing
- Document images stay in Verify MC and never enter the queue
Built for cannabis clinic intake staff · MMJ certification practices · telehealth cannabis clinics · clinic compliance teams
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 - check ID and residency documents
WebRun opens Verify MC to check ID and residency documents. - Open Verify MC and review patients with a visit in the next 3 days or a recent visit awaiting card issuance
- For each, check whether a photo ID and proof of state residency are uploaded and marked verified
- Note any document that is missing, expired, unreadable, or whose name or address does not match the record
Done when Every relevant patient has a documented ID verification status.
-
2
Google Sheets - build the verification work queue
WebRun builds the verification work queue in Google Sheets. - Append one row per patient needing verification with the exact issue: missing ID, expired ID, address mismatch, or unreadable upload
- Mark each row by urgency based on how soon the visit is
- Record only the patient reference and the document issue, never the document contents or personal identifiers
Done when The verification queue lists every outstanding document issue with its urgency.
-
3
Slack - post the shortlist to chase
WebRun posts the shortlist to chase to Slack. - Post a shortlist to the intake channel of patients whose documents must be resolved before their visit, most urgent first
- Show each by reference and the single item outstanding, so staff know exactly what to request
- Note that this is an internal work queue and the workflow contacts no patient
Done when Intake staff have today's document verification shortlist 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 approve or reject documents itself?
No. WebRun only flags which documents are missing or mismatched and queues them for your intake staff. A person reviews and verifies every ID, so the workflow never approves, rejects, or acts on a document on its own.
Does the queue store copies of patient IDs?
No. The Google Sheet and Slack shortlist record only the patient reference and the nature of the issue, such as expired ID or address mismatch. Document images stay in Verify MC, so no ID contents leave the source system.
How does it prioritise the list?
It ranks each outstanding issue by how soon the patient's visit is, so documents for patients due in the next day sit at the top and staff resolve the most time-sensitive verifications first.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.