Everyone Agrees It Is Booking Only. Then Somebody Describes a Symptom.
Every clinic deploying an assistant agrees the scope is booking and admin. Then a patient types out what is happening to them and asks whether they should be worried — and a system built to answer will answer, because that is what it does. A policy document cannot stop that at eleven at night. A refusal built into the system can, and that is the entire engineering problem here.
No credit card required · 30-minute call · No obligation to sign up
Six requests and where the line falls
The line is not about difficulty. It is about whether answering requires any clinical judgement at all — and the system has to be unable to cross it rather than instructed not to.
- Book me an appointmentYes · this is the whole point
- What do I bring, where do I park?Yes · genuinely useful, always asked
- How long does the procedure take?Yes · if a clinician wrote it
- Is this symptom serious?No · hard stop, every time
- Should I stop my medication?No · hard stop, and escalate
- I think this is an emergencyNo · stop, and say where to go
The last row is the one that has to be right before anything goes live. Somebody in genuine distress should reach a clear instruction about where to go within one exchange — not a booking flow, not a triage question, and never a reassurance. That path gets written and tested first, before a single ordinary booking is handled.
Instructions are not a control. A refusal in the system is.
Telling a language model to stay within booking and admin is an instruction, and instructions are followed most of the time. Most of the time is not a standard for this. What works is narrowing what the system is capable of doing at all: it draws only on a small set of clinic-approved answers written by your own people, and anything outside that set produces a handover rather than a generated reply. It cannot compose a clinical answer because it has nothing to compose one from.
The distress path gets built and tested before anything else. Somebody who indicates urgency reaches a clear statement of where to go, in one step, with no booking flow in between and no attempt to assess anything. That is not a fallback for later; it is the first thing built, because it is the case where being second-rate is unacceptable and the case a demo never includes.
On what it may know: appointment slots, opening hours, what to bring, where to park, how long something takes, what happens on the day, how to prepare. All of it written or approved by clinical staff, all of it revisable by them, none of it improvised. That list is genuinely useful, it is asked constantly, and it is where the value of this actually sits.
And data minimally. A booking system needs a name, a contact and a slot. It does not need a description of what is wrong, and a system that invites one has started collecting clinical information through a channel not built for it. We do not build systems that hold medical records, and we say so before being asked.
- ✓Narrow the capability, not the instructions — It cannot compose a clinical answer if it has nothing to compose from.
- ✓Build the distress path first — One step to a clear instruction. Tested before anything else.
- ✓Clinic-approved answers only — Written by your people, revisable by them, never improvised.
- ✓Collect the minimum — A name, a contact, a slot. Not a description of what is wrong.
- ✓No medical records, ever — Said before anybody asks.
Instructions are followed most of the time. Most of the time is not a standard for this.
What we build for a clinic
Six things, and the first two exist before a booking is ever taken.
The Distress Path, Built First
One exchange to a clear instruction about where to go. No booking flow, no assessment, no reassurance. Written and tested before an ordinary booking is handled.
A Hard Stop, Not an Instruction
It draws only on clinic-approved answers and hands over for anything else. The boundary is what it is able to do rather than what it has been told to do.
Booking and Rescheduling
Real slots, real availability, cancellations handled, and confirmation sent. The unglamorous core, and the part that returns reception’s day to them.
Missed Calls Captured
A call nobody could answer becomes a callback request with a name and a number, rather than a lost patient. Reliably the highest-value piece for a busy practice.
Bilingual Where It Helps
Urdu and English to the same standard where your patients need it, with a person when it is unsure. Not machine translation applied to clinical-adjacent wording.
A Record of Every Exchange
What was asked and what was said, retrievable by your practice. Both for your own governance and because somebody will eventually ask what the system told a patient.
What clients say
Real clients, quoted in their own words — published with their permission.
“It was a pleasure working with Ghalib and his team.”
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied in Healthcare
The method doesn’t change by market. What it’s pointed at does.
Audit The Hours
Where time actually goes, task by task, scored on volume, repetition and the cost of getting it wrong. Ends in a ranked blueprint with estimated hours saved — yours to keep either way.
Design The Guardrails
Before any building: what the agent may touch, where a human must approve, what happens when it is unsure, and which data is never allowed near a third-party model.
Build & Evaluate
One workflow at a time, in your accounts, scored against real examples from your business before it touches live work. Shipped early so it meets reality while it is still cheap to change.
Run & Improve
Monitored for cost, failures and quality drift. Models change, your business changes, and an automation nobody tends becomes a liability rather than an asset.
Honest, No-Nonsense Commitment
If the audit concludes that a task is not worth automating, we will tell you and refund the difference rather than build it anyway. And if a workflow we built does not hit the outcome we agreed in the blueprint, we keep working on it at no extra cost until it does or we take it out.
AI Automation pricing for Healthcare, in GBP
Quoted in pounds, and evaluation is included rather than optional here — a system talking to patients unsupervised is the last place to skip testing. None of this is clinical or regulatory advice. We build to the boundary your clinical governance sets; what that boundary is remains yours to decide.
Booking
Appointments and the basics.
- Distress path built and tested first
- Hard stop outside clinic-approved answers
- Booking, rescheduling and confirmations
Practice
The usual one. Plus calls and hours.
- Everything in Booking
- Missed-call capture and callback requests
- Out-of-hours cover with the same boundary
- Optional: bundle in SEO or Website Development
Group
Several sites or practitioners.
- Per-site availability and routing
- Bilingual handling where patients need it
- Evaluated against a clinical test set before launch
- Optional: combine all 4 services for full-funnel growth
Every plan is scoped around your market — start with a free first look and we’ll recommend what fits, priced in GBP.
What you’re actually committing to
Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.
- The audit is credited, not sunkPay for the audit, and the full amount comes off the build if you proceed. If you don’t, the blueprint is still yours to hand to anyone else.
- A fixed build price after the auditQuoted once we know what we are building. If it takes longer than we estimated, that is our risk — the price only moves if you change the scope.
- You own everythingAccounts, API keys, workflows, prompts, evaluation sets, logs and documentation — all in your name from day one, and still yours if we never work together again.
- Running costs are yours and visibleAPI usage is billed by the provider directly to you. We never resell tokens or mark up usage, and you see the real number.
- The retainer is month to month30 days’ notice, no exit fee. Stop it and your automations keep running — you are simply maintaining them yourself.
- Human approval is the defaultAnything customer-facing or irreversible needs a person until the evaluation data justifies otherwise, and that decision is yours to make, not ours.
These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.
Healthcare AI Automation questions, answered
Related AI Automation pages
Same service, different angle — by market, by service and by industry.
Want the boundary in the system?
Free 30-minute call · No obligation · Response within 24 hours
Get in touch with Ghalib Ashrafi HQ
Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.