Everything Your Clinic Runs On, in One Workspace

Appointments, patients, staff, WhatsApp, payments, AI and reporting built as one system — so a booking, a reminder, an invoice and a report all refer to the same record.

One platform, one source of truth

ZiyaraTech is a single cloud workspace for the whole facility. Every location, every team member and every patient lives in one account, and access to any of it is decided by permissions rather than by which screen someone found.

Multi-branch
Every location with its own working hours, staff and timezone — under one account.
Role-based
Owner, manager, receptionist and doctor roles, plus custom roles you build yourself.
Arabic & English
Switch the whole workspace between Arabic (RTL) and English (LTR) at any time.
Cloud-based
Reach your clinic's data from any device, inside the facility or outside it.

Capabilities by area

Nine areas of the platform, each one mapped to a screen in the clinic workspace. For every capability: what it does, the problem it removes, and what changes for your clinic.

01

Area

Appointments & scheduling

Booking is the operational core of a clinic. ZiyaraTech treats every appointment as a record with a status, a history, and a set of rules that decide whether it can exist at all.

Conflict-aware booking

Choose a branch, a staff member and the services, then pick from live availability. The chosen time is re-checked the moment the booking is saved.

The problem
Two patients booked into the same slot, or a doctor booked on a day off.
What you get
Holidays, time off, blocked periods, working hours and existing appointments are all enforced before a booking is accepted — with the exact reason shown when one is refused.

Appointment lifecycle

Every appointment moves through a defined set of statuses: pending payment, confirmed, in progress, completed, cancelled, no-show and rescheduled.

The problem
No shared answer to what actually happened with a given visit.
What you get
A status your whole team reads the same way, plus per-appointment notes and a timeline of every change.

Service catalog and visit length

Group services into categories, set duration and price, and control what is bookable. The selected services decide how long the visit takes.

The problem
Slots that do not match the real length of the treatment.
What you get
Availability that reflects the actual visit, plus a per-staff buffer reserved after each appointment.

Calendar controls

Company-wide or branch holidays, blocked periods for leave and maintenance, and explicit bookable calendar slots per branch and staff member.

The problem
Bookings landing on days the clinic is closed or the room is unavailable.
What you get
One place to close the calendar, with the same rules applied to front-desk bookings and patient self-booking alike.

Post-visit reviews

Patients rate the visit and the staff member who delivered it. Your team replies from the same screen.

The problem
Feedback that arrives somewhere you cannot respond to it.
What you get
Ratings attached to both the appointment and the staff profile, with your reply stored alongside them.
02

Area

Clinic, branches & team

One account covers the whole facility — every location, every person, and exactly what each of them can reach.

Multi-branch management

Each branch carries its own name, phone, address, timezone and weekly working hours, and can be deactivated without losing its history.

The problem
A separate system, or a separate spreadsheet, per location.
What you get
One account for the whole facility, with branch-level assignment for staff, schedules and bookings.

Staff profiles

Professional title, biography, photo, assigned branches and services, whether the person is bookable, and the buffer to reserve after each of their appointments.

The problem
Patients booked with a staff member who does not offer that service at that location.
What you get
Booking only offers staff who actually work at that branch and provide that service.

Working hours, time off and commissions

A weekly recurring schedule per branch, vacation and unavailable periods, per-service commission rules, and the person's rating history.

The problem
Schedules kept informally, and payouts recalculated by hand.
What you get
Availability and commission both read from the same staff record the calendar uses.

Roles and granular permissions

Owner, manager, receptionist and doctor roles ship with the platform. You can also build a custom role and choose permissions one by one.

The problem
Giving someone access to revenue just so they can book an appointment.
What you get
You can only grant permissions you hold yourself, and a preview shows exactly what a role opens before you save it.

Dashboard access on invitation

A staff member exists as a bookable record first. Turning on dashboard access sends an email invitation and opens the front-desk console for them.

The problem
Login accounts created for people who only need to appear in the calendar.
What you get
Booking availability and system access stay two separate decisions, each reversible without touching the other.
03

Area

Patients & CRM

Every patient is one record: contact details, clinical profile, tags, notes and files — with every appointment, conversation and payment attached to the same person.

Patient records

Name, phone, email, gender, date of birth, national ID, source, preferred language and marketing consent, with age derived from the date of birth.

The problem
The same patient entered three times under three phone numbers.
What you get
One searchable record per patient, scoped to your clinic and no one else's.

Medical profile

Medical history, allergies, blood type and emergency contact details, kept on the patient's profile alongside a chronic-conditions flag.

The problem
Clinical context that lives on paper and is not there when it matters.
What you get
What a clinician needs before a visit, on the same screen as the booking history.

Tags and segmentation

Create colour-coded tags, assign them to patients, and filter the CRM by tag or by active status.

