How to Automate After-Hours Patient Inquiries: What to Answer at 10 PM and What to Hold Until Morning
Your clinic's inbox, one ordinary week.
Tuesday, 10:47 PM. Ms Reyes asks how much a cleaning costs.
Thursday, 6:12 AM. Mr Lim asks whether you have anything before work, because he starts at eight.
Good Friday, 2:30 PM. Someone fills in the website form asking about braces.
All three get the same reply, which is nothing, until somebody opens the inbox. Ms Reyes waits ten hours. Mr Lim waits three. The braces question waits until Monday.
Nobody writes any of that down. There's no line in your books for a person who asked and went somewhere else, so the hours you're closed never get any attention or any budget.
Those hours are also a much bigger slice of the week than "after hours" makes them sound. Say you open at nine and close at six, Monday to Saturday. That is 54 hours open out of the 168 in a week, so you are shut for 114 of them, roughly 68 percent. Open seven days on the same hours and you are still shut for 105 hours, exactly 62.5 percent.
So work out which enquiries can be answered at midnight with nobody there, and which ones should wait for a person. That's the whole decision.
The short version
- Count your own night before you buy anything. Thirty days of message timestamps will tell you whether this is a real problem at your clinic or a story a salesperson told you.
- After hours isn't one block. The evening rush, the small hours, the weekend gap and a four-day holiday closure each need different handling.
- Sort every night message into four buckets: answer now, book now, do not answer, hold for a person. Write the script bucket by bucket rather than message by message.
- Inbound automation can run at 3 AM. Outbound must not. Work out when your reminders actually fire before you switch them on.
- A promise with a time in it beats "as soon as possible", but only if somebody is assigned to the morning.
- Block Holy Week, Undas and the Christmas stretch in your calendar before you automate booking, or you will sell slots on days nobody is in the building.
Count your own night first
You already have the evidence. It's sitting in Meta Business Suite, in your website form's inbox, and in your phone's call log.
Scroll back thirty days. For every enquiry that arrived after your closing time, write down two timestamps: when the patient first messaged, and when a human from your clinic first answered. Three numbers come out of that.
Start with your median night lag. Half your after-hours enquiries waited longer than that. Work out the same figure for messages arriving at two in the afternoon and put the two side by side. If your daytime lag is measured in minutes and your night lag in hours, you have found the leak.
Next, count how many after-hours enquiries never got a human answer at all. That number is usually worse than owners expect, because a message that scrolls off the first screen of the inbox is effectively gone.
Last, measure your weekend gap. Close at six on Saturday, open at nine on Monday, and that's a 39 hour stretch with nobody reading anything. Close at noon on Saturday instead and it's 45 hours. Count how many enquiries land inside your own gap.
Then bucket what you found, because the mix decides what is worth automating.
| Bucket | What it sounds like at 10 PM |
|---|---|
| Price | "Magkano po ang cleaning?" "How much for braces?" |
| Availability | "Open po kayo bukas?" "May slot ba this Saturday?" |
| Clinic details | Location, parking, hours, is there a dentist on Sunday |
| Coverage and payment | HMO accepted, instalment, GCash |
| Clinical | "Ang sakit ng ngipin ko" "Is this normal after extraction?" |
| A specific patient's record | Rescheduling, balances, a complaint |
If the first three buckets are most of your night, automation will pay for itself. If your nights are mostly clinical questions from existing patients, what you need is an on-call arrangement with a dentist rather than software, and you can stop reading here with your money intact.
After hours is four different problems
A lot of setups treat half past seven in the evening and two in the morning as the same situation. They aren't.
| Band | What arrives | What the system should do | Outbound messages |
|---|---|---|---|
| Evening rush, closing to about 11 PM | The most volume, and the highest intent. The patient is awake, holding the phone, and comparing you against two other clinics | Answer fully and book. This is the band that converts | Fine until about 8 PM, then stop |
| Small hours, 11 PM to 6 AM | Thin volume, and a higher share of pain and worry | Answer, escalate carefully, book if they want to | None |
| Weekend gap, Saturday close to Monday open | 39 to 45 hours with nobody reading anything | Answer and book into Monday, and say Monday out loud | Only in daylight, and only if someone can act on a reply |
| Long closures: Holy Week, Undas, 24 December to New Year, any day you shut | Days of accumulated enquiries | Answer, book into the first day back, and put the reopening date in the first reply | Almost never |
The last band is the one that catches clinics out. Philippine clinics close for stretches that clinics in other countries don't, and an automated booking system with an open calendar will cheerfully offer somebody a Good Friday appointment. Block those dates before you switch anything on, and block them again each year when Malacañang publishes the proclamation, because the movable dates shift.
The weekend gap has a trap of its own that has nothing to do with chat. If your reminder for a Monday appointment fires on Sunday and the patient replies "sorry po, hindi ako makakapunta", that reply sits unread until Monday morning. You will have received the cancellation and still lost the slot, because nobody was there to refill it. More on where your reminders land further down.
The night triage: four things a message can be
This is the part to write down before anyone configures anything. Every message that arrives while you're closed is one of four things, and each one has a different correct answer.
1. Answer now
Prices, services, opening hours, location, parking, what to bring, how long a cleaning takes, whether you accept a particular HMO, whether there's a dentist on Saturday.
The answers to these don't change between Tuesday afternoon and Tuesday midnight. They're also most of your night. The reply should come from a list you wrote and approved, word for word, rather than from a system improvising something plausible.
Two rules keep this safe. The automation answers only from your approved list, and when the question isn't on the list it says so instead of guessing. A confident wrong price at 11 PM is worse than no reply, because you will either honour it or start the relationship by arguing about it.
2. Book now
Someone who asks the price and then asks "may slot ba bukas?" is ready. Telling them to call in the morning, right at that moment, throws away the part of the conversation you were waiting for.
A booking button is the easy part. What matters is whether the times behind it are genuinely open, which means one calendar has to be the truth, or you'll double-book by the second week. That's a bigger subject than this article and it's covered properly in the booking guide.
Book them, confirm by text, and let the confirmation carry a way to change the appointment without messaging you again.
3. Do not answer, route
"Ang sakit ng ngipin ko, ano po gagawin ko?"
No automation should answer that, and neither should the front desk. Symptoms, medication, whether something is normal after a procedure, whether a treatment is safe for a particular person: all of it goes to a dentist, and at midnight the honest reply says so.
There's a smaller bucket inside this one, and it can't wait until morning. The American Dental Association's guidance on what counts as a dental emergency names three situations as potentially life threatening: bleeding that will not stop, swelling that could compromise the airway, and trauma involving the facial bones. Anyone describing one of those should be sent to a hospital emergency department now, not told to wait for you to open.
Write that line yourself, have your dentist approve it, and keep it short.
If you have bleeding that will not stop, swelling that is affecting your breathing or swallowing, or an injury to your face or jaw, please go to the nearest emergency room now. We will follow up with you as soon as we open.
Everything else clinical gets an acknowledgement and a place at the front of the morning queue.
4. Hold for a person
Billing disputes, HMO approvals with an unusual wrinkle, a complaint, anything about a specific patient's record, anything where the reply commits the clinic to something.
There isn't much to do here, but it's worth doing properly. The system should recognise that it's out of its depth, say so, take the patient's name and number, and flag the conversation. It must not guess, and it must not go quiet after admitting it can't help.
Write the promise with a time in it
"Thanks for your message! We will get back to you as soon as possible."
At 10:47 PM that sentence tells the patient nothing they didn't already know. It mostly exists so the clinic feels like it answered.
Compare it with a reply that has a time in it:
Our clinic is closed for the night. Jen opens the inbox at 9:00 AM tomorrow and yours will be first. If it's urgent, here is what to do tonight: [emergency line]
Or in the register most Philippine patients actually write in:
Sarado na po kami ngayon. Bukas po ng 9:00 AM, si Jen na po ang sasagot sa inyo. Kung emergency po, [emergency line].
You can keep the second one or break it, which is what makes it a promise. That cuts both ways. Don't write a time into the message unless somebody's morning genuinely starts with the inbox, because a broken 9:00 AM promise is worse than the vague version. The patient waited for that one.
Two smaller points that come up every time. Say plainly that the reply is automated, in the first message, because a patient who works it out on their own assumes you were hiding it. And don't let the auto-reply be the only thing that fires. An acknowledgement that answers nothing is the failure dealt with at length in the Messenger guide, and it's the same failure whether it happens at noon or at midnight.
Inbound runs all night. Outbound does not.
Get this one wrong and patients mute you.
Answering a message somebody just sent you at 1 AM is a service. Sending an unrequested message at 1 AM is a nuisance, and it teaches the patient to ignore your next one. So set an outbound window, roughly 8 AM to 8 PM, and check that everything scheduled actually lands inside it.
That check is the step people skip, because reminders are usually configured as an offset rather than a time. "Two hours before" sounds harmless until you apply it to the first slot of your day.
| Reminder rule | Appointment | Fires at | Verdict |
|---|---|---|---|
| 24 hours before | Monday 9:00 AM | Sunday 9:00 AM | Fine, though nobody at the clinic can act on a reply |
| 2 hours before | Tuesday 7:30 AM | Tuesday 5:30 AM | No. You will wake them |
| 1 hour before | Tuesday 8:00 AM | Tuesday 7:00 AM | Borderline, and acceptable if your patients commute early |
| 12 hours before | Monday 9:00 AM | Sunday 9:00 PM | Late, and again nobody is on duty for the reply |
| 48 hours before | Monday 8:00 AM | Saturday 8:00 AM | Fine |
Run that arithmetic against your earliest appointment of the day, not a typical one. The offset that works nicely for a 2:30 PM cleaning is the one that texts your 7:30 AM patient before dawn.
Two more rules go with it. Don't schedule an outbound send for a time when nobody can read the reply, which is the Sunday problem in the table. And hold any batch queued to go out during a closure: reminders sent on Good Friday for appointments the following week land in an inbox nobody is watching.
Whether your messages arrive at all on Philippine networks, and why links get blocked, is a separate subject with its own rules. The wording itself is covered in the template article.
What the front desk does at first light
Automation moves the work. It doesn't delete it. If nobody owns the morning, the queue just becomes a different kind of backlog.
Give it twenty minutes before opening and work it in this order.
Escalations first, oldest at the top. Not newest. The person who messaged at 9 PM last night has been waiting longest and is nearest to booking with somebody else, so sorting the inbox by recency inverts exactly the priority you want.
Then last night's bookings, checked against today's reality. The system booked against the calendar as it stood at midnight. If a dentist called in sick or a chair is down, those appointments need moving now, while there's still time to offer the patient something else.
Then everything else, including the enquiries the system answered by itself. Read a handful. You're checking whether the answers still match your prices and your hours, and this is how you catch a knowledge base that has quietly gone out of date.
Once a week, read the conversations where the system said it didn't know. That list is your backlog of answers to write, and it's the cheapest improvement available to you.
Common mistakes
Automating the acknowledgement and calling it done. "PM sent po" at midnight is an unanswered message with extra steps.
Leaving the calendar open through a closure. The system will book Good Friday, and somebody will turn up.
Letting the night system talk about clinical things. Draw the line in writing, and have the dentist approve the exact wording of the refusal.
Publishing a landline as your after-hours contact. An unanswered ring at 9 PM leaves you nothing at all, not even a record that somebody tried.
Sending outbound at night because the system was switched on. See the table above.
Promising a 9:00 AM reply with nobody assigned to 9:00 AM.
Buying before counting. If your night volume turns out to be four messages a week, fix it with a better pinned post and your own phone.
What this looks like when it is running
Most of the above you can set up yourself, and if your evenings are quiet you should. Nothing here needs a vendor.
The version that needs software is the one where the volume is real and nobody has a spare evening. Here is the same flow with Smile & Skin Clinic, the example clinic from our home page. Ms Reyes messages the Page at 10:47 PM asking about a cleaning. The assistant answers with the clinic's own price and duration, both taken from the list the clinic approved rather than from a guess. She asks what's open tomorrow, and it offers two times that are genuinely free because it checked the live calendar instead of a static schedule. She takes 2:30 PM. The booking is written, the confirmation text goes out straight away, and the reminder is scheduled for a sensible hour. In the morning Jen sees a booked appointment instead of a question to answer.
That's what OtterFlow does: it answers patient enquiries from what the clinic approved, in English, Taglish or Bisaya, books only times that are really open, and sends the confirmation and reminders afterwards. When a message is clinical, or when it doesn't know, it says so and hands the conversation to a person rather than filling the gap. We're a small team in Cebu, currently piloting with Cebu clinics, and the pricing is on the home page. If your nights look like the ones in this article, a fifteen minute call will tell you whether it's worth it faster than a trial will.
What to do this week
- Run the night audit. Thirty days, three numbers.
- Sort a week of night messages into the four buckets and see which one dominates.
- Write the answers for bucket one: prices, hours, location, HMO, preparation.
- Get the dentist to approve the clinical refusal and the emergency line, word for word.
- Block your closures in whatever calendar your bookings will come from.
- Work out where your reminders fire for your earliest appointment of the day.
- Assign the morning queue to a person by name, with a start time.
- Only then automate anything.
Steps one to seven cost nothing and are worth doing whether or not you ever buy software. Step eight is only worth doing once the first seven are done, because automation applied to an undecided process just produces the wrong answer faster.
Frequently asked questions
Should we tell patients the after-hours reply is automated?
Yes, in the first message. Filipino patients aren't offended by an automated reply that's genuinely helpful, and they're unimpressed by one pretending to be Jen at midnight. Saying it plainly also sets expectations about what the system can and can't settle.
Is it legal to collect a patient's details through an automated chat at night?
The Data Privacy Act of 2012 applies at midnight the same as at noon. In practice that means telling the patient what you're collecting and why, keeping it to what the booking needs, and knowing who holds what. When a clinic uses a booking tool, the clinic is the personal information controller and the tool is a processor acting on the clinic's instructions. Ours is set out in our privacy notice if you want to see the shape of it.
Do we need a dentist on call to do this properly?
No, but you do need a decision about what happens when somebody is in pain at 2 AM. The minimum defensible answer is the emergency-room line above plus a place at the front of the morning queue. Anything beyond that is a clinical policy question for your dentist, not a software one.
What about phone calls after hours?
A missed call tells you almost nothing and gives the patient nothing. If your published after-hours number is a mobile, at least you get a log to call back from. Better is to point after-hours callers at a channel that captures the enquiry, and to make that channel obvious on your Page, your Google listing and your voicemail.
Will this actually get us more appointments?
It gets you more answered enquiries, which is the part you control. Whether those become appointments depends on your prices, your availability and how the rest of the visit goes. Anyone selling you a percentage hasn't seen your clinic.
The one thing to take away
Most of your week is hours when nobody is there, and nobody has decided what the clinic says during them. That is the real problem, and it's a writing job before it's a software one: four buckets, a set of approved answers, a refusal your dentist signed off, and a name against the morning queue.
Do that much and you'll know exactly what you're automating. If you'd rather have someone build it around your prices, hours and booking rules and then keep it running, that's the conversation to book with us.