For clinics and practice administration
The paperwork around the visit, not the visit
Confirm appointments, chase the intake forms and log referrals on the channels your patients agreed to — administrative work only, with anything clinical going straight to your staff.
Administrative work only; every message to a patient waits for a person.
Where the week actually goes
A practice’s front desk does the same administrative work all day: confirming appointments, chasing the intake form, logging the referral, sending the reminder. None of it is clinical, and all of it decides whether the day runs on time. Awish does that administrative work from your description of it.
It works only on the channels your patients agreed to, with the systems you granted one at a time, and anything clinical goes straight to a clinician untouched. Each connection can be withdrawn; every message and every entry is on the record with who approved it.
The week today
A practice runs on admin. Confirming tomorrow’s list, chasing the form that never came back, logging the referral that arrived by email, telling the front desk which slots are still open. It is not clinical work, but it eats the day of the people who also have to answer the phone.
With Awish
Awish carries that layer and only that layer. It sends the reminder on the channel the patient consented to, checks what came back against what was required, and files a referral where the right team will see it. Anything clinical — a symptom in a reply, a medication question, an urgent message — goes to your staff, immediately and unanswered.
The workflows, end to end
Three workflows a practice runs, end to end — each with its trigger, the apps it touches, and the step where a person takes over.
- 01
Confirm appointments without the phone round
“Before each appointment, send the reminder on the channel the patient agreed to, handle the reschedules, and tell the desk which slots are still unconfirmed.”
Google CalendarWhatsAppGoogle SheetsClinical questions go to staff
- 02
Chase the intake paperwork before the visit
“When an appointment is booked, send the intake pack, check what came back for completeness, remind the patient, and flag the gaps to the desk.”
GmailGoogle DriveGoogle SheetsThe desk sees the gaps
- 03
Log a referral and keep its status visible
“When a referral arrives, read who sent it and for what, check the required documents, create the record, and route it to the right specialty queue.”
GmailGoogle DriveMicrosoft TeamsIdentity is verified first
Ready to start from
Described requests this team already runs — pick one and it lands in your chat, with its approval points intact.
Documentation Routing and Coding Support
A visit note draft is completed
Microsoft TeamsSharePointAsanaNever finalise a clinical note or a code without the authorised clinician or coder approving it.
Awish checks that the intake, referral or claim reached the right queue with its documents
Use this automationClaim Denial Triage
A claim is denied or rejected
Microsoft TeamsExcelSharePointAsanaDo not alter a diagnosis or a clinical code without review by a qualified coder or clinician.
Awish checks that the intake, referral or claim reached the right queue with its documents
Use this automationDigital Intake and Pre-Visit Check
An appointment is booked or is coming up
TypeformGoogle DriveMicrosoft TeamsUse only compliant data paths; never copy patient health information into a tool that has not been approved.
Awish checks that the intake, referral or claim reached the right queue with its documents
Use this automationEligibility and Benefits Verification
An appointment is booked or the coverage data changes
Microsoft TeamsExcelGmailPresent coverage as verification data, never as a guarantee of payment, and protect patient health information.
Awish checks that the intake, referral or claim reached the right queue with its documents
Use this automationNo-Show Risk and Reminder Escalation
48 hours before each appointment, when the risk criteria are met
TwilioGmailMicrosoft TeamsDo not use protected or sensitive attributes in the risk scoring unless that is explicitly lawful and operationally justified.
Awish checks that the intake, referral or claim reached the right queue with its documents
Use this automationAppointment Scheduling and Reminders
A patient requests an appointment, then 24 and 2 hours before the visit
CalendlyTwilioGmailMicrosoft TeamsDo not expose patient health information over insecure channels, and never treat an urgent clinical symptom as a scheduling request.
Awish checks that the intake, referral or claim reached the right queue with its documents
Use this automation
The tools this runs across
The apps these workflows connect. Each one is granted on its own, before anything runs, and can be withdrawn.
- Google Calendar
- Google Sheets
- Gmail
- Google Drive
- Apaleo
- Appointo
- Bart
- Bookingmood
- Booqable
- Cal
- Calendly
- Etermin
- Evenium
- Eventee
- Eventzilla
- Lodgify
- Planyo Online Booking
What stays under your control
Administrative work only
These workflows move appointments, forms and referrals. They do not triage symptoms, answer medication questions or touch a clinical decision.
Anything clinical goes to a person
A symptom, an urgent message or an unclear intent is escalated to your staff rather than answered — and it is escalated immediately, not queued.
Patient data stays on the paths you approve
Each connection is granted on its own and scoped to one app. A workflow sending reminders cannot reach anything else, and a connection can be withdrawn at any time.
Common questions
Will it answer a patient’s medical question?
No. Message routing classifies administrative from clinical and escalates anything clinical — symptoms, medication, urgency, or an intent it cannot read confidently — to qualified staff without replying.
How does it handle patient data?
Only through the connections you grant, one app at a time, and each one can be withdrawn. Awish runs your workflow in its own isolated execution with its own credentials, so what one workflow can reach is what you connected to it and nothing else.
Can it change a clinical record?
These workflows are administrative: appointments, intake documents, referral records and their status. A clinical note or a code is never finalised without the authorised clinician or coder approving it.
Which channels does it message patients on?
The ones you connect and the patient has consented to — a messaging channel, email, or both. The consent rule is part of the workflow you describe, not an afterthought.
Start with tomorrow’s unconfirmed appointments
Describe how the reminders should work. You will see the plan, and the points where a person takes over, before anything connects.
Free plan · No credit card required