Solutions · Healthcare
A front desk that answers on the first ring.
The Healthcare Receptionist template arrives already fluent in a clinic's day: booking, insurance, after-care — and knowing when to hand the call to a human.

A scene from your day
Quarter to eight in a Riyadh clinic: line one wants a dental appointment this week, line two needs to move a follow-up, and on line three a mother is asking about after-care for her son's extraction. Before the first employee hangs up a coat, all three calls have been answered.
Basher greeted each caller, disclosed it is an AI and that the call is recorded, verified the patient file, offered two open slots and read the details back before confirming, and — with the clinic's messaging connected — sent the confirmation over WhatsApp. The mother's question was answered from the clinic's own documents — and anything clinical was handed to the staff.
Inside the platform
The path is drawn before you start
Change any step yourself — drag and drop, no developer, no line of code. Appointment booking arrives already drawn: the agent checks the slot, confirms it, or offers another time. The confirmed booking itself needs your clinic's calendar connected — we do that with you during onboarding.
Ready to configure
What comes pre-wired
The conversation arrives ready and you can reshape any step yourself. Actions that touch your systems — a confirmed booking, a ticket, a record update — go live once that system is connected during onboarding. Every line here exists in the product, not in a marketing deck.
It knows why they're calling from the first sentence
Book or reschedule, cancel, a general inquiry, an after-care question, an emergency, a complaint — six common reasons, and every call takes its own path from the first sentence.
in the code: CONDITION · ×6A complete booking chain, not half a service
Identity verified by phone or medical record number, insurance checked before booking, the best two or three slots offered, details read back before confirming — and, once your calendar and messaging are connected, a confirmation over WhatsApp or SMS.
in the code: verify → insure → book → confirmEmergencies are not discussed — they are transferred
An instant transfer is wired into the template: at any urgent symptom, Basher reassures the caller and hands the line to emergency staff — without attempting a diagnosis.
in the code: TRANSFER → emergency_lineAfter-care from your own documents
Post-procedure instructions are answered from the clinic's knowledge base, under an explicit rule in the prompt: never a diagnosis, never a medication change.
in the code: knowledge_base: enabledCancellation with a policy — and an alternative first
Before cancelling, Basher reads the appointment back, states the cancellation policy and offers to reschedule instead — and every change is followed by an updated notification.
in the code: cancel_booking → reschedule?
Patient safety before model intelligence
Never a diagnosis. The patient's file stays untouched. An emergency reaches a human instantly. And these are not promises — they are guardrail rules written into the product, each by its exact name:
- Emergencies caught and rerouted
check emergency detection - Insurance manipulation flagged
check insurance fraud patterns - Patient data protected under Saudi PDPL
check pdpl compliance - Medical safety enforced
check medical safety - Arabic manipulation attempts blocked
check arabic prompt injection
config/guardrails/healthcare
Platform pillars
What it stands on
Every template borrows its strength from the platform itself — meet each pillar up close.
Arabic voice engine
Saudi dialect and a response time fit for an anxious call
Flow builder
The booking and cancellation path step by step, edited without code
Knowledge base
Insurance and after-care answers from your clinic's documents
Telephony
Warm transfer to the emergency line, with recording consent gates