The problem
No practical way to find a specific group of patients when you need one.
What you get
Segments you can reuse when building a campaign's recipient list.

Notes, addresses and files

Internal notes, multiple addresses, and file attachments — PDF, PNG, JPEG or WEBP, up to 10 MB each.

The problem
Referrals and reports scattered across chat threads and email.
What you get
Documents stored against the patient, reachable by anyone with permission.
04

Area

Conversations & notifications

Patient messages arrive in one inbox whether the assistant or a person answers them — and routine messages go out on their own.

Unified conversation inbox

Every chat in one list with assignment state, agent presence, delivery and read receipts, attachments and typing indicators.

The problem
Conversations trapped on one receptionist's personal phone.
What you get
Any authorised team member can pick up a conversation with the full history in front of them.

WhatsApp Business, on your own number

Connect your clinic's own WhatsApp Business account through Meta's onboarding, sync your approved templates, and send from your number — never a shared one.

The problem
Business conversations running through someone's personal account.
What you get
Your number, your templates and your history, with template status and last-synced time visible per account.

AI-to-human handover

The assistant hands a conversation to a person when asked, or when it cannot help. Agents take over, accept, transfer, release, or return it to the AI.

The problem
A chatbot that traps the patient in a loop with no way out.
What you get
A handover queue with wait and handling times, staff-only internal notes, and a timeline of every transfer.

Notification automation

Rules fire on real events — appointment created, confirmed, cancelled, completed, rescheduled or no-show, plus payment and subscription events — with an optional delay.

The problem
Reminders sent by hand, or not sent at all.
What you get
Templates in Arabic and English across WhatsApp, email, push and in-app, with a scheduled queue, delivery logs and retry.
05

Area

Campaigns & follow-ups

Re-engagement without exporting a list. Campaigns run on the same WhatsApp connection, the same patient records and the same consent flags as everything else.

Campaign types

Birthday, holiday, reactivation, promotion, or a fully custom campaign — each created as a draft you fill with recipients before launching.

The problem
Marketing that never happens because building the list takes a day.
What you get
Recipients selected straight from your CRM, with the campaign held as a draft until you are ready.

Controlled sending

Choose which connected number sends, pick an approved template, then launch, pause, resume, cancel or duplicate — with a per-minute throttle and a daily cap.

The problem
A single blast that burns your number's reputation in an hour.
What you get
A send rate you control, and a paused campaign that resumes exactly where it stopped.

Delivery metrics

Queued, sent, delivered, read, failed and skipped counts per campaign, with delivery and read rates and a breakdown of non-delivery reasons.

The problem
Knowing a campaign was sent, but not whether it arrived.
What you get
Per-recipient delivery state, and a single action to retry everything that failed.

Consent honoured automatically

Patients carry a marketing opt-in flag, and an opt-out is applied without anyone having to action it.

The problem
Messaging people who already asked you to stop.
What you get
Opt-outs enforced at send time, not left to whoever builds the next list.
06

Area

AI & automation

Two assistants and a workflow engine, all reading the same clinic data — with what each one may do bounded by permissions, not by prompt wording.

Dashboard Assistant for your team

Ask about revenue, subscription, appointments, patients, staff, AI usage or AI health in plain language. It answers using read-only tools scoped to your own permissions.

The problem
Simple questions that mean opening four screens and generating a report.
What you get
An answer in a sentence — and never data the person asking is not allowed to see.

Patient-facing assistant

A chat widget on your public pages that finds a clinic, lists branches, services and doctors, checks real availability, and books the appointment.

The problem
Booking requests arriving after hours with nobody there to answer them.
What you get
Each choice is validated against live data on the server, so the booking reflects your real calendar rather than the conversation.

Knowledge base and prompts

Teach the assistant with text entries or uploaded TXT and Markdown files, processed into searchable chunks — plus reusable prompts you activate or retire.

The problem
An assistant that answers confidently, and wrongly, about your clinic.
What you get
Answers grounded in material you wrote, which you can rebuild or remove at any time.

Workflows

Pick a trigger event, add gate conditions, then chain actions — send an email or WhatsApp message to the patient or a staff member, picking a template by name — each with its own delay. Start from a ready-made clinic template or build your own.

The problem
Routine follow-ups that depend on somebody remembering them.
What you get
Automation you can read on a canvas, test-run before activating, and switch off in one click.

AI monitoring and usage

Average, P95 and P99 latency, time to first token, tool success rate, error rate, tokens per second, resolution rate and handover rate — plus token usage per agent.

The problem
AI cost and quality that are invisible until the invoice arrives.
What you get
Usage measured against your plan's monthly allowance, with prepaid credits available if you need more.
07

Area

Payments, invoicing & subscription

Two separate money flows: what your patients pay you, and what you pay for ZiyaraTech. Both are tracked in the workspace.

