These are the features clinics and their reception staff typically ask for in reminder and patient-messaging tools. Each is classified with the same honesty as the stated features in 03. Being asked for doesn't mean you should build it; most of these are already in the clinic's EMR or a WhatsApp provider's toolkit.
Demand signals are judgment from competitor feature lists (Weave, Open Dental, Apptoto, Fresha, Cliniko add-ons, Indian EMRs, Brazilian WhatsApp tools), not from interviews. The week 1–2 interviews in 08 must confirm them.
Legend: TS = Table stakes, D = Differentiator, X = Distraction, L = Liability. Priority: P0 = v1 of the tested wedge, P1 = next, P2 = later, — = don't build.
A. Confirmation and no-show reduction (the core; lean in)
| Feature | Demand signal | Category | Priority | Notes |
|---|
| Two-way WhatsApp Confirm / Reschedule / Cancel buttons | High. Fresha's WhatsApp is one-way, and the gap is visible. | D | P0 | Replies write back to the diary. Utility template, clinic's own number. |
| Morning "unconfirmed" list for reception | High. It replaces the daily phone round. | D | P0 | One WhatsApp message to the receptionist at 9 a.m. with tap-to-call numbers. |
| Waitlist slot refill | Medium-high. Few small-clinic tools do it. | D | P0 | First patient to accept gets the slot. The only feature that adds money rather than saving it. |
| Baseline and monthly "no-shows prevented, slots refilled, ₹ saved" report | Medium (clinics don't ask, but it's what keeps them) | D | P0 | Measured against the clinic's own 4 weeks before switch-on. |
| Reminder timing rules (e.g. 24h and 2h before) | High | TS | P0 | Keep it to 2 rules per appointment type. |
| Reschedule link to open slots | Medium | TS / D | P1 | Needs a live view of free slots. Harder on paper diaries. |
| Deposit or prepayment link for high-value procedures | Medium. Prepayment is the strongest no-show deterrent. | D / L | P1 | Link goes to the clinic's own Razorpay or UPI. Never hold money. |
| Per-patient no-show history ("missed 2 of last 3") | Medium | D | P1 | Helps reception double-book wisely. Keep it inside the clinic's account. |
| SMS fallback for patients not on WhatsApp | Medium | TS | P1 | Only if pilots show ≥20% of patients aren't reachable on WhatsApp. DLT registration required. |
| Voice-call reminders | Low in India (reception already calls) | X | — | See 03. |
B. Diary and systems
| Feature | Category | Priority | Notes |
|---|
| Google Calendar sync | TS | P0 | The "layered on existing calendars" promise. |
| Simple web diary for paper-based clinics | TS | P0 | Minimal: dentist, chair, time, patient, phone. Not an EMR. |
| One EMR integration (whichever ≥5 paying clinics use) | D | P1 | Only with a documented API. Unverified which Indian EMRs have one. |
| Outlook, iCloud, CalDAV | TS | P2 | Rare in Indian dental clinics (assumption). |
| Full EMR, billing, charting | X / L | — | That's Practo Ray's, Eka's and HealthPlix's business. |
C. Revenue add-ons (paid, and priced to pass through message cost)
| Feature | Category | Priority | Notes |
|---|
| Recall reminders (6-month cleaning, follow-up after treatment) | D | P1 | Likely a marketing message (~₹1.09 at AiSensy's list rate). Price per message, not "unlimited". Confirm Meta's categorisation first. |
| Post-visit Google review request | TS / X | P2 | Every tool does it. Marketing category. |
| Treatment-plan follow-up ("you haven't booked your second sitting") | D | P2 | Real revenue for dental, but it needs treatment data you won't have without an EMR link. |
| Broadcast offers ("whitening at 20% off") | L | — | Marketing messages, number-quality risk, and spam complaints. |
| Birthday and festival greetings | X | — | Clinics ask for it, nobody pays for it, and it's marketing-priced. |
D. Languages and patients
| Feature | Category | Priority | Notes |
|---|
| Templates in English, Hindi and one regional language | TS | P0 | Pre-approved per clinic at onboarding. |
| Patient opt-in record and opt-out handling | TS / L | P0 | Needed for WhatsApp policy and DPDP. |
| Family accounts (one phone, several patients) | TS | P1 | Common in India. Easy to get wrong. |
E. Automation and AI
| Feature | Category | Priority | Notes |
|---|
| AI receptionist that answers patient questions on WhatsApp | X / L | — | Clinical questions are a liability. Meta policy on AI chatbots is a risk (unverified). Cliniko add-ons (MIEA, Vascue) already sell it. |
| Smart overbooking suggestions from no-show history | D | P2 | Only after 6+ months of per-clinic data. |
| No-show prediction score | L | — | Small data per clinic. A wrong score gets a patient double-booked. |
F. Compliance and trust
| Feature | Category | Priority | Notes |
|---|
| Data-processing agreement per clinic | TS | P0 | The clinic is the data owner; you process on its behalf (DPDP Act). |
| No clinical details in any message | TS | P0 | "Appointment with Dr X at 5 pm", never the procedure. |
| 90-day deletion after appointment | TS | P0 | Keeps breach exposure small. |
| HIPAA BAA, audit logs, US hosting | L for this wedge | — | Only relevant in the US, which is out of scope. |
4.1 Net effect
Of about 30 features clinics ask for, 5 belong in v1 (two-way confirmations, unconfirmed list, slot refill, baseline report, calendar or simple diary) plus templates and privacy rails. About 6 are differentiators at all, and every one of them is something an EMR could add in a quarter. That's the core weakness of this idea.