The one thing that kills most WhatsApp automation for small businesses

I’m building an AI receptionist that lives inside WhatsApp Business, for appointment-based professionals: physios, osteopaths, psychologists, small clinics. Booking, rescheduling, cancellations, FAQs, contacts. All inside the chat the client already uses.

Building in public here because one constraint shaped the entire product, and I almost missed it.

The constraint nobody talks about

Every "WhatsApp automation" pitch to a solo professional dies on the same objection:

"So I lose my number and three years of conversations with my patients?"

And usually the honest answer is yes. Most automation platforms make you migrate your number to their infrastructure. The moment you do, the WhatsApp Business app on the phone stops working, the chat history is gone, and the human can no longer step in from their phone.

For a corporate support desk that's fine. For a physiotherapist working alone, that number is the business. It's on the door, on Google Maps, in every patient's contacts. Nobody is going to hand it over to a stranger's SaaS.

So the requirement became non-negotiable: same number, same app on the phone, same history, human takeover at any moment, AI handling everything else in the background. That single requirement eliminated most of the obvious platforms I evaluated, and cost me weeks of rework. It's also, I now think, the actual moat, and it's a positioning decision much more than a technical one.

I started thinking "any small business". Wrong. Automation only pays for itself where a missed message equals a lost, dated, high-value slot. That's appointment-based work, and the pain scales with how often the professional has both hands busy. A physio with a patient on the table cannot answer. A restaurant owner can.

Second lesson: this is not a horizontal product. Language, tone, and booking rules differ enough per vertical that a generic bot feels wrong immediately. I'd rather be obviously right for one type of professional than vaguely useful for everyone.

Product is built, waiting list is open, first beta users are lined up. Flat monthly subscription, no per-seat pricing, no usage tiers to decode. I'm doing this solo, so every hour spent on the wrong vertical is expensive.

1. Before spending on marketing for a second vertical, how many conversations with real professionals did you need to be confident it was worth it? I keep oscillating between "five is enough" and "five is nothing".

2. Narrow launch in one country done properly, or two countries at once when you already speak both languages? Everyone I ask has a strong opinion and they contradict each other.

Happy to talk about the number-migration trap in the comments. It's the part nobody writes about, and in my experience it's where most of these products quietly lose the customer.

wably.app