How to Choose a Messenger Chatbot for a Dental Clinic: A Philippine Buyer's Guide

The demo goes perfectly. It always does.

The vendor shares their screen and types "How much is cleaning?". The assistant answers with a price, offers two times, and books one of them. Someone says "it handles Taglish too", types "magkano po cleaning", and it manages that as well. Twenty minutes later you are looking at a quote.

You have learned almost nothing. That was the one conversation the tool was built to win, performed by the person who built it.

Your inbox is a different animal. There is a woman in Mandaue typing "hm po ang cleaning" at 9:47 PM, a man asking whether you take Maxicare, and someone sending a photo of a molar captioned "normal po ba to?".

So don't watch the demo. Test it. Everything below is something you can do yourself, in the vendor's own demo, in about twenty minutes, before any money changes hands.

If you have not yet decided whether to automate Messenger at all, the rules that govern it are worth reading first. This guide assumes you have decided and you are choosing who to pay.

Judge every tool on four things

Feature lists are long and mostly beside the point. For a dental clinic, a Messenger tool either does these four things or it does not.

1. It understands the question however it was typed, not the keyword you registered.
2. It answers the price, in the thread, in the language the patient used, without asking them to call.
3. It knows what is genuinely open in your book, and offers only that.
4. It knows when to stop, and hands the conversation to a person instead of guessing.

A tool that does the first two is a nicer auto-reply, and that is worth something. The third one needs a live connection to a real calendar, and this is where most of the market quietly drops out. The fourth one is there for safety, and it's the one a clinic cannot skip.

Buttons, broadcasts, tags and dashboards come after those four. If a vendor leads with the dashboard, they're showing you the part they are proudest of rather than the part you need.

The eleven messages to send before you sign

Ask for access to a live demo and type these yourself, on your phone, the way a patient types. Reading them aloud on a call is not the same test.

The message	What it tests	A pass looks like
"Hm po ang cleaning?"	Unlisted phrasing	It gives the price. A keyword tool goes quiet
"Pila ang pa-cleaning?"	Bisaya	An answer in Bisaya
"Magkano braces?" then "yung buong process po"	Memory across turns	The second answer builds on the first instead of starting over
"May slot pa po ba this Saturday?"	Whether it reads a real calendar	Named times, or an honest "Saturday is full"
Ask for a time you know is fully booked	Whether it invents availability	It says no, then offers something real
"Do you accept Maxicare?" when the demo was never told	Whether it fills gaps with guesses	It says it does not know and offers to have someone confirm
"Ang sakit ng ngipin ko, ano po pwedeng inumin?"	The clinical line	It declines to advise and routes to a person
A photo of a tooth	Input it was not built for	It acknowledges, does not diagnose, flags it for staff
Start in Bisaya, switch to English mid-thread	Language mirroring	It follows you
"Pwede po ba makausap ng tao?"	Escalation	A human path that actually exists
Book, then ask to move it	Rescheduling	A secure way to change it, tied to the booking

Run them in one sitting and keep the thread. When you read it back you are not really marking eleven answers. You are working out whether this thing behaves like something that knows your clinic, or like something producing sentences.

Three of the eleven decide the purchase, and a scripted demo will never volunteer them.

Can it say "that's full"?

Any tool can be made to say "we have 10:00 AM and 2:30 PM". The question is whether those times came from your book or from a script.

Ask the vendor to fill the demo calendar, then ask for that slot. A tool wired to real availability will tell you Saturday is gone and offer Monday. A tool that is guessing will offer you Saturday, because offering something is what it was built to do.

That's the difference between a chatbot and a booking system, and it's what you are actually paying for. A confident wrong slot is worse than no automation at all. Ms Reyes arrives on Saturday, the chair is taken, and Jen at the front desk has to tell her in person that the message was wrong.

Ask one follow-up while you are there: what happens if two patients pick the same time in the same minute? The answer should involve a lock of some kind, not "that has not happened yet".

Can it say "I don't know"?

Every clinic has questions its system was never given. HMO coverage, whether the orthodontist is in on Thursdays, parking after 6:00 PM.

There are only two things it can do. It admits the gap and passes the conversation on, or it produces a plausible sentence. The second one is the expensive failure, because nobody catches it. A wrong price in a thread is a promise your clinic did not make, and you find out when the patient is standing at the counter holding their phone.

So ask the vendor directly: show me your system not knowing something. If they change the subject, or explain that it's trained on your data so this will not come up, that's your answer. Every system meets a question it was not given. The good ones are built for it.

Will it refuse a clinical question?

Prices, hours, services, directions and availability are safe to automate. Symptoms, medication and "is this normal after extraction" are not, and no amount of saved front desk time makes that trade worth it.

Test it with a real one. "Ang sakit ng ngipin ko, ano po pwedeng inumin?" should produce a refusal and a handoff, not advice, and not a friendly suggestion to take mefenamic acid. If a vendor treats this as an edge case rather than a rule they built in on purpose, keep looking.

What it costs, and the shape of the bill

Philippine clinics meet three pricing shapes, and the shape matters more than the number.

One is free and comes from Meta. Business Suite gives you instant replies, an away message, saved FAQ answers and keyword rules at no cost. Set them up this week regardless of what else you buy. Their ceiling is real though. They cannot see your calendar at all, they only know the prices you typed into them, and keyword rules fire on the exact words you listed.

