Your entire clinic in a single platform.
With two voice assistants: one runs the clinic by voice alongside you, the other answers patients on the telephone in their own language.

• One subscription in place of three or four invoices. Management, invoicing, accounting, the insurance channel, prescriptions, reminders and backups are already included. There is not a single chargeable module: plans differ only in the number of doctors and voice minutes, never in features.
• The reception routine takes care of itself. The in-app assistant manages appointments alongside the doctor, while the telephone assistant returns patients' calls and arranges rescheduling. These are not prompts but real operations in the system, carried out while your hands are occupied with the patient.
• Nothing left to assemble. There is no need to buy, connect and pay for separate services on top of a base package. Here “all in one” is not a slogan but the architecture.

The in-app assistant resides within the software, knows your entire clinic and acts on voice commands — natural, conversational speech in real time (you can interrupt it with a stop word and ask again).

• You give it a name. Set in the clinic profile what your assistant is called, and the software answers to your assistant's name.
• It greets you by name — you set how it addresses you.
• You write its instructions in plain language — “I am on leave next week”, “on Wednesdays I see patients until midday”. This is its memory between sessions, and you can dictate it as well: “remember that…”.
• It reminds you of whatever you asked — “remind me tomorrow at 2 pm to ring the supplier”; the reminder appears in your first voice session after that time.
• It reads out incoming patient messages — those left by telephone or sent on WhatsApp, together with voice-session summaries and patient feedback after visits.
• It respects clinic hours when booking and suggesting slots.
• It shows you how to use the software. No technical knowledge is required: ask “where do I click to set a price” or “how do I send an invoice”, and it takes you through step by step. Say “look at my screen” and it reads your screen and tells you whether the cursor is in the right place (on the desktop).
• It looks things up online. Ask a general question — the weather, a fact, a recent change in the rules — and it retrieves the answer from the internet and reads it back. Retrieval only; no clinical decisions.

The telephone assistant operates on a dedicated number: it answers patients, books, reschedules and cancels appointments, calls back from the waiting list. At the first sign of urgency it puts the call through to the doctor's personal phone and gives the caller the emergency number; overnight, with the practice closed, it gives that number and offers to take a message. On every call it introduces itself as the practice's automated attendant, not a member of staff.

It selects the language unaided. It greets the patient with the clinic's name in the country's language, then identifies the caller's language from their first words and switches to it: a Spanish caller reaching a clinic in Italy is answered in Spanish, while the record itself is saved in the clinic's language. The in-app assistant likewise speaks to the doctor in the doctor's own language.

You are held up in traffic with an appointment in twenty minutes. You tell the in-app assistant:

No member of staff touched the telephone. The schedule changes only after the patient has genuinely agreed — not a moment sooner. That is the difference between scheduling software and an assistant that keeps the day running.

The in-app assistant is not a demonstration with a handful of commands. Behind it are hundreds of voice actions, and the great majority perform real operations in the system:

During onboarding you choose a profile, and the software opens precisely the modules your specialty requires — records, scales, documents and the voice command set:

For example: dentistry — dental chart and periodontology; cosmetology — face/body chart, mole map, injection log, before/after photos; psychiatry — MSE, risk assessment, PHQ-9 / GAD-7 scales, therapy goals; paediatrics — growth chart and immunisation schedule.

Inside is a universal channel to insurers: a single engine performs eligibility checks and claim submissions from configuration, with each clinic's credentials encrypted, access controlled and a secure audit trail throughout.

• USA — live Availity and Stedi integrations for eligibility checks (270/271) + Stedi 837P claim submission. Each clinic connects its own account.
• Israel, UK, Germany, France, Italy, Spain — a document-based reimbursement model: the platform produces a detailed itemised invoice/receipt in 7 languages (for Israel — ready-made insurer letters as well), which the patient submits to their own insurer.
• Any insurer with an API connects through configuration — you paste in the provider's documentation, and the engine generates a template.

Built and verified for US clinics (registration opens with the staged rollout):

