Management cannot see what arrives
No number for conversations received, none for those left unanswered, none for reply time.
The operating system for medical complexes
Instagram · WhatsApp · Facebook · TikTok · Google Maps
One inbox that turns into bookings — and tells you which ad produced them.
Built for Saudi medical complexes. Arabic-first, not translated.
Instagram blocks replies after 24 hours. A conversation you miss does not come back.
Meta's rule — not a setting in our system
The problem
Patients reach you through Instagram, WhatsApp, Facebook, TikTok and Google Maps — and all of it lands on one receptionist's phone.
No number for conversations received, none for those left unanswered, none for reply time.
Budget goes out on campaigns, and the result is judged by impression rather than by riyal.
Conversations, promises and follow-up dates walk out of the door with them.
The solution
With a counter showing when the reply window closes.
Routed automatically by shift, daily cap and channel.
And the campaign it came from stays attached to it.
To the channel, the campaign, the branch, the employee and the service.
Inside the system
What arrived, then the booking, then the number that says what worked.
Reply window: Every channel in one list, with a counter for what is left of the reply window. Window closed — reply from the app
Noura A.
Facial cleanse
Khalid M.
Implant
Abu Mohammed
Consultation
From conversation to booking to attendance — with the source attached to the card.
| Source | Bookings | Attributed income |
|---|---|---|
| 64 | 86,400 | |
| Dental campaign | 31 | 52,000 |
| Google Maps | 22 | 28,900 |
| Unattributed | 17 | 19,300 |
Income attributed to each channel — and what is unattributed stays visible, never distributed. "Unattributed" is always its own row — distributing it across campaigns makes every one of them look better than it is.
An illustrative representation of the interface — the figures shown are for illustration only and belong to no complex.
Product
Six groups, exactly as they appear in the system.
Inbox · Posts and comments · Google reviews · Ad lead forms · Google Sheets sync · Bookings · Customers · Tasks and reminders · Customer campaigns
Six axes over one date range: services · clinics · doctors · staff · customer statuses · sources.
Story Center · Ads · Landing pages with live links.
Connected accounts · WhatsApp · Message templates · Tracking and pixels.
Clinics within the complex · Doctors · Services · Offers · Packages · Before/after.
Complex profile · Team and its four roles · Team activity log · Rewards · Subscription · Trash.
What sets it apart
Most Instagram messages arrive with no phone number — just an @username. That is the normal case here, and the exceptional one everywhere else.
A counter on the conversation, an alert before it closes, and a report of the customers lost.
From ad spend to realized riyals — by attribution recorded on the row itself, not by guesswork.
Central administration · a scope per region and city · visit any branch as yourself, and everything you do is logged under your name.
How it works
There is no installation. The first step is connecting one channel, and it takes minutes.
Through the platform's own authorization. We never take your password, and you can disconnect it yourself at any time without us.
Median and 90th percentile — not a single average that hides the worst cases.
Over the last 30 days: how many conversations closed before anyone replied.
Whether we continue together or not. The number is yours.
What moves with you: customers, historical bookings, services and prices. What does not: your old conversation history — there is no source for it; conversations begin the day the channels are connected.
Value
We do not promise a percentage improvement. We promise you will know your number within 30 days.
| Today | After |
|---|---|
| How many conversations went unanswered yesterday? | A number on the screen |
| How many patients did we lose to a closed window? | The "missed windows" report |
| How long does our first reply take? | Median and 90th percentile |
| Where did this booking come from? | The channel and the campaign |
| Which service, doctor, clinic or employee produces? | Six reporting axes |
| What did last month's campaign produce in riyals? | Return on ad spend |
| Who did what, and when? | A full audit log |
Your patients' data
One complex cannot see another's data — guaranteed by automated tests that fail the build.
Patient photos and attachments sit on storage with no public URL at all, readable only through an authenticated request.
And the upload key cannot read them — so whoever holds the server cannot open a single one.
Every change recorded under its author, and an export is logged before the first byte leaves.
We do not hold a formal security certification today, and we will not claim one. What we have is exactly these controls, and we will put them in the contract.
Under the hood
The technical choices a user actually feels — not a list of tools.
The interface was built right-to-left, and the Arabic fonts are self-hosted, so nothing waits on an external server at first paint.
The complex panel, the group panel and the operator panel all read from one documented API, so two screens cannot disagree about a number.
Hiding a button is not a control. Every route declares the ability it requires, and a test that reads the route table refuses any new route without one.
Authorization through the platforms themselves, with no passwords, and revocable from your own account without going through us.
Plainly
We say it here, not after you sign.
FAQ
Most systems start from a contact that has a phone number. We start from the message: an Instagram conversation with no number, just an @username, is a normal case here. And if your system already answers "how many conversations went unanswered yesterday?", you do not need us.
WhatsApp works for replying. But it will not tell you how many conversations were missed, how long your reply took, or which ad produced the booking — and nothing of it remains when the employee leaves. We do not replace the reply; we put it somewhere it can be measured.
What moves with you: customers, historical bookings, services and prices. What does not: your old conversation history — there is no source for it, and conversations begin the day of connection. The important step is not the import but connecting the channels, which takes minutes. And we can start with a single branch before expanding.
Controls instead of adjectives: complete isolation between complexes guaranteed by automated tests · patient files on a private disk with no public URL · hourly encrypted backups whose upload key cannot read them · and an audit entry written before the first byte of any export leaves. And plainly: we do not hold a formal security certification today, and we will not pretend otherwise.
Outbound WhatsApp currently goes through a provider that automates WhatsApp Web. It works and has been tested on a real number, and there is a risk of a ban if it is misused — which is why the system enforces spacing between messages and a daily cap. Those are protective controls, not performance settings. The official path (WhatsApp Business API) is built as a ready alternative.
Inbound is ready: Instagram, Facebook, WhatsApp, Google Maps, Meta ad forms and Google Sheets, plus a documented API. There is no ready-made integration with any specific medical system — name the system and the data you want to move, and we will come back with a specific answer.
Connection is through the platform's official authorization — we never take your password, and you can revoke it at any time from your own account settings without going through us. The more important question: today your messages sit on an employee's personal phone. Which is riskier?
We are early, and we will not invent a number. That means two things: direct attention from us, and your feedback reaching the product quickly. We are not asking for blind trust — we are asking for 30 days on one branch with your own figures, and if it tells you nothing you did not know, we stop.
You export your data yourself at any time from inside the system — customers and bookings. And we can add an exit clause to the contract committing to a full copy on request.
Yes: a central administration above the branches, with a scope per region and city, and the ability to visit any branch as yourself — everything you do during that visit is logged under your name, not the branch staff's.
We connect one channel, measure your reply time, and extract your missed windows over the last 30 days. You keep the report whether we continue or not.
One question or a full session — both reach the same person.