Patient reminders and no-show follow-up for clinics
Empty slots hurt access as much as revenue. We build reminder workflows that read the schedule from your EHR, send reminders in each patient's preferred channel within the limits of the US healthcare texting rules, take confirm, cancel and reschedule replies, offer freed slots to a waitlist and send every no-show to a person for follow-up. A typical build costs $1,000 to $2,500 and takes about four weeks.
The problem
Why clinics still lose appointment slots
Most EHRs can send a basic reminder, but clinics still lose slots: the reminder goes out once, the patient cannot easily reschedule, and a cancellation the night before leaves a gap nobody fills.
Missed visits need care. A patient who did not attend a follow-up after a procedure or a course of physical therapy may need a clinician to look at the chart, not an automated warning about the no-show policy.
Texting patients in the US also has rules: the healthcare exemption covers appointment reminders but limits length and frequency and excludes billing content, so reminders and payment messages need different designs.
What we build
What our patient reminder automation includes
Reminders by preferred channel
Text, email or voice, following each patient's recorded preferences and quiet hours.
Confirm, cancel or reschedule
Simple replies or a link update the schedule or create a task, depending on what the EHR allows.
Waitlist offers
When a slot opens, suitable patients on the waitlist are offered it in order, first to accept gets it.
No-show list
Every missed visit goes to a coordinator list, with a flag for appointment types the clinic marks as clinically important.
Policy applied consistently
Late-cancellation and no-show policy wording sent the same way every time, with fees decided by staff.
Monthly summary
Reminders sent, confirmations, cancellations, slots refilled and no-shows by appointment type.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Schedule read
Each day the workflow reads upcoming appointments from the EHR.
-
02
Automated
Reminder sent
Patients get an approved reminder with confirm and reschedule options.
-
03
Automated
Slot refilled
Cancellations trigger waitlist offers for the freed slot.
-
04
Coordinator review
Coordinator follows up
No-shows go to a coordinator, who calls the patient and rebooks.
-
05
Clinician or medical director decides
Clinical follow-up
For flagged appointment types, the clinician decides what a missed visit means for care.
How it behaves
How reminders and no-show follow-up behave
What the patient sees
- A short reminder in the channel they chose
- An easy way to confirm, cancel or reschedule
- A call from the clinic if they missed a visit
What staff see
- A daily no-show list with flags for important visit types
- Waitlist offers accepted and slots refilled
- A monthly summary by appointment type
What the automation does
- Reads the schedule and applies texting limits and opt-outs
- Handles replies and offers freed slots
- Logs every message for audit
Edge cases and fallbacks
- Patient replies with a clinical question
- No automated answer; routed to staff under the clinic's process.
- Two waitlist patients accept the same slot
- First confirmed acceptance wins and the other gets a polite note.
- Patient has opted out of texts
- Email or a call instead, as recorded in their preferences.
- EHR schedule unavailable
- That day's run is held and retried, never sent from stale data.
Architecture
Patient reminders and no-show follow-up at a glance.
- Input
- Logic and services
- Output
- People
How it flows
- 1 Every day the workflow reads upcoming appointments from the EHR.
- 2 Contact rules apply channel preferences, opt-outs, quiet hours and the healthcare texting limits.
- 3 Reminders go out with confirm and reschedule options; cancellations trigger waitlist offers.
- 4 No-shows go to a coordinator, and flagged appointment types go to the clinician.
Project planner
How the project runs, phase by phase.
Patient reminders & no-show follow-up project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Current reminders, appointment types, cancellation policy, waitlist practice and EHR access.
-
02
Design
2 to 3 days
Reminder timing and wording, reply handling, waitlist rules and clinically important visit types.
-
03
Build
1 to 2 weeks
Schedule reads, reminders, reply handling, waitlist offers and the no-show list.
-
04
Shadow run
About 1 week
Reminders go to a test group while staff check every reply.
-
05
Launch
1 to 2 days
Switch on for one clinic or service line, then widen.
-
06
Support
Ongoing
Wording changes, new appointment types and monitoring.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Workflow mapping with the clinic team, wording, data flows and a written specification.
$200 – $400
-
Build
The n8n workflow, rules, AI step where useful, logging and error handling.
$500 – $1,300
-
Integrations
EHR or practice management access, messaging and staff alert channels.
$150 – $400
-
Testing and shadow run
Acceptance tests and a side-by-side run while staff keep the old process.
$100 – $250
-
Launch and training
Go-live, front-desk walkthrough and a short run book.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. If your EHR's built-in reminders already work, we connect to them and add only what is missing. Messaging and n8n are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing). A BAA needs Twilio's Security or Enterprise Edition if patient information is in the messages.
- n8n: Free self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: healthcare text exemption limits
The FCC exemption covers purposes such as appointment confirmations and reminders, sent free to the patient, 160 characters or less, at most one message a day and three a week, with STOP honoured immediately. It excludes marketing and billing content. General information, not legal advice.
Source: www.law.cornell.eduUS: Twilio and PHI
Twilio requires a signed BAA (with its Security or Enterprise Edition) and HIPAA-eligible products before patient information flows through its messages.
Source: www.twilio.comUK: service messages vs marketing
Appointment reminders are service messages; anything promotional in the same text becomes marketing under PECR and needs consent or the soft opt-in.
Source: www.legislation.gov.ukFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Patient reminders & no-show follow-up questions, answered.
Usually the parts around the reminder: two-way replies, waitlist offers for freed slots, a no-show list for coordinators and reporting. Where the EHR reminders are good, we keep them and connect to them.
Not under the US healthcare exemption, which excludes billing and financial content. Balance reminders need their own consent and design, so we keep them separate.
A well-timed reminder, an easy way to reschedule and a quick waitlist offer do most of the work. Each patient gets a small number of messages within the frequency limits.
The policy wording is sent consistently, but any fee is decided by staff. Some missed visits have good reasons, and some need a clinician to look at the chart.
Where the EHR or booking tool offers self-scheduling, the reminder links to it. Otherwise a reschedule reply creates a task for the coordinator.
Confirmations, cancellations with notice, slots refilled from the waitlist and no-shows by appointment type, month by month.
Free 20-minute call
Want this for your healthcare clinic?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for healthcare clinics
All servicesHealthcare CRM & new-patient pipeline
Every enquiry from web forms, calls, chat, directories and physician referrals lands in one healthcare CRM pipeline with owners, follow-ups and a weekly report by source and service line.
From $1,000 · About 4 weeks Details
Referral management & patient intake
Log incoming referrals the day they arrive, send and chase intake and consent forms, track what is missing before the first visit and close the loop with the referring provider.
From $1,000 · About 4 to 5 weeks Details
AI receptionist & medical answering assistant
An AI front desk on your website, text line or phone that answers from the clinic's approved answers, takes booking requests, discloses it is automated and hands anything clinical to staff.
From $2,500 · About 5 to 8 weeks Details