Appointment agent
Books, reschedules and cancels against your practice management system, respecting clinician availability, appointment types and duration rules. Confirms by SMS or WhatsApp.
Clinics & healthcare
Reception is the busiest, most interrupted role in any clinic. Most of what it handles is scheduling. Very little of it needs clinical judgement — but all of it needs to be handled carefully, because this is health data.
The day-to-day
Where the money goes
Booking, rescheduling and cancelling appointments is high-volume, rules-based work. Every minute reception spends on it is a minute not spent on the patient in the room.
A patient who cannot easily reschedule will simply not attend. Making cancellation frictionless sounds counterintuitive but reliably increases utilisation, because a cancelled slot can be refilled and a no-show cannot.
Patients often deal with admin in the evening. A clinic that cannot take a booking at 8pm loses it to one that can.
Details captured verbally and typed later are the origin of a large share of billing and record errors. Structured capture at the point of contact removes an entire class of rework.
What we would build
Books, reschedules and cancels against your practice management system, respecting clinician availability, appointment types and duration rules. Confirms by SMS or WhatsApp.
Automated reminders at the intervals that actually work for your patient mix, with one-tap confirm or reschedule, and automatic offer of the released slot.
Collects the administrative and history information you need before the appointment, in the patient's language, written straight into the record so nothing is re-keyed.
Answers strictly administrative questions — opening hours, location, parking, what to bring, insurance accepted, preparation instructions you have published — and escalates anything else immediately.
What we design around
These are the things that make a generic build fail here. We treat them as hard requirements from day one, not as issues discovered in testing.
The agent does not triage, diagnose, interpret symptoms or advise on medication. Any clinical question is an immediate, unconditional escalation to a person. This boundary is enforced in the guardrails, not left to the model's judgement.
Before any build we agree what data the agent may see, where it is processed, how long it is retained and who can access it — aligned to UAE health data regulation and your own obligations. This is scoped in the governance engagement, not bolted on afterwards.
Explicit detection for language indicating urgency, with an immediate instruction to call emergency services and a hard handover. Tested deliberately and repeatedly.
Patients are told they are speaking to an automated system and how their information will be used, at the start of the call.
A realistic first quarter
Indicative, and it changes with your systems — but this is the shape, and the ordering is deliberate: lowest risk first, so the evidence arrives before the exposure does.
Governance first: data map, retention, access, escalation policy, and the explicit list of what the agent may never do.
Build reminders and confirmations. Lowest clinical risk, fastest measurable effect on utilisation.
Add booking and rescheduling against the practice management system, tested extensively including emergency-language cases.
Add structured pre-visit intake once the booking flow has run clean on live traffic.
How we would engage
Control the risk
Your team is already pasting client data into public AI tools. We put the policy, access controls and vendor review in place that let you say yes to AI safely — sized for a mid-sized business, not an enterprise compliance department.
Read moreBuild it
Voice and chat agents that answer every call, qualify the enquiry, take the booking and write it into the systems you already use — in English and Arabic, around the clock. Amira, running live for a Dubai client, is one of ours.
Read moreFAQ
It can be, and that is precisely why we start with governance rather than with a build. We agree data residency, processing, retention and access before writing an agent, and we will decline a workflow that cannot be done compliantly.
The agent does not engage with them. It escalates to a person, and where the language suggests urgency it instructs the caller to contact emergency services immediately. We test this path harder than any other.
Usually. We confirm what your system exposes in the first fortnight. Where an integration is not available we design around it rather than promise something we cannot deliver.
Some will not, and that is fine — the agent is not the only route in. A patient who asks for a person gets one. Removing the routine calls is what frees reception to give those patients more time, not less.
Bring us a month of call logs or enquiry data and we will tell you, specifically, where it is leaking and what it is worth fixing.
Altus AI concierge
Answers about our work — and books your call
Hello — I'm the Altus concierge. Ask me anything about AI adoption, governance, or the agents we build. If it's a fit, I'll set up a call with the team.
AI-generated. We store what you send so we can follow up. Privacy