The diabetic foot check that stops coming back

In podiatry, the visit that protects a patient most is the one they never think to book themselves: the diabetic foot check that only works while it keeps happening. When one lapses, nothing flags it, and a patient who should return in ten weeks is gone in twelve. An AI receptionist for podiatry closes that gap by working the recall as an outbound call and writing the rebooking straight into the diary.

A podiatry diary is not built from one-off visits. It is built from people who come back: the diabetic foot check every few months, the nail and callus review that never really ends, the wound that needs watching until it does not. The new referral is the exciting part. The returning patient is the business.

The front desk knows this on a good day. On a bad day, when three phones are ringing and someone is standing at the counter with a card in their hand, the patient who just finished their appointment walks out without the next one booked. Nobody decided that. It just happened, in the ninety seconds when there was no one free to say "shall we get the next one in the diary now".

That patient is now a name in a recall list. And a recall list is only as good as the person with time to work it, which in most practices is nobody.

27%

of practice leaders rank no-shows their top patient-access focus, MGMA December 2025

9 to 12 weeks

the interval most podiatry clinics set for routine nail and callus recalls

5

podiatry systems 2care books into: splose, Cliniko, ModMed, eClinicalWorks and AdvancedMD

A missed recurring appointment sounds like a scheduling annoyance. In podiatry it is not always that.

For a patient with diabetes, the foot check is surveillance. It is looking for the early signs of a problem before that problem becomes an ulcer, because an ulcer is the event that can begin a longer and much worse pathway. This is why a podiatry clinic's own protocol treats a diabetic foot recall as a clinical priority rather than a courtesy reminder, and why the gap between "due" and "booked" is one the practice actually has to own.

The routine nail and callus patient is a different case with the same operational shape. They are not at acute risk, but they return every 9 to 12 weeks for years, or at least until they drift to another clinic because yours never rang. One lapsed booking there is not one lost appointment. It is a decade of appointments that now belong to someone else. A clinic that quietly sheds even a handful of these patients a month is losing its most predictable revenue in the place nobody is looking.

How recurring podiatry recalls actually fall off

Nobody sets out to lose a recurring patient. The loss is structural, and it happens in three ordinary places.

The first is the checkout that never happens, described above: the patient leaves mid-rush without the next slot booked. The second is the recall that gets entered but never chased, because working it means a person sitting down to make thirty outbound calls that the day never has room for. The third is the callback that lands after hours or during the clinic, hits voicemail, and quietly ends there.

No-shows are the biggest patient-access worry practice leaders name for 2026, ahead of online scheduling and phone access, in an MGMA poll of 236 practice leaders in December 2025. An unworked recall is a no-show the practice created for itself, one appointment at a time.

What working the recall list means, call by call

An AI receptionist works the recall list as outbound contact, not a passive reminder. It reads the live diary, offers a real slot, and commits the booking in the same call. The third row below is the one to read, because it describes what happens when the patient does not pick up.

Moment in the recall call	What the patient hears	What the system does
Recall reached	"Your last foot check was in June, shall we book the next one?"	Caller matched to the existing record before anything is created
Slot offered and taken	"Thursday the 14th at 10 with the same clinician"	Live availability read at that moment, appointment written during the call
No answer or a decline	"No problem, I will text a link and try again Friday"	Recall left open, SMS queued, nothing marked as done

The failure path is the test. A reminder tool marks the recall as actioned and moves on. A system that leaves the recall open, follows up by text, and retries on your cadence is the difference between a list that shrinks because it was worked and a list that shrinks because it was cleared.

What the agent reads, writes, and never touches

The recall workflow only touches scheduling and the fields needed to book. The third group is the one your review should read first, because it is the boundary most vendor pages leave to be discovered after signing.

Direction	Object	What it means for a recall
Read	Provider diary and visit type	Live availability and the correct length for a foot check versus a nail review
Read	Patient identity and coverage	The returning patient is matched, not entered twice, and insurance on file is reused
Write	Appointment and reason for visit	The booking is committed against the provider, with the recall type recorded
Write	Demographics and call outcome	Contact details confirmed aloud, and a traceable record of what the call did
Never	Clinical notes and results	Not read, not written, not read aloud; a result call is escalated, never handled
Never	Medication and anything out of scope	A request is taken down and passed on, never granted, and nothing beyond granted scope is reachable

Every write is a discrete, reversible event with the call attached, so a booking made in error is one your team can trace and undo rather than a change nobody can account for later. Escalation is a routing decision, not a clinical one: the presentations that must reach a person are the ones your practice defines in its own words, and the same rules run on every call regardless of the hour.

The connection, in the terms your IT review will ask about

None of this needs software installed on your machines, and no credentials are shared with us. The connection is authorised against your system and scoped to scheduling, and the rows below are settled during implementation review rather than assumed.