Payments and refunds

Record a charge against a patient, track its status, and issue a full or partial refund with a reason — every refund tied to its original payment.

The problem
Refunds reconciled from memory at the end of the month.
What you get
A complete charge-and-refund history you can filter by status.

Patient invoices and settlements

Invoices per patient with number, amount, status and issue date, plus settlement batches per period showing gross, fees and net.

The problem
Revenue figures that do not match what actually reached the account.
What you get
A period-by-period view of what was collected and what was deducted.

Your subscription and usage

Your plan, renewal date, auto-renew state and grace period, with live meters for appointments, WhatsApp messages, AI tokens and campaigns.

The problem
Hitting a plan limit mid-day with no warning.
What you get
Usage against limits visible before it becomes a problem — and your existing data stays fully accessible even if a period lapses.

Add-ons, credits and upgrades

Buy extra capacity directly — messages, appointments, campaigns, branches, staff seats — or prepaid AI credits. For anything outside your plan, request it and receive a quote.

The problem
Growth blocked until a plan change is negotiated.
What you get
Permanent add-ons that never expire, and a quote you accept only if the price works.
08

Area

Analytics & reporting

Numbers generated from the same records your team works in, so a report and a screen never disagree.

Live dashboard

Patients in your CRM, active staff, total appointments booked, and handovers waiting for an agent — on the workspace home screen.

The problem
Opening five screens to answer how the clinic is doing today.
What you get
The state of the clinic at a glance, refreshed on demand.

Daily and monthly reports

Generate a report for a date or a month covering appointments, completed, cancelled, revenue and new patients.

The problem
Month-end assembled by hand from several places that disagree.
What you get
A stored report per period that you can compare against the ones before it.

Trends

Appointment and revenue trends built from your generated reports, showing total, completed and cancelled over time.

The problem
A single month that tells you nothing about direction.
What you get
The shape of the business over time, not just its latest snapshot.

Channel and AI analytics

WhatsApp analytics per account, campaign delivery performance, and AI totals — tokens, requests, conversations, resolution rate and handover rate.

The problem
Communication spend with no measurable return.
What you get
Every channel measured the same way, in the same place.
09

Area

Integrations & developer tools

A general-purpose integration layer for connecting ZiyaraTech to whatever else your facility already runs.

API keys with scopes

Create named keys, choose exactly which scopes they reach, set an optional expiry, and rotate, deactivate or revoke them. The secret is shown once.

The problem
One all-powerful key shared with every vendor.
What you get
Per-integration keys you can narrow, expire and revoke independently.

Outbound webhooks

Register an endpoint, subscribe it to the events you care about, and receive signed deliveries with full history — HTTP status, retries, response body and a replay action.

The problem
Silent integration failures discovered days later.
What you get
Every delivery visible, and any failed one replayable without touching your data.

External system connections

Connect a practice-management, medical-record, ERP or CRM system to import and sync data, with a conflict policy, field mappings, inbound webhooks, health checks and a staff-provisioning review step.

The problem
Double entry between ZiyaraTech and the system you already own.
What you get
Records kept in step, with conflicts surfaced for a person to decide rather than silently overwritten.

Request and delivery logs

Every API request against your clinic — method, endpoint, status and response time — alongside the webhook delivery log.

The problem
An integration that broke, with nothing to look at.
What you get
A record you can search when something needs explaining.

Multi-tenant and permission-first, by construction

Your clinic's data is separated from every other clinic's at the data layer, and what each person can reach is decided by the permissions they hold — checked on the server on every request.

Tenant isolation

Every record belongs to exactly one clinic. Patients, conversations, files, reports and payments are scoped to your account and unreachable from any other.

Least-privilege permissions

Access is authorised server-side on every request, not merely hidden in the interface — and nobody can grant a permission they do not hold themselves.

Audit trails

Appointment timelines, conversation timelines, API request logs and webhook delivery history record what happened, when, and who did it.

Session and transport safeguards

Authentication tokens live in HttpOnly cookies with CSRF protection, and every page is served under a strict Content Security Policy.

Three things worth knowing up front

WhatsApp goes live through Meta

Connecting your WhatsApp Business number and authoring templates happens inside ZiyaraTech. Meta then verifies your business and approves each template before it can be sent — the same step every business using WhatsApp Business messaging goes through.

Card payments need merchant onboarding

Recording charges, issuing refunds, invoicing patients and generating settlements are available in the workspace from day one. Taking live card payments additionally requires activating a merchant account with the payment processor — a standard onboarding step arranged with our team.

Integrations are a framework, not a catalogue

Scoped API keys, signed webhooks and the connection layer let you integrate with a system you already run. There is no ready-made connector for a specific named practice-management or medical-record product yet.

See it against your own clinic's day