In a large part of the world the enquiry does not arrive on a web form; it arrives as a WhatsApp message to the business number, often outside working hours, often as one line: 'price?' or 'available tomorrow?'. A business that answers in seconds books the customer; one that answers next morning finds the customer went elsewhere. The WhatsApp Business API makes the first response a system rather than a person's phone.

Acknowledge instantly, qualify gently

The first automated reply should feel like a person: a greeting with the business name, an acknowledgement of what they asked, and one question that moves things forward — which service, which location, which day. Buttons and lists make this quick on a phone. Keep the automated part to two or three exchanges; the goal is to collect enough to book or to hand to a person with context, not to run a long script.

Book into the real calendar

Connect the flow to the actual booking system — a clinic's scheduler, a calendar tool, a CRM — and offer real slots. The customer picks one, the booking is created, a confirmation goes out with the address and what to bring, and reminders go out the day before and the morning of. No-shows drop when reminders are on time and easy to reschedule from.

Hand off cleanly

Any message the flow does not understand, any request for a person, and any enquiry over a value threshold goes to a human with the whole conversation attached — in a shared inbox or the CRM, not on one employee's personal phone. Set working-hours behaviour explicitly: outside hours, collect the details and promise a callback time, then create the task.

Stay inside the rules

Business-initiated messages outside the 24-hour window need approved templates; keep them useful (confirmations, reminders, follow-ups) rather than promotional. Ask for opt-in before marketing messages. Log every conversation to the CRM so that when the customer calls, whoever answers knows what was said.