Patient portals for clinics in Egypt
Booking that finishes on your site instead of dying in an inbox — with reminders that cut no-shows and a patient history that does not live in someone's personal chat.
A dermatology chain in Heliopolis showed us their WhatsApp Business inbox. Across two branches, over thirty days, there were 847 booking messages with no reply. Not refusals — no reply at all. Messages that arrived after 6pm, during the Friday rush, or buried under three hundred other chats by the time anyone scrolled back.
At a typical 1,200 EGP visit, that is roughly a million pounds of demand that knocked and got no answer. Not all of it would have converted — but you do not need all of it, and right now you cannot even see it.
What moves off the chat app
- Real booking — live slots per doctor and per branch, so two staff replying on one number can no longer double-book 5pm Thursday.
- Automated reminders — the single highest-return feature here — clinics running on memory see 20–30% no-shows, and reminders typically take that under 10%.
- After-hours capture — patients book when they are free, which is late at night and on weekends. A form does not sleep; a receptionist does.
- Patient history in a system — prescriptions, packages, notes and before/after photos attached to a record rather than scattered across a personal phone.
The receptionist is not the problem
She is one person, with two hands and one phone, doing intake and follow-up and check-out and answering the same question forty times a day. Hire a second and you will still lose the after-hours messages, the weekend messages, and the burst that arrives when a reel does well.
The bottleneck is not a person. It is that your booking lives inside a chat app that was never built to run a schedule — so your busiest hours are exactly the hours you are least able to answer. The moment marketing works, intake breaks.
Systems we have already shipped
- CMYH — from an Instagram bio link to a site with real checkout — booked out within a month.
- IGBS — a 17,000-record client portal in eight modules — four years live with zero outages.
- The long version — the full write-up, including how chat booking bleeds money.
How a project runs
- We start with the friction, not the feature list — where the current setup actually breaks, and what it costs when it does.
- A written scope: which modules go in phase one, what each one does, the timeline and what is explicitly out.
- We build in phases, so one department is live and useful before the next starts. You see working software early, not a demo at the end.
- Handover in your name: code, database, hosting and documentation. You can move all of it to another team without asking us.
Common questions
Our patients only use WhatsApp. Will they book on a site?
They book where it is faster. The portal does not replace WhatsApp — it gives the message a place to land, so 'what times do you have Thursday?' becomes a link instead of a conversation your receptionist has forty times a week.
Are we too small for this?
If one person can comfortably hold the whole schedule in a notebook, probably. The threshold is usually two doctors or two branches — the point where two people start replying on one number.
What about patient data?
It lives in a database you own, with role-based access, rather than in a personal phone that leaves when the employee does. That is the strongest argument for moving off chat, independent of revenue.
How long does it take?
Six to twelve weeks depending on scope. Booking and reminders first, since that is where the money is; records and history after.
Related systems
- Buyer portals — the same pattern for property — a customer login over records you already keep.
- What we build — the full range: sites, stores, systems and ongoing care.
- Bilingual and RTL — Arabic and English done properly, from the start.