All templates
For vein clinics, vascular surgeons & front desk staff

Recall vein patients for their post-ablation duplex check

Every morning, WebRun opens OmniMD, finds patients whose post-ablation duplex recheck is due, drafts a personalized recall text in Twilio, and pencils a candidate recheck slot in Google Calendar, then queues both for your front desk to approve so no patient is contacted or booked without a human.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 8:00 AM WebRun
1 OmniMD find patients due for a post-ablation recheck
2 Twilio draft a recall text for each patient
3 Google Calendar pencil a candidate recheck slot
Run a sample
In short

How do I automatically recall vein patients for their post-ablation recheck?

WebRun finds patients due for a post-ablation duplex recheck in OmniMD every morning, drafts a personalized recall text in Twilio, and pencils a tentative slot in Google Calendar. It queues both for your front desk to approve, so patients get recalled on schedule while every message and booking waits for a human to confirm.

  • Post-ablation rechecks happen on schedule instead of slipping
  • A tentative slot is held so booking is quick once the patient replies
  • No recall text or booking happens without front desk approval

Built for vein clinics · vascular surgeons · front desk staff · vascular ultrasound schedulers

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 omnimd.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    OmniMD - find patients due for a post-ablation recheck
    omnimd.com How to Automate OmniMD
    WebRun in OmniMD: find patients due for a post-ablation recheck
    WebRun opens OmniMD to find patients due for a post-ablation recheck.
    • Open OmniMD and find patients whose ablation was performed within the recheck window, typically 3 to 7 days for a DVT check and then longer term
    • Confirm each has no post-ablation duplex recheck already scheduled or completed
    • Capture the patient initials, ablation date, and the recommended recheck type
    • Note how many days past the ideal recheck date each patient is

    Done when Every patient due for a post-ablation recheck without one booked is listed.

  3. 2
    Twilio - draft a recall text for each patient
    twilio.com How to Automate Twilio
    WebRun in Twilio: draft a recall text for each patient
    WebRun opens Twilio to draft a recall text for each patient.
    • Draft a short, friendly recall SMS for each patient inviting them to book their post-ablation duplex
    • Personalize with the patient first name and keep clinical detail minimal
    • Queue every message as a draft in Twilio. Do not send. Leave all drafts for review

    Done when A recall text is drafted and queued for each due patient, none sent.

  4. 3
    Google Calendar - pencil a candidate recheck slot
    calendar.google.com How to Automate Google Calendar
    WebRun in Google Calendar: pencil a candidate recheck slot
    WebRun opens Google Calendar to pencil a candidate recheck slot.
    • Pencil a tentative recheck slot on the ultrasound calendar for each due patient
    • Mark the slot as unconfirmed so it holds time without committing the patient
    • Leave confirmation and any patient contact to your front desk after the recall is approved

    Done when A tentative recheck slot is held for each due patient, none confirmed.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
omnimd.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Recheck recalls · Google Calendar
OutputWhat each run produces - A recall text drafted in Twilio and a tentative Google Calendar slot for each patient due for a post-ablation recheck, all queued for front desk approval.
Drafts + held slots
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

Will it text patients or confirm bookings on its own?

No. Every recall text is drafted in Twilio and each calendar slot is penciled as unconfirmed. Your front desk approves before anything sends or books, so no patient is contacted or committed without a human deciding.

How does it know a patient is due for a recheck?

It reads the ablation date in OmniMD and applies your recheck schedule, for example an early DVT check and a later reflux recheck, then lists patients past the ideal date who have no recheck booked.

What if the patient already booked their recheck?

It checks the live schedule in OmniMD and Google Calendar each morning, so any patient who already has a recheck booked is skipped and no duplicate recall is drafted.

Put this on autopilot.

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