Attendance with text reminders, up from 67.8%
In a Cochrane review, attendance rose from 67.8% to 78.6% when patients received a text message reminder, at a lower cost than phone calls. On WhatsApp, the reply is one tap.
Clinic management software for Saudi Arabia runs the whole clinic from one workspace: appointment booking, WhatsApp and SMS reminders in Arabic and English, the patient file, insurance pre-approvals and claims, invoicing and reporting across every branch. Capra connects to the EMR, to NPHIES, to Sehhaty and to the insurers your clinic works with, with integrations built for you during onboarding and human support in UAE hours, an hour ahead of Riyadh.
Will it connect to what we already run? Will patients actually reply? And will somebody answer when we call? A clinic in Riyadh, Jeddah or Dammam lives on WhatsApp, bills several insurers through one national platform and often grows into a second city, so the answers decide the purchase.
In a Cochrane review, attendance rose from 67.8% to 78.6% when patients received a text message reminder, at a lower cost than phone calls. On WhatsApp, the reply is one tap.
Your EMR, NPHIES for pre-approvals and claims, Sehhaty for the appointment information patients see, and the insurers and TPAs you bill all have to stay in step. Capra connects to each of them; the connections are scoped and built during onboarding, not left for you to work out.
WhatsApp enquiries answered hours later from a personal phone are enquiries that book elsewhere. One clinic number, a shared inbox and templates in Arabic and English turn replies into bookings.
Switch channels to see how a reminder, a reply and a confirmation look on each one. Patients get the template in their preferred language, those who are not on WhatsApp get the SMS automatically, and every version lands on the same patient file.
Plain text, delivered through Twilio. Patients answer with a word, and the answer updates the appointment.
WhatsApp Business messages with tap-to-answer buttons. The reply threads straight back into the same conversation.
Email from your own verified domain (DKIM), with an appointment letter attached when you want one.
A named onboarding lead from the scoping call to go-live, in hours that match the Saudi working day.
Your onboarding lead maps your branches, appointment types, languages and the systems you run: EMR, NPHIES, Sehhaty, insurers and TPAs.
Bulk import from your current system, national ID or Iqama and insurance details on every file, and WhatsApp Business on your clinic number with Arabic and English templates and SMS fallback.
Messaging, booking and reminders are live within a few days; each integration is built, tested with your data and switched on according to the onboarding plan you agreed.
WhatsApp, the patient file, insurance, branches and bookings that share one record and one login.
Reminders, confirmations, results-ready notices and booking links go out from your clinic number in the patient's preferred language. Reception answers from one shared inbox instead of a personal handset, and every message, in either language, is threaded to the patient file.
National ID or Iqama number and insurance details are captured at registration, consent and documents are kept in Arabic and English, and clinical notes, prescriptions and letters sit on the same file as every WhatsApp message and invoice. Every change is logged with who made it and when.
Capra connects to the EMR your clinicians chart in, to NPHIES for pre-approvals and claims, to Sehhaty for the appointment and visit information your clinic exchanges with it, and to your insurers and TPAs, so patient, visit and claim information moves without re-typing. Pre-approval and resubmission queues are configured for your insurance coordinator, with the status of each request visible on the booking.
One account runs every branch: per-branch diaries, roles and WhatsApp numbers, with reporting that shows utilisation, no-shows and revenue per branch and per doctor. A group with clinics in Riyadh, Jeddah and Dammam sees all three in one view, and each branch sees only its own patients and settings.
Patients book from your website or a WhatsApp link within the rules you set, self-pay appointments can take a deposit at booking, and reminder rules per appointment type send the right message at the right local time. A reply confirms or moves the appointment and the diary updates itself.
Capra is role-based and configurable, so a self-pay dermatology clinic in Jeddah, an insurance-led polyclinic in Riyadh and a dental branch in Dammam each get a workspace that matches their day.
Named here as systems Capra connects to. Each connection is scoped on your onboarding call and built and tested with your data before it goes live.
Defence in depth, from the first message to the last record. This is how we operate, not a badge.
Connections use current TLS with HSTS, and stored data is encrypted with keys managed by our cloud provider.
Permissions come from defined roles, privileged access needs multi-factor authentication, and rights are reviewed regularly.
Security-relevant events are recorded, retained and reviewed so unusual activity can be investigated quickly.
Critical data is backed up regularly and protected like production, with processes to restore service after a disruption.
UK clinics are hosted in the UK by default; deployment in other regions, including the UAE, is available on request with the same protections.
Capra connects to the record, calendar, accounting, messaging and claims systems you already run; integrations are built with you during onboarding.
Yes. NPHIES is one of the systems Capra connects to for Saudi clinics, alongside your insurers and TPAs, for pre-approvals, claims and the responses that come back. The connection is scoped on your onboarding call, built and tested with your data by Capra's own team, and switched on with every exchange logged in your audit trail.
Yes, as a system Capra connects to for the appointment and visit information your clinic exchanges with it. What moves, in which direction and how often is agreed on the scoping call and written into the integration, and your onboarding lead tests it with you before it goes live.
Deployment in the region is available on request. Clinics that need their data held in the Kingdom or the wider Gulf are deployed accordingly, with the same encryption, role-based access, backup and audit practices described on our security page. Tell your onboarding lead and it becomes part of the plan from day one.
Yes. Support is human, in UAE hours, which run an hour ahead of Riyadh and cover the Saudi working day, from a named team rather than a bot. Every new clinic has a named onboarding lead from the scoping call to go-live, and questions about configuration, imports or the day-to-day reach someone who knows your setup.
Yes. Reminder, confirmation, results-ready and booking templates are kept in both languages, each patient's preferred language is stored on their file so they receive the right one, and reception can reply in either language from the shared inbox.
Yes. A booking link on WhatsApp or your website lets patients choose a slot within the rules you set, reminders carry confirm and reschedule buttons, and a tap updates the diary. Patients who are not on WhatsApp get the same options by SMS.
Insurance details and the pre-approval status sit on the booking, pre-approval and resubmission queues are configured for your insurance coordinator, and Capra connects to NPHIES and your insurers so requests and responses are not re-typed. Your payers' own requirements stay exactly as they are; Capra keeps the status visible and the paperwork in one place.
Yes. Branches, rooms, doctors and WhatsApp numbers live in one account with per-branch diaries, permissions and reporting, so a group with clinics in Riyadh, Jeddah and Dammam sees every branch in one view while each branch sees only its own patients and settings. A doctor who works across two branches keeps one diary.
Only if you want it to. Most Saudi clinics keep the EMR their doctors chart in and add Capra for booking, WhatsApp, reminders, the patient file and reporting, connected so patients, appointments and documents stay in step. Clinics without a system they want to keep use Capra as the record as well.
Messaging, online booking and reminders are usually live within a few days of the scoping call. Integrations with your EMR, NPHIES, Sehhaty and your insurers follow the onboarding plan you agree with your named lead, each built and tested with your data before it goes live.
Yes. Because the product is role-based and configurable, a single-doctor clinic switches on booking, WhatsApp reminders and the patient file, while a polyclinic adds departments, insurance queues, multi-branch reporting and the integrations its payers need. Both get the same support and the same named onboarding lead.
Explore more
Book a personalized demo and we'll show you exactly how Capra fits your practice, with your channels, your calendars, and your workflows.
Just have a question? Send us a message