Every channel into one queue
Messages from social channels and from the website land in a single team inbox on the WhatsApp Business API. The team sees one thread per patient, with the full history.
A private clinic ran patient conversations across four different messaging platforms. Moving every channel into one inbox cut the operational load by nearly a third.
Clínica Lucas Miranda opened in 2015 in Brazil. It is an aesthetic and wellness practice with a multidisciplinary team, built around personalized care.
Almost every patient conversation happens on messaging. Enquiries, bookings and cancellations all arrive the same way, in the same channel, at every hour.
The clinic had already worked through more than four messaging platforms. Each one was rigid where a medical practice needs to bend, and support was slow when something broke.
At one point the team ran two WhatsApp numbers at the same time. Around them grew a ring of internal coordination groups, which is what a team does when the tool will not hold the work.
What was actually going wrong before anything changed, and why it stayed that way so long.
The problem was never the volume of messages. It was that nobody could see the whole conversation in one place.
With four tools in play, a patient could be answered twice or not at all. Supervision was impossible, because there was no shared view to supervise.
Qualification suffered in the same way. Someone asking about a first treatment sat in the same queue as a confirmation, so the team spent its attention on whatever arrived last.
Built inside the tools the company already paid for. Nothing exotic, put together in a different order.
Messages from social channels and from the website land in a single team inbox on the WhatsApp Business API. The team sees one thread per patient, with the full history.
A flow captures the enquiry and qualifies it before a person is involved. Booking and confirmation run on the same flow, so the calendar never drifts from the thread.
Internal notes sit inside the thread, so a manager can follow a live conversation and step in only when it matters. Broadcast campaigns go out from the same place.
The before column is where the company started. The after column is where it landed once every system was running.
| Metric | Before | After |
|---|---|---|
| Messaging platforms in use | More than four | One |
| WhatsApp numbers in use | Two | One |
| Parallel coordination groups | In use | Gone |
Conversational engagement today is not a differentiator, it is a basic necessity. Being efficient in this channel is an obligation.
Every story leaves one. Reading it is cheaper than learning it the slow way.
The clinic did not start with an AI project. It started by putting every conversation in one place, which is the boring step that makes the rest possible.
The feature the team uses most is the internal note, not the bot. Visibility came before automation, and the savings followed.
The campaign result says something else. Once the patient history lives in the thread, a simple birthday message becomes a revenue line.
The points the story turns on, in the order they happened.




The auditoría de IA y operaciones finds it, prices it, then hands you a plan in two working days. Your fee comes off the first thing you build with us.