Your entire clinic — in one program.
Plus two voice assistants: yours runs the clinic by voice, while the phone assistant speaks with patients in their own language.

• One subscription instead of three or four invoices. Management, invoicing, accounting, the insurance channel, prescriptions, reminders, backup — already inside. Not a single paid module: plans differ only by the number of physicians and voice minutes, never by functionality.
• The front-desk routine handles itself. The in-app assistant manages appointments alongside the physician; the phone assistant calls patients back on its own and arranges rescheduling. Not a set of prompts — real operations in the system while your hands are occupied with the patient.
• Nothing left to assemble. No more buying, connecting and paying for separate services on top of the base program. "All in one" here is not a slogan — it is the architecture.

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

• You give it a name. Choose in the clinic profile what your assistant is called — and the program adopts your assistant's name throughout.
• It greets you by name — you decide how it addresses you.
• You write its standing instructions in plain language — "I'm on vacation next week," "on Wednesdays I see patients until noon." This is its memory between sessions (you can also dictate them: "remember that…").
• It reminds you of whatever you asked — "remind me tomorrow at 2:00 PM to call the supplier" (it raises it in your first voice session after that time).
• It reads out incoming patient messages — those left by phone or sent on WhatsApp, along with voice-session summaries and patient feedback after visits.
• It respects clinic hours when booking and suggesting slots.
• It teaches you the program. You are not a programmer — ask "where do I click to set a price" or "how do I send an invoice," and it guides you step by step. Say "look at my screen" and it reads your screen and confirms whether the cursor is in the right place (desktop only).
• It looks things up online. Ask something general — the weather, a fact, a recent rule change — and it retrieves the answer and reads it back to you. Retrieval only; no clinical decisions.

The phone assistant works on a dedicated number: it answers patients, books, reschedules and cancels appointments, calls back from the waitlist. At the first sign of urgency it puts the call through to the physician's personal phone and reads the emergency number out to the caller; at night, with the clinic closed, it gives that number and offers to take a message. On every call it introduces itself as the clinic's automated attendant, not a person.

It selects the language itself. 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 speaker calling a clinic in Italy is answered in Spanish — while the chart entry is saved in the clinic's language. The in-app assistant likewise speaks with the physician in the physician's language.

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

Not one staff member picked up the phone. The schedule changes only after the patient's actual "yes" — not a moment sooner. That is the difference between "scheduling software" and "an assistant that runs your day."

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

During onboarding you select a profile, and the program opens exactly the modules your specialty requires (records, scales, documents, 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; pediatrics — growth chart and immunization schedule.

At the core is a universal channel to insurers: a single engine drives eligibility checks and claim submissions from configuration, with each clinic's credentials encrypted, access control in place and a secure audit trail.

• 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 program produces a detailed itemized 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 physician’s in-app voice assistant — fully. Hundreds of real actions by voice: schedule, patient cards, invoices, prescriptions, 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 physician signs and sends the prescription; prescription PDFs carry NPI and DEA, Schedule II refills are locked at 0.
• Patient communication via WhatsApp and e-mail (SMS switches on after A2P registration) — with TCPA consent management (opt-in/opt-out, STOP honored) and CAN-SPAM-compliant unsubscribe.
• State sales tax configuration for the rare states that tax medical services.

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

US law, honored 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 honored 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 program manages the clinic; diagnoses and prescriptions are entered by the physician. 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 phone assistant reads each line item 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 physician confirms. The built-in interaction table is not exhaustive and does not replace a professional drug reference: the absence of a warning does not mean the combination is safe.
• Delivery to the patient — by e-mail 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 your clinic — to them you are one of thousands. We will: write to us, every request is reviewed, and the most requested improvements ship in forthcoming updates. You have a direct line to the developer rather than anonymous support. The program grows with your clinic.

Click a plan to see its add-on minute packages.

• Clinic isolation. Each clinic's data resides in an isolated store with strictly token-based access in Microsoft's certified cloud. Every request is scoped 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 voice assistant does not record calls — neither audio nor transcript is stored; the system keeps call metadata (number, time, duration) and whatever the assistant files at the patient's request, such as a message for the physician or a refill request.
• Incidents. On a suspected security incident the clinic is notified, and access to cloud integrations can be suspended immediately from within the program.

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