An AI receptionist is a product category, not a reliable description of shipped behaviour. Before you buy, ask the vendor to demonstrate the exact call, booking, calendar, reminder, escalation, and failure workflows your clinic needs. This post gives that acceptance pack, the price questions, and the TRAI and DPDP timing to check.
Key takeaways
- Treat each claimed front-desk job as a vendor-specific workflow to test. A product label alone does not prove calling, booking, reminder, triage, or patient-facing behaviour.
- Check TRAI’s TCCCPR 2018 requirements for the actual messaging workflow. DPDP’s core processing provisions are scheduled to commence eighteen months after the 13 November 2025 Gazette notification; use consent, notice, retention, and opt-out controls as preparation and check other applicable obligations.
- Require a human escalation path for clinical questions under the Telemedicine Practice Guidelines 2020.
- Patient Square lists AI Receptionist as an Autopilot module. Autopilot is ₹4,999 per clinician month-to-month or ₹3,999 per clinician monthly-equivalent on annual billing, ex-GST; add 18% GST.
front-desk workflows to test: calls, booking, missed calls, reminders, and escalation
TRAI TCCCPR, the regulation your reminders and calls run under (notified 19 July 2018)
DPDP core processing provisions after the 13 November 2025 Gazette notification
Sources: TRAI TCCCPR 2018; MeitY, DPDP Act 2023; MeitY Gazette G.S.R. 843(E), 13 November 2025.
What does an AI receptionist actually do at the front desk?
Picture a two-doctor OPD in Indore at 11am. Twelve people in the waiting area, the desk phone ringing, and a WhatsApp inbox with nine unread “doctor available today?” messages. The receptionist can do one thing at a time. Everything else waits or drops.
Use the scene to test five vendor claims, not to assume any of them: answering routine calls, booking and rescheduling against the live calendar, missed-call recovery, reminder delivery, and FAQ routing with human escalation. For each, run a consented test with a staff takeover and a deliberately failed handoff. Record the calendar result, duplicate-booking prevention, message template, opt-out, audit trail, and recovery owner. If your bottleneck is the queue inside the room rather than the phone, our OPD queue management guide is the better starting point.
Can it replace your receptionist? No, and be suspicious of anyone who says yes
Do not make a staffing decision from a demo. Test the vendor’s claimed volume workflows with the current team, then require human escalation for clinical, distressed, and exception cases. The acceptance record should show what happens when the calendar is unavailable, the caller is unmatched, a message fails, or a clinical question arrives.
What compliance questions should you ask about clinic messages?
Before enabling a vendor’s messaging or calling workflow, ask which channel and registered entity will send it, and which TCCCPR classification, DLT setup, headers, templates, customer preferences, opt-out, escalation, retention, and failure process apply to the proposed use.
The Telecom Commercial Communications Customer Preference Regulations, 2018 is the framework to check for the actual SMS or calling workflow (TRAI, TCCCPR 2018). Obtain the vendor’s written answers for the channel and use case you propose, then have the clinic’s appropriate adviser and messaging provider confirm them.
Do not assume a booked reminder has a particular classification, or that a vendor provides a calling, booking, reminder, or WhatsApp workflow. Require a demonstration and written compliance answer for every claimed flow, including its human handoff and failure path. If WhatsApp is your main channel, our WhatsApp for clinics guide can help frame the questions to take to the vendor and provider.
Who’s responsible for the patient’s data? You are
The Digital Personal Data Protection Act, 2023 defines data-fiduciary, notice, consent, and processing obligations, but the 13 November 2025 commencement notification schedules sections 3 to 17, including those core processing provisions, eighteen months after publication. On this page’s update date, do not present them as current enforcement. Use the controls below as prudent preparation and check other applicable law, contracts, and professional obligations.
For any AI-receptionist vendor, obtain written answers about patient phone numbers, call logs, recordings, retention, location, access, and opt-out before processing. Those are useful procurement and preparation questions regardless of the staged DPDP date.
Three questions to put to any AI-receptionist vendor before you sign:
| Question | What a good answer sounds like | Red flag |
|---|---|---|
| Where does patient data (numbers, call logs, recordings) sit? | A named region and a straight answer, in writing | ”On the cloud, it’s secure” with no specifics |
| Are calls recorded, and can we turn that off? | Yes/no, with a toggle you control | Vague reassurance, no control |
| How does a patient opt out of messages? | A documented opt-out you can point patients to | ”That never comes up” |
“The vendor handles compliance” is not a complete procurement answer. Record the vendor’s commitments and have the clinic’s appropriate adviser assess its obligations.
Where’s the line on medical advice? At the doctor, always
Require the vendor to demonstrate a booking/routing workflow that escalates clinical questions rather than answering them. That is a procurement requirement, not a claimed Patient Square behaviour.
Under India’s Telemedicine Practice Guidelines 2020, giving medical advice is the professional responsibility of a Registered Medical Practitioner, who has to identify themselves by name, qualification, and registration number and verify the patient or caregiver before advising (MoHFW/Board of Governors, Telemedicine Practice Guidelines 2020). A front-desk assistant, human or software, is none of those things. So the design rule is a hard handoff: the instant a caller asks “should I take this medicine” or “my child has a fever, what do I do,” the assistant’s only correct move is to route to the doctor or the clinic’s clinical staff, not to answer.
For any claimed booking, reminder, timing, direction, fee, or routing flow, require a vendor demonstration and an immediate human escalation path for clinical questions. Ask what happens when a caller describes a symptom, when the workflow fails, and when staff must take over; record the answer in the acceptance test.
Does the front desk talk to the rest of your clinic?
A standalone answering bot is a start. But the front desk isn’t an island, and its real value shows up when the calls and messages connect to the calendar and the visit itself.
Ask the vendor to run one connected test: create a booking, inspect calendar availability, change it, send a permitted reminder, hand off a clinical question, record the visit, trigger any claimed follow-up, and then recover from a failed message or duplicate attempt. Confirm which steps are automated, which require staff, and whether the audit trail reaches the systems you use. If you’re evaluating just the booking layer right now, our appointment scheduling software buyer’s guide breaks down what online booking has to get right. And for the after-visit side, patient follow-up automation covers which nudges need a clinician’s eyes.
Where does Patient Square fit, and what won’t we claim?
Patient Square is an AI clinical platform. Practice Copilot brings the whole practice under one AI copilot — an ambient AI Medical Scribe that hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft minutes after the visit, plus a bundled AI EHR, scheduling, and messaging as you move up the plan. Hospitals get Hospital Copilot.
AI Receptionist is a named Practice Copilot module at Autopilot. The current product material does not describe its calling, booking, reminder, triage, or patient-facing behaviour, so this page does not assign those behaviours to Patient Square. Use the acceptance pack above to make a vendor demonstrate the operational details that matter to your clinic.
Practice Copilot can use Patient Square EHR from the Copilot tier as its system of record or work alongside an existing EHR. The practice pricing is per clinician: Assist is ₹1,999 month-to-month or ₹1,599 monthly-equivalent on annual billing; Copilot is ₹2,999 month-to-month or ₹2,399 monthly-equivalent on annual billing; Autopilot is ₹4,999 month-to-month or ₹3,999 monthly-equivalent on annual billing. Prices are ex-GST and GST is added at the prevailing rate, currently 18%. Start your 7-day free trial to test the documented scribe workflow and inspect the Autopilot module in the product context.