Run the Whole Clinic From One Account
ZiyaraTech is built around how a clinic's day actually runs: the front desk books, the team delivers, patients get answered, and the owner sees the numbers — without the four disconnected systems that usually sit in between.
What usually gets in the way
These are the operational problems the platform was built to remove. Each one maps to a screen in the product, not to a promise.
Scheduling that fights back
Double bookings, appointments landing on closed days, and slots that do not match how long the treatment actually takes.
Patient information in too many places
Contact details in one system, clinical notes on paper, and referral documents sitting in a chat thread.
No clear view of the team
Working hours, leave, and who can be booked for what — all kept informally, and never quite current.
Patient messages on personal phones
Conversations only one person can see, with no record left behind when they are away.
Reporting that takes a day to assemble
Numbers gathered by hand at month-end, from sources that never fully agree with each other.
Payments reconciled from memory
Charges, refunds and invoices tracked in a spreadsheet that quietly drifts away from reality.
Performance you can only feel
No way to compare this month to the last, or one branch to another, using the same measure.
Work that exists only because the tools do not talk
Re-typing the same booking into a second system, and sending reminders one message at a time.
What ZiyaraTech handles
The daily operations the platform covers today. Each is backed by a working screen in the clinic workspace.
The booking itself
Branch, staff member, services and time — checked against holidays, time off, blocked periods, working hours and existing appointments before it is accepted.
The patient record
Contact and clinical details, tags, notes, addresses and files, with every appointment, conversation and payment attached to the same person.
The team
Profiles, assigned branches and services, weekly schedules, time off, commission rules and rating history.
Patient conversations
One inbox for incoming chats on your own WhatsApp Business number, with assignment, internal notes and full history.
The messages that go out
Reminders and follow-ups triggered by real events, in Arabic or English, across WhatsApp, email, push and in-app.
Money in
Charges, refunds, patient invoices and settlement periods, tracked against the appointment they belong to.
Your ZiyaraTech plan
Plan, renewal, usage meters and invoices — with add-ons and upgrade requests when you outgrow a limit.
The numbers
A live dashboard, generated daily and monthly reports, trends over time, and per-channel analytics.
Who does what
ZiyaraTech ships with the roles a clinic actually has. Each one is a set of permissions — and you can build your own if none of them fits.
Owner
Full access to the clinic workspace: settings, billing, staff, permissions, and every report the platform produces.
Manager
Day-to-day operational access across bookings, patients, staff and communications, and — together with the owner — the ability to manage clinic settings.
Receptionist
Signs in to a dedicated front-desk console covering bookings, patients, scheduling, services, conversations and campaigns.
Doctor
A bookable staff member with their own schedule, assigned services, ratings and commission rules — with dashboard access only if you grant it.
Custom roles
Build a role for a specific job and choose permissions one by one. Only permissions you already hold are offered, and a preview shows what the role opens before you save.
Being bookable and having a login are two separate decisions. Staff appear in the calendar as soon as they are added; dashboard access is switched on separately and sends an email invitation.
The patient's side
What a patient experiences, using only the flows that exist in the product today.
- 01
They ask
A patient opens the assistant on your public pages and asks a question — or messages your WhatsApp Business number directly.
- 02
They choose
The assistant walks through clinic, branch, service and doctor, then offers genuinely open times from your calendar.
- 03
They book
The appointment is created against your clinic's calendar, and the chosen time is re-checked at the moment of booking — a slot taken in the meantime is refused rather than double-booked.
- 04
They are reminded
Notification rules fire on the appointment's own events, so confirmations and reminders go out without anyone sending them by hand.
- 05
They are followed up
After the visit a feedback request can go out on the delay you configured, and the rating lands on both the appointment and the staff profile.
- 06
They can always reach a person
A patient can ask for a human at any point. The conversation moves into your team's inbox with its full history, and the reply comes from the same thread.
Inside the clinic, day to day
Where each part of the day happens in the workspace.
Appointments
Book from the front desk, filter by status or doctor, reschedule or cancel, and move a visit through its statuses with notes and a timeline.
Patients
Search by name, email or phone, then open a profile for clinical details, tags, notes, addresses, files and history.
Staff
Add people, assign branches and services, set weekly hours and time off, and control exactly what each of them can reach.
Communications
Answer chats from one inbox, run notification rules and templates, and send campaigns from your own WhatsApp number.
Billing
Track charges, refunds, patient invoices and settlements — and manage your own plan, usage and add-ons in the same place.
Analytics
Watch the live dashboard, generate daily and monthly reports, and compare trends across periods.
AI
Ask the Dashboard Assistant for numbers, manage the knowledge it answers from, review handovers, and automate follow-ups with workflows.
Why clinics choose ZiyaraTech
Each of these is a property of how the platform is built, not a claim about the market.
One place for the whole facility
Bookings, patients, staff, messages, money and reports refer to the same records — so they cannot disagree with each other.
Access decided by permissions
Every request is authorised on the server against the permissions the person actually holds, not by which screen they happened to open.
Separated by design
Each clinic is its own tenant. Your patients, conversations, files and reports are scoped to your account and unreachable from any other.
Rules the calendar enforces
Holidays, time off, blocked periods, working hours and double-booking are all checked before a booking is accepted — including bookings the assistant makes.
Automation you can read
Notification rules and workflows are visible objects you can inspect, test-run, pause and delete — not hidden behaviour you have to guess at.
AI bounded by your data and your permissions
The assistants answer from knowledge you supply, using tools scoped to the asker's permissions, and hand over to a person when a person is needed.
Arabic and English, both first-class
The whole workspace switches between Arabic (right-to-left) and English (left-to-right), while numbers, amounts, dates and references stay identical in both.
Open at the edges
Scoped API keys, signed webhooks, and a connection layer for the external systems your facility already runs.