Enquiries that wait until morning
A patient messages on WhatsApp at 9 PM or fills in the website form during lunch. The reply arrives the next afternoon, and by then they have booked with the clinic that answered first.
An AI assistant for clinics answers booking enquiries within minutes, reminds patients before they forget, and gives the front desk a short brief each morning. It never gives medical advice: clinical questions go straight to your staff, and compliance requirements are scoped with you before anything is built.
A patient messages on WhatsApp at 9 PM or fills in the website form during lunch. The reply arrives the next afternoon, and by then they have booked with the clinic that answered first.
Appointments are confirmed once, weeks ahead, and then forgotten. A gap is discovered when nobody walks in, and rebooking is a call the front desk never has time to make.
The check-in after a procedure, the review request and the nudge for the next session are each small. Each depends on someone remembering during a full clinic day.
| When | The assistant | You or your team | Result |
|---|---|---|---|
| A new enquiry arrives by WhatsApp or the website form | Replies within minutes with opening hours, your approved prices and a booking link, and asks the practical questions the desk needs. A symptom or treatment question is not answered; it is passed to staff with the thread attached. | Front-desk staff answer anything clinical and confirm the booking. | Every enquiry gets a prompt first reply, and every clinical question has a named owner. |
| 48 hours and 24 hours before each appointment | Sends a reminder by WhatsApp or SMS with confirm and reschedule options and writes the answers into the calendar. | The front desk reviews the unconfirmed list at 4:00 PM the day before. | A confirmed schedule, with cancelled slots offered to the waiting list. |
| An appointment is marked as a no-show in the practice system | Drafts a short, kind rebooking message offering two open slots. | Front-desk staff approve the message before it is sent. | A missed appointment gets a rebooking offer the same day instead of silence. |
| Two days after a visit | Drafts a check-in from the template your clinician approved for that treatment type. If the patient replies positively it follows with a review request linking your Google Business Profile. | A clinician approves each template once. Staff read any reply that mentions a concern. | Follow-ups happen on schedule, and worries reach a clinician quickly. |
| Every day at 7:30 AM | Compiles yesterday's bookings and cancellations, unanswered enquiries, gaps in today's schedule and ad spend from Meta and Google. | The clinic manager reads the brief and assigns the open items. | The manager starts the day knowing which items need a decision. |
| A consumable such as gloves, anesthetic or skincare stock falls below its reorder level | Checks the stock sheet and drafts a purchase request to the usual supplier with the quantity. | The practice manager approves the order. | Supplies are reordered before a treatment room runs short. |
The daily brief lands with the manager: three cancellations overnight, two enquiries still unanswered and yesterday's ad spend.
A WhatsApp enquiry about a facial treatment gets a reply with the booking link. The patient then asks about a skin reaction, so the thread goes to a nurse.
The front desk clears the handover queue, answering the clinical questions the assistant has set aside for staff.
Tomorrow's unconfirmed appointments arrive as a short list, and the desk phones the two who have not replied.
A no-show from the morning has a drafted rebooking message waiting. The desk approves it and it is sent.
Tomorrow's post-visit check-ins are queued, each from a template the clinician approved.
If a tool has an API or an export, it can usually be connected.
The assistant handles logistics: hours, prices you have approved, and booking. Any question about symptoms, results, medication or suitability goes to a clinician, and the patient is told a team member will reply.
Clinical records remain in the systems scoped for them. The assistant works from booking details and approved templates, and each workflow is limited to the access it needs.
Requirements such as HIPAA in the US depend on your tools and data flows. We scope them in discovery, before the price is fixed, and we do not claim compliance in advance.
The assistant drafts. A person on your team sends.
This isn't a template with your logo on it. Every build starts from how your business actually runs — so there's no off-the-shelf demo, and we won't pretend otherwise.
We map how your week and your business actually run, and pick the first tasks worth handing over.
On the strategy call we build one of your real tasks with AI, on screen — your data, not a generic demo.
We scope the build with you on a strategy session and quote it in writing — agreed before a single workflow is built.
The assistant is wired into your tools, with inputs set up for each person on your team.
We go live, then tune reminders, reports and sign-offs as your team settles in.
No. The assistant never gives medical advice, diagnoses or treatment suggestions. It handles logistics such as opening hours, approved pricing and booking. Anything clinical is passed to your staff with the conversation attached, and the patient is told that a team member will reply.
A receptionist bot talks to patients; this assistant also works for your team. Besides drafting booking replies it sends reminders, rebooks no-shows, chases follow-ups and tells the manager each morning what needs a decision. Staff approve rebooking messages and clinical replies.
We do not claim compliance for a build in advance. Requirements such as HIPAA depend on your tools, data flows and agreements, so we scope them in discovery before the price is fixed. The design keeps patient data in the systems scoped for it and limits each workflow to the access it needs.
Usually, yes. WhatsApp Business and SMS are common starting points, and a booking or practice management system can be connected if it has an API or export. We confirm each connection during scoping and tell you plainly if a system cannot be connected.
Your staff do. Reminders and approved-template messages can run on a schedule if you allow it, while rebooking offers, replies to concerns and anything unusual wait for a person. You decide per message type, and the rules are visible settings you can change.
Medical, dental and aesthetic clinics that lose bookings to slow replies or no-shows. The emphasis differs: an aesthetic clinic leans on enquiry response and review requests, a dental practice on recall and reminders. We shape templates and rules around how your clinic works.