Verify MC Automated Renewal Reminder Drafts
Every morning, WebRun opens Verify MC, checks each expiring patient against your staggered reminder schedule of 60, 30, and 7 days out, drafts the correct next reminder email in Gmail for anyone due one, and posts a Slack coverage summary showing how many patients sit at each stage, so the full renewal series is ready for staff to approve and send.
How do I draft a staggered medical cannabis renewal reminder series for approval?
WebRun opens Verify MC each morning, places every expiring patient on your staggered renewal schedule of 60, 30, and 7 days out, and drafts the correct next reminder email in Gmail for anyone due one. It posts a Slack coverage summary of each stage, so the full reminder series is prepared for staff to approve rather than written by hand.
- Patients get a paced 60, 30, and 7 day reminder sequence, not one email
- Every stage's draft is prepared and awaiting approval each morning
- Staff see live coverage of who sits at each reminder stage
Built for medical cannabis clinics · MMJ certification practices · patient coordinators · telehealth cannabis doctors
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 - place patients on the reminder schedule
verifymc.com
WebRun opens Verify MC to place patients on the reminder schedule. - Open Verify MC and read the certification expiry date for every active patient
- Work out which reminder stage each is due today: 60 days out, 30 days out, or 7 days out
- Skip anyone already renewed or whose reminder for that stage was already prepared
Done when Every patient due a reminder today is matched to the correct stage.
-
2
Gmail - draft the next reminder in the series
gmail.com
WebRun drafts the next reminder in the series in Gmail. - Draft the stage-appropriate reminder email for each due patient, gentler at 60 days and clearer at 7 days
- Keep every draft free of diagnosis or treatment detail, referencing only the renewal and how to rebook
- Leave each email as an unsent Gmail draft for staff to review and approve before it is sent
Done when A stage-correct reminder draft sits in Gmail for every patient due one today.
-
3
Slack - post the reminder coverage summary
slack.com
WebRun posts the reminder coverage summary to Slack. - Post a coverage summary to the front desk channel: how many patients sit at 60, 30, and 7 days out today
- List the count of drafts prepared and awaiting approval, referencing patients by number only
- Note that all reminder drafts are held for staff approval and none are sent by the workflow
Done when Staff see today's reminder coverage and the draft count 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 send the reminder emails itself?
No. WebRun drafts the stage-correct reminder in Gmail and leaves it unsent for staff to review and approve. The Slack summary is internal only, so no reminder reaches a patient without a person signing it off.
How is this different from a single expiry reminder?
It manages a staggered series, placing each patient at 60, 30, or 7 days out and drafting only the reminder due today. That gives patients a paced sequence of nudges rather than one email, all prepared for approval.
Do reminders reveal any clinical information?
No. Every draft references only that a renewal is due and how to rebook, with no diagnosis or treatment detail, and the Slack summary uses patient reference numbers, so protected health information is never exposed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.