Healthcare · Follow-ups & reminders
Appointment Scheduling and Reminders
Starts when: A patient requests an appointment, then 24 and 2 hours before the visit
Free plan · Outcome verification included · You approve every connection
How it runs
Six stages, from the moment it starts to the checks that keep running afterwards.
It starts
A patient requests an appointment, then 24 and 2 hours before the visit
Awish plans it and asks for each app
The apps it needs are connected one at a time, with your permission, before anything runs.
It does the work
Exactly as the request below describes, across the connected apps.
It stops where a person should decide
Do not expose patient health information over insecure channels, and never treat an urgent clinical symptom as a scheduling request.
It verifies the outcome
After each run, Awish checks that the intake, referral or claim reached the right queue with its documents.
It keeps monitoring
Failures, silent failures and connection health are watched on every plan; anomalies, root cause and recommendations on Business.
The request it runs
This is what opens in chat when you use the template. Change any part of it before anything connects.
“Set up an automation that manages patient appointment scheduling, reminders and rescheduling. Trigger it when a patient requests an appointment, and send reminder checks 24 hours and 2 hours before the scheduled visit. It should offer valid slots based on the provider and location rules, schedule the chosen slot, send a compliant reminder, handle rescheduling and cancellation and update the source system. Connect it with Calendly, Twilio, Gmail and Microsoft Teams. Do not expose patient health information over insecure channels, and never treat an urgent clinical symptom as a scheduling request.”
- Calendly
- Twilio
- Gmail
- Microsoft Teams
Monitoring included
What Awish watches once this template is running.
- Outcome verificationEvery plan
- Silent-failure detectionEvery plan
- Connection healthEvery plan
- Hours saved and ROIEvery plan
- Anomaly detectionOn Business
- Root-cause explanationOn Business
- Recovery recommendationOn Business
More Healthcare templates
Documentation Routing and Coding Support
- Microsoft Teams
- SharePoint
- Asana
Claim Denial Triage
- Microsoft Teams
- Excel
- SharePoint
- Asana
Digital Intake and Pre-Visit Check
- Typeform
- Google Drive
- Microsoft Teams
Eligibility and Benefits Verification
- Microsoft Teams
- Excel
- Gmail
Questions about this template
Can I change where it stops for approval?
Yes. Open the template in chat and say where you want it to stop. The plan updates before anything connects.
What if one of these apps is not connected yet?
Awish asks you to connect each app it needs, one at a time, before the workflow runs. You can decline any of them.
How does Awish know this workflow worked?
After each run it checks that the intake, referral or claim reached the right queue with its documents, in the app where that should happen. If a run reports success but the result is missing, it flags a silent failure.
Run it on your own apps
It opens in chat with the request written. See the plan, approve each connection, and Awish verifies the outcome from the first run.
Free plan · No credit card required