A physiotherapy clinic's front desk fields a specific mix of calls all day: existing patients rescheduling, new patients asking what it costs, and people trying to work out whether their insurance covers it.
The third category is the one that takes the longest and generates the least. A patient asking whether you're recognised by their insurer, whether you can bill directly, and whether they need a GP referral first can occupy five minutes of a receptionist's time. Repeated fifteen times a day, that's more than an hour, and none of it is booking anyone.
All of it is documented information.
The three questions that gate a booking
Cost. Session price, whether the initial assessment costs more, whether you do packages. Straightforward if published.
Insurance. Which providers you're recognised by, whether you bill them directly or the patient claims back, whether they need pre-authorisation. This is where most of the reception time goes.
Referral. Whether the patient needs a GP referral before they can be seen. The answer varies by market and by insurer, and patients almost never know.
Get those three answered instantly and reliably and a meaningful share of your enquiry-to-booking friction disappears.
What the bot handles, and what it can't touch
The line in physiotherapy is the same as in any clinical setting, and it's not negotiable.
Fine: fees, insurers, referral requirements, appointment length, what to wear, parking, practitioner qualifications and specialisms, what services you offer, opening hours, cancellation policy.
Not fine: what an injury might be, whether physio will help it, whether someone should rest or move it, how long recovery takes, whether an exercise is safe, or anything at all about a specific person's condition.
The correct handling of "I've got a sharp pain in my shoulder when I lift my arm, can you help?" is to acknowledge it, explain that an initial assessment is exactly how that gets answered properly, and offer to get them booked or have a physiotherapist call. Not a discussion of rotator cuffs.
Configure that as the first rule, and configure it to err toward handing over. Over-caution costs you nothing here; under-caution is a real risk.
Specialism matching is genuinely useful
Most physio clinics have therapists with different focuses. Sports injury, post-operative rehab, women's health, neurological, occupational. Patients don't know that and often book with whoever has a free slot.
A bot can ask what kind of help someone is looking for, in general service terms ("sports injury", "after an operation", "ongoing back problem"), and note it so reception books them with the right therapist. That's not clinical triage; it's the same question your receptionist already asks, done more consistently.
The effect is real: better matched first appointments mean better outcomes and fewer patients who don't come back after session one.
Post-operative and referred patients
A large slice of private physio work comes via consultants and surgeons, and those patients arrive with a specific protocol and a lot of questions: does the clinic have the right equipment, have the therapists worked with this procedure before, how soon after surgery can they start, will you liaise with the surgeon.
Those are answerable from your service content, and answering them well positions the clinic as the competent choice. Post-operative enquiries are unusually sensitive to this. They convert far better when the questions about equipment and consultant liaison are answered at first contact rather than discovered at the appointment.
Capturing the booking
Keep the data minimal:
- General area of concern, in the patient's own words, no detail requested
- Whether this is a new problem or ongoing
- Insurer, if using one
- Preferred days and times
- Name and phone
Nothing more. Detailed health history belongs in your intake process, not a chat window. Instruct the bot explicitly not to ask follow-up questions about symptoms even if the patient volunteers detail.
The red-flag escalation
Write a scripted response for anything suggesting a medical emergency: chest pain, sudden severe headache, loss of sensation in the saddle region, loss of bladder or bowel control, sudden weakness on one side, symptoms following a significant fall or accident.
The bot must not assess. It directs to emergency services, immediately and unambiguously, and stops.
This should be the very first instruction in the configuration.
Where the time actually gets saved
Clinics usually adopt this expecting more bookings. The bookings do come (evening enquiries are a real and underserved channel), but the effect most clinics notice first is on reception.
The insurance conversation, in particular, is enormous in aggregate and almost entirely mechanical. Handing it to a bot gives your front desk back a chunk of every day, which they spend on the things that only a person can do: managing the diary, handling reschedules, and looking after patients who are actually in the building.
Getting it live
Point it at your website so it learns your fees, insurer list, services, therapist specialisms, and referral policy. If your insurance information isn't published clearly, write that page first; it's the highest-value content you can add, bot or no bot.
Set the capture fields as above. Write the three instructions: no clinical discussion, red-flag escalation, hand over when unsure.
The number that tells you it worked
Two numbers. Evening and weekend enquiries captured, and reception call volume on insurance and fee questions.
The first tells you whether you're reaching patients you previously missed. The second tells you whether your front desk got their day back, and in a busy clinic, that's often the change people notice most.