This post is for hospital administrators, patient-access heads and digital teams in India and the Gulf who are considering an AI voice agent to answer calls when the front desk is closed. It answers a narrow question: of everything a caller might say at 2 a.m., what may the agent do alone, and what must it pass to a person or refuse?
The commercial case for after-hours answering is easy to make, because enquiries arrive at night and a voicemail loses many of them. The safety case is harder. A hospital line receives calls from frightened people, and some of them describe emergencies. An agent that books a routine appointment for someone describing chest pain has done something the hospital cannot defend.
The framework below is a design pattern, not clinical guidance. Every escalation rule, symptom list and script must be defined and signed off by the hospital's clinical leadership and legal counsel, and tested before launch. Marketing should not author triage content.
The four intent classes
Every call that reaches an after-hours agent should be sorted into one of four classes. The classes are about what the agent does, not about the topic.
| Class | What the agent does | Examples |
|---|---|---|
| Book | Completes a transaction within approved limits | New consultation request, reschedule, health-check package enquiry converted to a slot |
| Inform | Gives approved factual information | Visiting hours, location, parking, departments, which documents to bring, doctor timings as published |
| Escalate | Transfers to a human or an emergency path | Urgent symptoms, distress, a request for a person, anything the agent cannot classify |
| Refuse | Declines politely and redirects | Diagnosis, medication advice, test interpretation, requests for another person's records |
The most important design decision is the default. When the agent is unsure which class applies, the default must be escalate, not book. The cost of a needless transfer is a few minutes of a nurse's time. The cost of a missed emergency is not comparable.
Emergency detection comes first, not last
The emergency check must run before any booking logic, on every turn of the call, not just the first. Callers often open with a routine request and mention a worrying symptom in the third sentence.
Build it as a layer separate from the conversational model:
- Keyword and phrase rules in each language the line serves, defined by clinicians, covering the red-flag conditions your hospital has chosen. Public health bodies describe the typical presentations. For example, the NHS describes the signs of a stroke with the FAST acronym and tells people to call emergency services immediately, and its heart attack guidance lists chest pain, breathlessness and other symptoms for the same urgent response. Use such public sources as a prompt for your clinical team's own list, not as the list itself, and not as a substitute for local protocols.
- A model-based check as a second layer, tuned to err towards escalation.
- A rule that overrides everything else: if either layer fires, the agent stops the booking flow and follows the emergency script.
The emergency script should be short, calm and unambiguous. It tells the caller to call the emergency number, offers to connect to the hospital's emergency department or ambulance line if your protocol allows, and stays on the line where it can. It does not ask the caller to complete a form.
Routing norms differ by city and country
This is where you cannot copy a generic design. Emergency numbers, ambulance services and the way hospitals receive emergency calls vary by country, emirate, state and even by city. In India there is a unified emergency number, 112, but which ambulance service answers, and how a private hospital's own emergency line fits in, depends on your location. In the Gulf, emergency numbers and ambulance arrangements are set by each country and, in the UAE, can involve emirate-level authorities.
We have not verified a per-city routing table here, and you should not use one from this article. The practical step is to build your own: for each campus, record the emergency number the agent should give, the hospital's emergency desk extension, the ambulance arrangement, and who confirms the table is current. Review it on a schedule and after any change in services. Treat the table as a controlled document with a named owner.
What the agent may book after hours
Define the list of bookable services narrowly and keep it in a configuration the operations team can edit.
- Allowed to book: new outpatient consultations, follow-ups, scheduled diagnostics and health packages, within published slots.
- Allowed to take a request but not confirm: services with preconditions, such as procedures that need pre-assessment, or second opinions that need record review.
- Never booked by the agent: emergency visits, admissions, anything described as urgent by the caller, and requests that need a clinician's judgement about whether a consultation is appropriate.
Make the agent read back date, time, location and the department, and tell the caller that a human will confirm in the morning if your process requires it. Do not let it invent a slot. Availability must come from the hospital's scheduling system.
