A connected day of care

A clearer way to run the clinic.

Bring patient records, scheduling, reception, queues and payments into one calm workspace designed for care teams.

Foundation in active development. Access is currently limited to configured clinic teams.

The platform

One operating picture, from arrival to checkout.

EzzeDr keeps the patient and visit record in the clinic workspace. Reception, practitioners and finance work from role-specific views of the same operational data. The current foundation covers core scheduling, queue and billing flows; more clinical and specialty workflows are being built.

Built for care teams

Designed for a broad range of outpatient clinics.

Specialty workflows are planned and will be introduced only when their clinical and operational rules are ready.

Medical centers

Dental clinics

Dermatology clinics

Aesthetic and cosmetic clinics

Laser clinics

Physiotherapy clinics

General clinics

Capabilities

The tools behind a well-run visit.

Availability labels describe the current application, not future marketing commitments.

Patient management

Tenant-scoped patient registration, MRNs and search.

Foundation available

Appointments & scheduling

Branch-local booking with slot collision protection.

Foundation available

Reception & check-in

A dedicated view of arrivals and daily operations.

Foundation available

Queue management

Guarded transitions from waiting to checkout.

Foundation available

Clinical records

Private documents exist; structured clinical workflows remain in development.

In development

Billing & payments

Invoices and integer-value payments with overpayment protection.

Foundation available

CRM & follow-ups

Follow-up and relationship workflows are planned.

In development

Staff management

Role-based membership exists; full staff operations are planned.

In development

Treatment packages & sessions

Data structures exist; end-to-end package operations are planned.

In development

Multi-branch management

Branch-aware data and access boundaries exist; broader operations are planned.

In development

Reports

Operational and financial reporting is planned.

In development

WhatsApp communication

An EzzeSend event adapter exists; live customer messaging is not configured.

In development

Reception

Know what needs attention now.

The reception workspace centers on the local clinic day, arrivals, the live queue and the next action for each patient.

01 Find or register a patient
02 Book an appointment or handle a walk-in
03 Check in and follow queue progress
04 Complete checkout and record payment

Patient journey

A continuous visit, with clear handoffs.

Before arrival

Scheduling connects the patient, practitioner, service and branch.

At reception

Staff see the appointment and check the patient into the queue.

During care

Queue status shows where the patient is in the visit.

At checkout

The team can see payment work associated with the visit.

EzzeSend connection

Communication around care, with a clear data boundary.

EzzeDr is the system of record for patient, appointment, clinical and financial data. EzzeSend is intended for WhatsApp communication and automation, using only the information needed for each communication.

Recipient policy, delivery records and workspace provisioning states are prepared. Live WhatsApp delivery and automatic remote workspace creation are not yet enabled.

EzzeDr EzzeSend

Clinic records stay in EzzeDr. Communication events travel through the integration boundary.

AI receptionist

A future conversational front door.

AI-assisted reception through EzzeSend is a planned capability. It is not available in the current application, and medical decisions remain with clinic professionals.

In development

Aesthetic clinics

Specialty operations deserve their own workflow.

Package balances, sessions and treatment context have a data foundation. Specialty-specific scheduling, treatment execution and liability handling still require implementation.

In development

Multi-branch

A clear boundary for every location.

The foundation stores branches, time zones and branch-scoped appointments. Access is checked on server-side clinic operations.

Privacy & security

Care data stays under clinic control.

EzzeDr uses tenant-scoped queries, role permissions, private medical document storage and audit events. Security review and production hardening remain required before clinical use.

Plans

Plan details are being defined.

Subscription options and pricing will appear here when the plan system and commercial terms are approved. No price is currently published.

Plans pending

Questions

A few practical answers.

Is EzzeDr available for self-service signup?

No. Access currently requires clinic setup by an administrator.

Does EzzeDr already send WhatsApp messages?

No live customer WhatsApp delivery is configured. The EzzeSend integration contract is still provisional.

Is the AI receptionist available?

Not yet. AI-assisted reception is planned through EzzeSend.

Does EzzeSend hold the medical record?

No. EzzeDr is designed to remain the system of record; EzzeSend is the communication layer.

Clinic workspace

A calmer day starts with a clearer view.

Configured clinic team members can sign in to the current foundation.

Terms

Public subscription terms are being prepared. Clinic access is currently arranged directly. Communication and AI services, when enabled, will be provided through EzzeSend and disclosed in the final service terms.

Privacy

EzzeDr keeps clinic records as the primary source. Any future EzzeSend communication will use the minimum necessary information and distinguish operational communication consent from marketing consent. A full privacy notice will be published before public onboarding.