What exactly is included in WhatsApp automation for a clinic?+
The full engine, not a chatbot widget. We set up the official WhatsApp Business API on your clinic's number, complete Meta business verification, and build the conversation flows end to end: instant replies to every enquiry with qualification questions, an in-chat booking flow with live slot selection synced to your calendar or practice-management system, T-24h and T-2h appointment reminders with confirm/reschedule buttons, post-visit review requests routed through a satisfaction pulse, report-ready notifications for diagnostics, an FAQ auto-answer library covering timings, pricing, preparation and directions, and human handoff rules with a shared team inbox. You also get front-desk training, a template library approved by Meta, and a monthly report covering reply times, chat-to-booking conversion, no-show rate and review velocity. We write the copy, you approve it — every message sounds like your clinic, not a robot.
How long does setup take before flows go live?+
Two to three weeks for most clinics. Week one is flow mapping: we document your enquiry sources, booking rules, doctor schedules and the most common patient questions, then draft every conversation for your approval. In parallel we begin Meta business verification on your number — this is the step with external dependency, typically 3–7 working days depending on how quickly Meta processes your business documents. Week two covers API configuration, calendar/CRM integration, and message template submissions (Meta reviews templates, usually within 24–48 hours). We launch with conservative handoff rules — the automation hands over to humans early and often in week one while we watch live conversations, then we progressively let it handle more as the flows prove themselves. If your number is currently on the regular WhatsApp or WhatsApp Business app, we manage the migration to the API carefully so you keep the number and lose no chat continuity for patients.
How does pricing and billing work, and what are 'API costs'?+
Our Core plan is ₹12,000/month, Growth with broadcast campaigns is ₹20,000/month, and multi-location or hospital deployments are custom-quoted. On top of our fee, Meta charges per-conversation API fees — these are passed through at cost with no markup. In India, a utility conversation (reminders, confirmations, report alerts) costs roughly ₹0.12–₹0.35 and marketing conversations around ₹0.78–₹0.88; service conversations initiated by the patient are free within the 24-hour window. For a typical single-location clinic handling 300–600 conversations a month, API costs usually land between ₹500 and ₹2,000 — small relative to a single recovered booking. Billing is monthly in advance, no long lock-in; we ask for a 90-day initial commitment because flows need one optimisation cycle to hit their numbers. Setup and verification are included in the first month rather than charged as a separate onboarding fee.
How is this different from your appointment booking automation service?+
They overlap on one flow and differ everywhere else. Appointment Booking Automation is channel-agnostic scheduling infrastructure: self-serve booking from your website, Google Business Profile, Instagram and WhatsApp, calendar sync, waitlists and no-show recovery. WhatsApp Automation is a communication engine for one channel — the channel with a 98% open rate — and covers much more than booking: instant enquiry response, FAQ automation, report-ready alerts, review requests, post-procedure sequences and broadcast campaigns. If your biggest leak is patients who can't book outside front-desk hours, start with booking automation. If your biggest leak is slow replies, unanswered chats, no-shows and a silent review profile, start here. Many partner clinics run both — the booking engine handles scheduling logic while the WhatsApp engine handles every conversation around it — and we discount combined retainers because the integration work is shared.
We have international patients / we're a clinic outside India. Does this work with SMS?+
Yes. WhatsApp is the dominant patient channel in India, the UAE, the UK and Southeast Asia, so clinics in Dubai, Singapore, Manila, London and Kuala Lumpur run the same flows we build for Indian clinics — often bilingual (Arabic/English, Tagalog/English). For the US market, where WhatsApp penetration is low, we deploy the identical automation logic over SMS/text: instant text-back on enquiries, booking links, T-24h/T-2h reminders and review requests via A2P 10DLC-registered numbers, which is the compliant route for business texting in the US. The flows, timing and reporting are the same; only the transport layer changes. For clinics serving medical tourists — IVF, dental, cosmetic and orthopaedic practices in India treating patients flying in from the Gulf, Africa or the West — we run WhatsApp for the enquiry-to-arrival journey since that is the channel international patients already use to talk to Indian providers.
How do you handle messaging consent and DPDP compliance?+
Consent is engineered into every flow, not bolted on. Under India's Digital Personal Data Protection Act 2023 and Meta's own policies, patients must opt in before receiving business-initiated messages. When a patient messages you first, that conversation is consent for the service context; for anything beyond it — reminders tied to a booking, review requests, recall campaigns — we capture explicit opt-in with a clear statement of what they'll receive and how to stop. Every list we message has a logged consent record (source, timestamp, scope), every template includes a working opt-out, and opt-outs are honoured instantly and permanently across campaigns. Marketing consent is always collected separately from service consent, never bundled. We also avoid putting clinical details in outbound templates — a reminder says you have an appointment, not what it's for — which matters for sensitive specialties. Data lives on India-region infrastructure for Indian clinics, and we support deletion requests end to end.
Will patients be annoyed by automation? When does a human take over?+
Patients are annoyed by two things: silence and robots that trap them. We engineer against both. The automation's job is speed and utility — answer instantly, show slots, confirm bookings, deliver reports — and its second job is knowing when to stop. Handoff rules trigger on clinical questions, symptom descriptions, complaint language, pricing negotiations, or the patient simply typing 'talk to someone'. The conversation then lands in a shared team inbox with the full transcript, an assigned owner and a response-time alert, so the human picks up with context instead of asking the patient to repeat themselves. In our partner data, satisfaction actually rises after automation goes live, because the median patient gets what they wanted — a slot, a report, an answer — in under a minute, and the patients who need a human reach one faster because the front desk is no longer buried in repetitive chats.
Is this the official WhatsApp API? What about grey-market tools that are cheaper?+
We only deploy the official WhatsApp Business API through Meta-authorised Business Solution Providers. Grey-market tools — bulk senders, cracked WhatsApp Web automations, unofficial APIs — are cheaper because they violate WhatsApp's terms. The predictable outcome is your clinic's number getting banned, often mid-campaign, taking years of patient chat history and your printed-on-everything phone number with it. For a clinic, that number is an asset on signboards, prescriptions and Google listings; risking it to save a few thousand rupees a month is a terrible trade. The official API also brings things grey tools can't: the green verification tick (which measurably lifts reply rates), approved message templates that reliably deliver, granular delivery analytics, and multi-agent team inboxes. Every flow we run passes Meta's template review, which doubles as a useful quality gate — if a message wouldn't pass, it probably shouldn't be sent to a patient anyway.
Does this work for my specialty — diagnostics, dental, IVF, dermatology, hospitals?+
The engine is the same; the flows are specialty-tuned, and that tuning is most of the value. Diagnostics and imaging: report-ready alerts, fasting/preparation instructions, home-collection booking — call volume typically drops 40–60%. Dental: 6-month recall nudges, post-extraction care sequences, high-value treatment-plan follow-ups for patients who took a quote and went quiet. IVF and fertility: sensitive, medically reviewed enquiry handling, cycle-stage reminder sequences and document checklists before consults — with extra care on privacy since even an appointment reminder can be disclosive. Dermatology and cosmetic: before/after journey check-ins, session-package reminders, review requests timed to visible results rather than the visit. Hospitals: department-wise routing, OPD scheduling by doctor, pre-admission instruction packs and discharge follow-ups. In every case the clinical copy is reviewed with your doctors before launch — automation never gives medical advice, and anything resembling a clinical question routes to your team.
We're an international clinic — do you bill in rupees?+
No — international clients are quoted and billed in their local currency. Clinics in the UAE receive AED pricing, US and Singapore practices are quoted in USD, UK clinics in GBP, and Southeast Asian clinics typically in USD unless a local-currency arrangement works better. The rupee prices on this page translate to roughly USD 145–290 per month for the Core and Growth tiers, with the same deliverables, the same official-API-only policy, and reporting calls scheduled in your timezone. Payment is by international card, wire or Wise, invoiced with applicable tax documentation for your jurisdiction. We currently run WhatsApp and SMS automation for healthcare providers in Dubai, Singapore, London and Manila alongside our Indian partner base, so region-specific compliance — UAE telecoms rules, UK GDPR, US TCPA/A2P registration for the SMS variant — is handled as part of setup, not discovered as a surprise later. If you operate across countries, multi-region deployments are quoted custom with a single consolidated report.