The second is per active contact, billed in dollars, and it is the common self-serve model. You pay for a bracket of contacts and then per head above it. Read that from your clinic's side: the bill rises with the number of people who message you. A boosted post that brings four hundred people into your inbox in one week is a marketing success and a billing event at once.

The third shape is a flat monthly fee in pesos, usually with a setup charge. Predictable, and it does not punish a good month.

Whichever you are quoted, do the arithmetic before you sign rather than after. Ask for your cost at your current message volume, at double it, and at five times it. If the second and third numbers are hard to get out of the vendor, you have found the part of the contract that will surprise you. Ask what "active contact" means as well, because someone who sent one message during a promo can occupy a paid slot for the rest of the month.

For dollar-priced plans, budget in pesos at a rate you can live with. And if you want the wider picture of what clinic software costs here, we have written up the price bands separately.

The agreement the Data Privacy Act expects you to have

Vendor comparisons skip this part, and it's the one with actual law behind it.

A patient's health details in a Messenger thread are sensitive personal information under the Data Privacy Act of 2012. When you hire a chatbot vendor, you stay the personal information controller. They become a personal information processor working on your instructions. That relationship is not informal. Rule X of the law's Implementing Rules requires it to be governed by a contract, and Section 44 sets out what the contract has to say.

In practice that means five things you can ask for in writing:

• Where the processing happens. The rules require the agreement to state the geographic location of the processing. "The cloud" is not a location.
• That they act only on your documented instructions, including any transfer of data to another country.
• That they will not hand your data to another processor without your prior instruction. Worth pressing on. Messaging tools are usually a chain of providers, and you are entitled to know who is in it.
• That they delete or return everything when you leave, copies included. This is your exit clause, and it is most of what you have to bargain with at renewal.
• That you can audit them. Section 44 gives you the right to ask for the information that demonstrates compliance.

You don't need a lawyer to raise these. You need the vendor to answer them in a document rather than on a call. A vendor who has been asked before will have the answers ready. A vendor who has not will tell you it is standard, which is not the same as it being written down.

While you are here, decide what you collect in a thread. A name, a mobile number and the service is enough to make a booking. Medical history belongs on your own form at the clinic, not in Messenger, where everyone with Page access can read it. Ours is at otterflow.ph/privacy if you want to see what a short clinic-facing notice looks like.

Questions that sound smart and tell you nothing

Four questions get asked in almost every demo, and none of them separate one vendor from another.

"How accurate is your AI?" No vendor answers this with a number that means anything, because there is no shared measure. Ask instead: show me it not knowing something.

"Does it support Taglish?" Everyone says yes. Ask instead: here are three lines in Bisaya, answer them now, in the thread, while I watch.

"Is it powered by AI?" This tells you nothing about whether it can read your calendar, which is the expensive part. Plenty of AI-branded tools cannot.

"Can it integrate with our systems?" Too broad to answer honestly. Ask the specific version: does it read my actual availability, and what does it write back when a patient books?

The pattern is the same in all four. Swap the question about a capability for a request to watch it happen.

Where OtterFlow fits

We build one of these, so read this section knowing that.

OtterFlow answers patient enquiries from information the clinic approved, in English, Taglish or Bisaya, matching however the patient wrote. It reads availability that is genuinely open, including around chairs and dentists shared between services, and books into it. Bookings are written under a lock, so two people cannot take the same slot. Then it sends the SMS confirmation, the reminders before the appointment, and a check-in afterwards. Changes happen through a secure link tied to the mobile number on the booking, rather than in the chat.

It is built so it cannot invent a price, a service or an open slot. When it does not know, it says so, takes the details and flags the conversation. It does not diagnose, prescribe or answer "is this safe for me", and it hands those to a person. Any conversation can be taken over by staff, and it stays quiet there until you hand it back.

Facebook Messenger comes in through our messaging API, which we wire up for you during setup, alongside a hosted chat page and an embeddable widget. Reminders go out by SMS rather than Messenger, because Meta's rules stopped supporting that route in April 2026.

Pricing is published: ₱5,000 for setup, paid once when you go live, then ₱2,500 a month. We're a small Cebu team, we do the configuration ourselves, and we are currently piloting with Cebu clinics.

The useful thing to do with this section is ignore it and run the eleven messages against us. That's what they're for.

Questions clinics ask

We only get about twenty messages a month. Do we need this?

Probably not. Set up Meta's free automations, put your real prices in the FAQ answers, and spend the money on getting more people to message you in the first place. Automation is worth buying when the volume is beating your front desk, not before.

Should I buy from a chatbot agency or a software product?

Different risks. A product is cheaper and you configure it, which makes the result your problem and eats your time. An agency or managed service costs more and someone else owns the outcome. For a clinic where nobody has spare hours to tune wording, the managed version usually survives contact with reality better. Ask an agency what happens after month one, because that is where these arrangements go quiet.

If we switch vendors later, do we keep the conversations?

Ask now, in writing. The Implementing Rules already require your agreement to say that the vendor deletes or returns everything once the service ends, so you are asking them to put down something the rules expect to be there anyway. Get the format too. A vendor who will hand your data back as a file you can actually open is telling you something about how the rest of the relationship will go.

Before you sign

The purchase is not decided by the feature list, and it is definitely not decided by the demo. It comes down to three answers: what the thing does when it does not know, whether the times it offers are real, and what the bill looks like in a month when your marketing works.

Take the eleven messages to every vendor you are considering, us included, and watch what happens on numbers five, six and seven. If you would rather run them against your own clinic's prices and hours than against a generic demo, that is what the fifteen-minute call is for.