What the review asks	How it works
Availability	Read live at the moment of the call, never from a nightly extract
Write timing	The appointment exists before the caller hangs up, with no queue to key in
Concurrency	No cap on simultaneous calls, so a Monday recall push runs alongside inbound
Duplicates	Callers matched to the existing record first, so a recall does not create a second chart
Audit	Every call transcribed and every write logged against the patient record
Compliance	A BAA is signed before any patient data moves, with regional hosting on request

Where the diabetic foot recall gets chased instead of filed

The case for 2care in a podiatry practice is narrow and specific: it is the recall list, not the switchboard.

US podiatry runs on a mix of specialty systems like TRAKnet, Sammy and splose alongside broader platforms like ModMed, AdvancedMD and Cliniko. Most call handling answers the phone when it rings, but the recurring-care problem is the opposite shape, because the patient who lapsed is precisely the one not ringing. 2care is listed in the eClinicalWorks and Cliniko marketplaces, and runs the recall as outbound recall outreach on the cadence you set, calling and texting patients who are due, reading live availability, and writing the booking back into the diary during the call. A patient who ignores the call gets a text; one who ignores the text gets another attempt. The list is worked every day, not on the rare afternoon someone has a spare hour.

2care also holds one thread per patient across voice and SMS, so a patient who books a foot check by phone and later texts to move it is the same record, not a fresh enquiry. A foot clinic's recall rebuild is this with a practice's own numbers attached.

The compliance line most vendors get wrong

There is a real distinction here that a lot of vendor copy blurs, and it is worth getting right before you sign anything. A service that only patches a call through to a person can fall under the HHS conduit exception, because it has only transient access to the information it carries.

A system that transcribes the call, resolves the caller against a record, and writes an appointment back is a business associate under HHS business associate rules, because it is creating, receiving and maintaining protected health information.

A signed Business Associate Agreement is then required, not a courtesy. Ask any vendor working your recall list to confirm the agreement covers that workflow specifically, and treat "HIPAA compliant" with no BAA as an unfinished answer. The point is not a compliance badge, it is knowing which of the two things you are actually buying.

When an AI receptionist is the wrong call for a podiatry desk

This does not fit every practice, and pretending it does is how you end up disappointed after setup.

A single-handed clinic with a quiet phone and a receptionist who is never more than half busy does not have the recall problem this solves, and would feel the cost without the benefit. A caller who needs a clinician's judgement in the first thirty seconds, a fresh wound that has changed or an infection that is spreading, needs a person and a fast handoff, not a booking flow. And if your podiatry software has no API, the write-back that makes this worthwhile does not exist yet, and you are looking at manual booking. Ask about your specific system before assuming it connects.

Frequently asked questions

Does it write into splose, Cliniko or ModMed, or just hand us a request?

It writes. Availability is read live and the appointment is created in your system during the call, so there is no queue of booking requests for the desk to key in afterwards. The booking respects the provider templates and visit types your system already enforces, so a recall cannot be booked against a rule your team would refuse.

How does it avoid creating a duplicate chart when it calls a lapsed patient?

The caller is matched against the record your system already holds before anything new is created. For a recurring patient who has attended for years, that means they are recognised rather than entered a second time, and the rebooking lands on the existing chart with their history and coverage intact.

Can it tell a diabetic foot check from a routine nail appointment?

It books from the recall type held on the record, so a diabetic foot review and a routine nail visit are treated as the separate recalls they are, at their own intervals and lengths. The clinic sets the priority and cadence for each cohort, and the agent books to those rules rather than judging clinical urgency itself.

What happens if a recall call turns into something clinical?

It is escalated on the protocol your practice defines, with the call detail attached, and reaches a person rather than being assessed by the agent. A patient describing a wound that has changed or an infection that is spreading is a routing decision the system is built to make, not a clinical judgement it is allowed to make.

Is working a recall list against patient records HIPAA compliant?

A system that matches a caller, schedules, and writes the booking back is handling protected health information, which makes it a business associate under HHS rules and means a signed BAA is required. Every call is transcribed and every write is logged against the record, so the workflow stays auditable long after the call.

Pull your recall list before you do anything else

Open your practice software and pull the recurring patients whose last visit is now past their normal interval, the diabetic foot checks and nail reviews overdue by more than a fortnight. Count them, then count how many were contacted after they lapsed. The gap between those two numbers is the size of the problem, and you can measure it this week whether or not you change anything about how the phone is answered.

That number is usually the moment the recall list stops looking like admin and starts looking like the diary.

Ready to see it on your own systems? Book a demo and hear 2care work a sample podiatry recall list against a live diary, so you judge the rebooking flow on a real call rather than a slide.