For many clinics, salons and local service businesses, WhatsApp is now the front door. Clients message to ask about prices, move appointments and send photos, often outside opening hours. Running WhatsApp for your business on a single phone at the front desk works when you are small, but it breaks quietly as you grow: messages are missed when that phone is busy, nobody knows who replied to whom, and the conversation history lives in a device rather than in your client records. This guide covers how to run it properly without losing enquiries.
Move from one phone to a shared inbox
The first step is structural. The WhatsApp Business app on one handset was designed for very small teams. Once more than one or two people are answering, you need a shared inbox connected to the WhatsApp Business Platform (the official API), using your own business number.
A shared inbox gives you three things a phone cannot:
- Several people working at once, each with their own login, so the inbox is not tied to whoever holds the phone.
- A record of who did what, so you can see who replied, when and what was said.
- Continuity, because conversations stay with the business when staff change shifts, roles or jobs.
In Medzelo, for example, WhatsApp messages land in a shared inbox, each thread links to the matching lead or client, and, with lead creation switched on in the AI agent settings, new numbers can be added as leads. Read more about WhatsApp and Meta leads.
Give every conversation an owner
Shared inboxes have their own failure mode: everyone assumes someone else will reply. The fix is ownership. Decide how conversations are assigned, for example new enquiries to the person on reception duty, existing clients to their usual team member, and anything about payments to the practice manager.
Then make ownership visible. Each conversation should show who owns it and whether it is waiting on you or on the client. At the start and end of each shift, someone checks for unassigned and unanswered threads. That five-minute routine prevents most lost enquiries.
Set response standards the team can meet
Clients notice how fast you reply on WhatsApp, because the app shows when a message was delivered and read. Agree response standards and write them down. A simple version might be:
- New enquiries during opening hours get a first reply within a short, agreed time, and a booking offer in that first reply where possible.
- Existing clients asking about an appointment get a reply the same working day.
- Messages received out of hours get an automatic acknowledgement that says when the team will reply.
Pick standards that match your staffing, then check them weekly. A promise of instant replies that you keep breaking is worse than an honest "we reply within the hour".
Use templates without sounding robotic
Templates save time and keep answers consistent. Write short replies for the questions you get every day: prices, opening times, parking, what a first appointment involves and how to reschedule. Keep them friendly and edit them for each client, adding their name and the specifics they asked about.
On the WhatsApp Business Platform there is a second kind of template that matters. Free-form replies are allowed within 24 hours of the client's last message. After that window, you need a message template that WhatsApp has approved before you can message again. Plan approved templates for the moments you know you will need them: appointment reminders, follow-ups after a visit and replies to enquiries that went quiet.
AI can help here, as long as a person stays in control. A sensible pattern is for AI to draft a suggested reply and for a staff member to approve or edit it before it is sent, with sensitive questions handed straight to the team.
Link chats to client and lead records
A WhatsApp thread on its own tells you very little. The same thread next to the client's bookings, payments, forms and notes tells you a lot. When conversations are linked to records:
- Staff can see a client's upcoming appointment before replying to "can I move Thursday?"
- New enquiries become leads with a stage, so you can see how many turned into bookings.
- The history is in one place when a client calls, emails or walks in.
Facebook Messenger and Instagram direct messages raise the same problem. Bringing them into the same inbox is the long-term goal; check how mature each channel is in your tools before relying on it. The integrations page shows which Medzelo connections are available today and which are still in beta.
Data protection basics
Client messages often contain personal information and, for clinics, health information, which deserves extra care. This is not legal advice, and you should take advice on your own obligations, but a few habits are sensible for any business:
- Keep client chats off personal phones. Use a business account that the business controls.
- Limit access by role. Not everyone needs to see every conversation.
- Collect only what you need. Do not ask for medical details over chat if they belong in a proper consultation form.
- Get consent before marketing. Only send promotional messages to people who have opted in, and honour opt-out requests promptly.
- Know how long you keep chats and how you would find and export a client's messages if they asked.
The ICO's guidance for small businesses is a good starting point if you operate in the UK.
A weekly WhatsApp health check
Once the basics are in place, a short weekly review keeps them working:
- How many new enquiries came in, and how many have an owner?
- What was the typical time to first reply, in hours and out of hours?
- How many enquiries turned into bookings?
- Which questions came up repeatedly and need a better template or a website answer?
- Were any conversations left without a reply for more than a day?
Treat WhatsApp like any other front door to the business: staffed, organised and measured. The enquiries are already arriving. The work is making sure none of them fall through the gaps.
Run WhatsApp as a team, not from one phone
See how a shared inbox, linked client records and approved templates work together, using your own services and team structure.