New patients ring once. If reception is with the person standing in front of them, the call goes to voicemail and the patient rings the next practice on the list. The agent answers every call, books against your live calendar, and stops at the clinical line rather than crossing it.
Most practices find that the bulk of inbound calls are scheduling, not medicine.
Do you take my insurance, do you have anyone sooner, how much is a first consultation. This caller is comparing you against two other practices in the same hour, and the practice that answers is usually the practice they book.
The highest-volume call and the most mechanical: find a slot, move a slot, cancel a slot. It needs the live calendar and the practice's own rules about who can do what and how long it takes.
Results, medication, symptoms, whether something can wait. This is the call that must reach a person, and reach the right person, with the reason already written down.
Nothing here is a staffing failure. It is a structural one.
A receptionist with a patient at the counter cannot take the call, and should not. So the practice ends up choosing between the patient present and the patient calling, several times an hour, all day. The phone loses that argument every time, and nobody records what it cost.
They cluster at opening, at lunch cover, and in the hour after a closure. Staffing for the peak means paying for the trough. Staffing for the average means the peak goes to voicemail, which is where the new-patient enquiry dies.
The scope is deliberately narrow. Everything clinical is a handoff, by design and in writing.
Availability is read at the moment of the call, not from a copy, and the appointment is written back during the same conversation. Appointment length, the practitioner, the room and the buffers are configured with you before launch, because those rules are where booking automation usually goes wrong.
How the booking works →A confirmation call the day before reaches people that an unread text does not, and it turns some no-shows into reschedules instead of empty chairs. When a slot frees up, the same agent can work down a waiting list and offer it.
Anything about symptoms, results or medication is captured with the reason and the callback number and routed to whoever you nominated. The agent does not decide how urgent it is; it applies the rule you gave it and says plainly what will happen next.
None of these calls arrive on their own. A patient due for a follow-up, an annual exam or the next step in a treatment plan is not going to chase the appointment — the clinic has to place the call, from its own records, or the date quietly slides.
A follow-up appointment, a post-procedure check, a review of how a new medication is sitting. The next step was already agreed at the last visit, so the call is picking up a commitment that was already made, not proposing something new.
A yearly exam, a screening, a routine review: a date the clinic already sets, on a calendar nothing forces the patient to watch. Nobody chases a problem that has not announced itself yet, which is exactly why this call keeps losing to whatever is urgent today.
A plan delivered in stages — physiotherapy, orthodontics, a multi-session course — has the next booking built into it. Between sessions, the patient's own memory is the only thing holding the plan together; a call that books the next step before it is forgotten replaces that with a system.
No complaint on file, no cancellation, just a longer gap since the last visit than the clinic would choose. That is the same lapsed-contact case as any other reactivation list, worked the same way: on the clinic's own patient file, never a bought one.
How reactivation calling works generally →Benerra supplies the calling technology for a patient recall system. The clinic decides who is on the list, what the call proposes, and when it is allowed to ring.
Who is due, and for what, is read from the recall interval, the treatment plan or the appointment history the clinic already keeps — not a blanket 'we miss you' pass over every patient on file. A recall call and a lapsed-patient call are told apart before either one dials.
Which systems are read and written, and the script for each recall reason, are agreed and confirmed in writing before the first live call, the same discipline as any other Benerra build. Benerra does not set clinical outreach policy: the clinic decides what to say and when to call, and checks its own jurisdiction's rules on contacting patients, the same way it would for any other outbound list.
Booked, declined, asked to be taken off the list, no answer: each record gets a dated outcome and a transcript behind it, the same reactivation mechanic used outside healthcare.
If a supplier will not tell you this part, that is the part to ask about.
The agent will not tell a caller whether a symptom is serious, whether to take a medication, or whether they need to be seen today. It says it cannot answer that and gets them to someone who can.
Recognising a genuine emergency from a description is not something we will claim. What we do instead is agree an explicit rule with you: the words and situations that trigger an immediate transfer or a scripted instruction to call the emergency number, and nothing subtler than that.
Call audio, transcripts and the fields the agent collects run on our own servers and stay in-region, and our appointed representative in the European Union under Article 27 GDPR is named on the compliance page. We do not claim HIPAA, ISO or any audited standard we have not been audited against, and your own review should start from what that page states.
What we do and do not claim →A booking that lands anywhere other than the system your staff already look at is worse than no booking.
The agent reads availability and writes appointments into the system you already run. What matters technically is whether availability can be read and a booking written back programmatically. Where a system cannot do that, we say so during scoping rather than after.
It sits on the line patients already have. You choose whether it answers everything, only overflow, or only outside opening hours, and we confirm in writing which systems are connected before it takes a live call.
What changes between these pages is which calls matter and what the agent has to be stopped from doing.
The agent who answers first gets the viewing. Everyone else gets a callback nobody returns.
What we would build →You are under a sink. The phone is a job you have not quoted yet.
What we would build →Three questions are most of your call volume, and all three have an answer in a system.
What we would build →The service desk is with a customer at the counter. The sales enquiry arrives at nine at night.
What we would build →Every failed delivery is a phone call and a second van. Most of them are an address problem.
What we would build →These six are where inbound call volume is heaviest and the integrations are best understood, not the limit of what the agent handles. If your calls are repetitive and the answers live in a system, the shape of the work is the same.
Every industry page →