Nasaq pairs a rock-solid, conflict-free booking engine with an AI layer that talks to your patients on WhatsApp - booking, rescheduling and reminding, around the clock. The model understands and speaks. It never makes the clinical call.
Runs the operations layer for modern clinics
Every capability below rests on one rule: a deterministic core decides, and the AI only understands and talks. That is what makes it safe to put in front of real patients.
Guesses, hallucinates, double-books
Understands, verifies, never overbooks
Patients book, reschedule and cancel in plain language over WhatsApp - Arabic or English. Nasaq reads intent, confirms details, and writes the appointment.
Overlapping bookings on the same doctor or room aren't caught after the fact - they're made impossible by the database itself. No phantom slots, ever.
Automated reminders, follow-up nudges and no-show recovery run on schedule, in the patient's language, so your calendar stays full without manual chasing.
When a slot frees up, Nasaq offers it to the right waiting patient automatically - recovering revenue that a cancellation would otherwise cost you.
Anything sensitive, unclear, or clinical is escalated to your staff by explicit rule - never guessed at. The team stays in control of every judgment call.
Your front desk sees every conversation, appointment and task in a single calm view - no app-switching, no copy-paste between tools.
Nasaq is deliberately two layers. A thin AI interface that understands language, and a deterministic engine that owns every decision and every write.
A patient writes in their own words. Nasaq's AI layer reads the intent - book, move, cancel, ask - in Arabic or English, and asks for anything it's missing.
Before anything is promised, the deterministic core re-validates live availability, the clinic's rules, and permissions. The AI can suggest, but it cannot invent a slot.
The appointment is written through a single guarded interface with tenant isolation and a conflict constraint. The patient gets a confirmation; your calendar updates.
From there, reminders, follow-ups, no-show recovery and the waitlist run automatically - every step logged in an append-only audit trail.
Nasaq is split on purpose. A thin AI interface that understands language sits on top of a deterministic engine that owns every decision and every write — and the two can only ever talk through a guarded gate.
Reads what the patient means in Arabic or English, asks for anything missing, and phrases the reply. It suggests — it never writes.
Re-checks live availability and clinic rules, then writes the appointment through one guarded path with tenant isolation and a conflict constraint.
It can understand a request, propose real open slots, and draft the confirmation.
It can't invent a slot, bypass a rule, or make a single clinical call.
In healthcare, an unpredictable AI is a liability. Nasaq's guarantees are structural - enforced by the database and the architecture, not by hoping the model behaves.
No diagnosis, treatment or drug advice on any surface. The model handles scheduling and language only; anything clinical escalates to a human by rule.
No patient information reaches an external model before explicit, recorded consent. The consent gate is enforced deterministically, not left to the conversation.
Every clinic's data is walled off at the database level. A cross-clinic query simply cannot be written - isolation is enforced by the database, not a forgotten filter.
Every state change writes an append-only record of who did what, when, and what changed. The trail is never edited or deleted.
No - and it can't. Nasaq draws a hard line: the AI only understands language and schedules appointments. Anything clinical - diagnosis, treatment, medication - is escalated to your staff by an explicit rule, never answered by the model.
Overlapping appointments on the same doctor or resource are made impossible by a constraint in the database, not by an app-level check that could be bypassed. The AI physically cannot promise a slot that isn't really free.
Each clinic's data is isolated at the database level, so a cross-clinic query can't happen. No patient information reaches an external model before recorded consent, and every change is written to an append-only audit trail. The design is aligned with PDPL.
Yes - Arabic-first, including dialect. Patients can write naturally in Arabic or English, and Nasaq replies in the same language. The dashboard is fully bilingual and right-to-left aware.
WhatsApp for patients, and a clean web dashboard for your team. No app for patients to install - they just message the clinic like they already do.
Days, not months. We connect your calendar, services and working hours, tune the reminders, and your clinic has a 24/7 front desk. Your team keeps working the way it already does.
See Nasaq handle a real booking conversation, end to end, in your own clinic's setup. No card, no commitment.
Set up in days, not months. Arabic and English from day one.