A WhatsApp automation demo can follow a clean menu. A real business conversation may contain a booking request, missing details and a request for human help in the same message. Design the flow around those interruptions before connecting it to a live calendar.
A patient at a dental clinic writes: 'oi, quero saber se o doutor atende amanhã pq minha filha tá com dor de dente desde ontem e não consegui dormir.' That's not a clean intent. It's a booking request, an urgency signal, a child patient indicator, and an implicit expectation that someone will respond with empathy - all in one message.
Separate message interpretation, business validation and human handover. Interpretation extracts a possible intent. Validation checks the calendar and the allowed action. Handover routes uncertainty or a health-related concern to the appropriate staff; the bot should not diagnose the patient.
The WhatsApp Business Platform provides the messaging APIs. In a Node.js integration, a webhook receives the message, a classifier proposes an intent and a conversation state machine records the next allowed step. Check the platform rules before sending outbound reminders.
An example state machine is GREETING to INTENT_CAPTURE to ENTITY_EXTRACTION to AVAILABILITY_CHECK to CONFIRMATION to BOOKED. Store it under a stable conversation identifier, define expiry according to the business and avoid keeping unnecessary patient data. A message outside the allowed transition should trigger clarification, not a guessed booking.
A reminder can offer CONFIRM or RESCHEDULE and show the appointment in the patient's timezone. Treat the send timing as a configuration choice. Record sent, delivered, confirmed, cancelled and attended statuses to assess the flow without inventing a before-and-after no-show rate.
I will not claim an uma parcela significativa drop. The no-show figure belongs to a published case study with client attribution, not to a workflow template. The reminder shape above is the documented feature.
Provide a visible route to a person and use explicit escalation rules for urgent or sensitive messages. A sentiment score can miss a health concern. Test missed escalations and make sure staff can see the conversation context before taking over.
Budget for setup, hosting, maintenance and messaging. To estimate a return, compare the full running cost with the contribution from appointments actually retained or staff time actually saved. Neither a reminder feature nor a monthly subscription proves payback in the first month.