• The doctor’s in-app voice assistant, in full. Hundreds of real actions by voice: scheduling, patient records, invoices, prescriptions and reminders.
• Insurance: live Availity and Stedi integrations — eligibility checks (270/271) and 837P claim submission; superbill PDF for out-of-network reimbursement.
• E-prescribing (Photon, USA only) — one click opens the provider's window where the doctor signs and sends the prescription; prescription PDFs carry NPI and DEA, Schedule II refills are locked at 0.
• Patient communication by WhatsApp and email (SMS is enabled after A2P registration) — with TCPA consent management (opt-in/opt-out, STOP honoured) and CAN-SPAM-compliant unsubscribe.
• State sales tax configuration for the rare states that tax medical services.

The patient-facing telephone assistant is not yet enabled in the USA. Voice calls carry health information, so it is enabled only under a dedicated Business Associate Agreement with the telephony carrier; negotiations are in progress. The platform is fully usable without it, and the moment the agreement is signed the telephone assistant is enabled for US clinics with no migration.

US law, honoured in the architecture:

• HIPAA-aligned safeguards — health data is encrypted at rest (field-level AES-256-GCM on top of database encryption) and in transit (TLS); access is written to a tamper-evident audit log; a Business Associate Agreement is available for your clinic.
• HIPAA-aligned infrastructure — hosting on HIPAA-eligible cloud services and zero-data-retention speech terms under DPAs (current list on the Sub-processors page); a Business Associate Agreement is available for your clinic.
• TCPA — texting a patient requires recorded consent; revocation is honoured everywhere, including automated reminders.
• California SB 1001 — wherever the assistant speaks, it discloses that it is a voice assistant, not a human.
• Not a medical device — the software manages the clinic; diagnoses and prescriptions are entered by the doctor. See medical device status.

• Eight payment systems under one interface: Stripe, PayPal, Tranzila, Cardcom, PayPlus, Green Invoice, Grow, iCount.
• An invoice with a payment link — in one step; the link can be sent via WhatsApp or SMS.
• “What did I pay for?” — the telephone assistant reads each line of the invoice to the patient and reconciles it against the clinic's price list.
• Credit notes — proper reissuing: the original stays unchanged, a new document gets its own number; partial notes, discounts with tax recalculation.
• VAT and tax by country — the system computes the right rate for the country and prints a legally correct fiscal footer.
• Annual tax report — a 6-sheet Excel export, ready for your accountant.

• Country-specific prescription PDF — USA (NPI, DEA), UK (GMC, private prescription), Israel (RTL Hebrew), Germany, Spain, Italy, France — with the clinic header, allergy banner, signature and a QR code for verification.
• Safety built in — checks for allergies, drug interactions and controlled-substance rules; a risky combination is flagged with a warning, and the prescription goes ahead only once the doctor confirms. The built-in interactions table is not exhaustive and is no substitute for a professional formulary: the absence of a warning does not mean the combination is safe.
• Delivery to the patient — by email as a direct attachment; through a secure portal with a one-time code, the patient sees their prescriptions and can request a refill.

Large vendors will not add a feature for a single clinic — to them you are one of thousands. We will: write to us, and we review every request and release the most requested improvements in forthcoming updates. You have a direct line to the developer rather than an anonymous helpdesk. The software grows with your clinic.

Select a plan to see its additional minute packages.

• Clinic isolation. Each clinic's data is held in an isolated set with strictly token-based access in Microsoft's certified cloud. Every request is confined to your clinic alone, and the isolation is verified continuously by automated checks.
• Encryption. Data is transmitted over TLS; sensitive fields (names, contacts, medical notes) are encrypted in the database. A clinic's integration credentials are stored encrypted.
• Access control and audit. Login by staff PIN codes, role-based permissions; key actions are written to a secure audit log with an integrity chain.
• Backups. A daily encrypted backup; at any time the clinic can export its entire database (Excel / ZIP) and request permanent deletion of all data.
• Subprocessors. Medical information is not shared with third parties other than trusted infrastructure providers (cloud hosting, speech technology, telephony, messaging delivery), each under its own DPA / BAA — the up-to-date list is on the Sub-processors page.
• Calls. The telephone assistant does not record calls: neither audio nor transcript is stored. The system retains call metadata (number, time, duration) and anything the assistant files at the patient's request, such as a message for the doctor or a repeat-prescription request.
• Incidents. Where a security incident is suspected the clinic is notified, and access to cloud integrations can be suspended instantly from within the software.

More detail — in the Privacy Policy, AI Act Disclosure and Medical Device Status.