Patient Voice Agents
V

Vite Clinic

AI phone receptionist for Swiss medical practices and clinic groups. Clinics forward calls from their existing number; a realtime assistant answers routine questions around the clock, books and changes appointments and records callbacks in the clinic's practice management system through a connector built per clinic, and transfers medical, urgent, sensitive and uncertain calls to clinic staff under the clinic's rules. The clinic controls what share of forwarded calls the assistant answers and reviews its behavior before live use. It claims Switzerland's four national languages, Swiss German and 40-plus languages.

The terms describe it as an administrative communications tool and not a medical device. Stored data is hosted with Infomaniak in Switzerland; live audio runs through Twilio and speech and assistant processing through OpenAI, on routes outside Switzerland until European routing is verified, all set out on a public provider register with retention periods. Price: CHF 200 per 100 calls after paid onboarding, with a 30-day live pilot. Accounts are by private invitation and no clinic deployment is published yet. Operated by Benjamin Crozat EI, a sole proprietorship registered in Nice, France (SIREN 750 497 570); launched 2025.

AI Health Index verifiedSeptember 23, 2026
Compare Vite Clinic with other vendors
Founded
2025
Headquarters
Nice, France
Website
viteclinic.ch
Categories
patient-facing-voice-agents, healthcare-admin-automation
Indexed Products
AI phone receptionist, Clinic dashboard, Clinic group rollout
Assessment

Capability Axes

An AI Health Index grade measures what a buyer can verify from public sources on the date shown. It is not a rating of how good the product is. A vendor can build an excellent system and grade low on an axis because it publishes nothing an outsider can check. How grades read

AI Capability
AA on AI CentralityThe artificial intelligence is the product. Remove the model and there is nothing left to sell.
Vendor Published

The conversation is the product. A realtime model answers the clinic's forwarded calls, understands the request, answers approved clinic questions, records or completes booking changes and hands medical, urgent, sensitive and uncertain matters to staff; there is no human agent tier behind it and no other product in the catalog. The dashboard reports what the assistant did. With the model removed, nothing is left to sell. The model is bought from OpenAI rather than built, which is recorded on the supply chain and transparency rows rather than here.

BB on Autonomy and Oversight ModelThe oversight structure is described and one part is missing, commonly the threshold at which the system stops or what happens after it is wrong.
Vendor Published

The boundary is published in both directions and one part is missing. Routine questions and appointment changes are handled on the call; the terms say 'human, medical, sensitive, or uncertain matters remain with clinic staff' and that the assistant may refuse, escalate or hand off when information is missing or safety rules apply; the home page shows callers with symptoms or medication questions transferred straight to a person.

The clinic sets the routing rules, approves the assistant's behavior and the human path before live calls, and controls what share of forwarded calls the assistant answers. A booking request is not a confirmed appointment unless an enabled integration confirms it. What is missing is the threshold at which the assistant judges a call medical or uncertain, and what happens when it treats a medical call as routine.

BB on Model and Technology TransparencyThe approach or the suppliers are named without the version and update discipline behind them. Naming a supplier is the entry to this band both here and on Model Supply Chain Disclosure, which ask different questions of the same disclosure: who receives the data, and what produces the output.
Vendor Published

The model supplier is named and the configuration is described; the model itself is not. OpenAI powers realtime speech and the assistant, Twilio carries live audio, Infomaniak hosts the application in Switzerland, and each provider's role in the call path is described on the trust page. The clinic's own approved information and routing rules configure the assistant. No model family, version or update practice is named, and the trust page says the eligible models and endpoint settings for European processing still require verification.

AA on Model Supply Chain DisclosureEvery party is enumerated by name including the model layer. A public subprocessor list naming the model provider, with the retention and training terms that govern data once it arrives, is the canonical artifact.
Vendor Published

Every party between a patient's call and the answer is named, with its role, retention and terms. The trust page lists Infomaniak Network SA (Swiss application hosting, database and encrypted backups), Twilio Ireland Limited (Swiss number, routing and live audio, with its call-record retention, its dependencies including Twilio Inc., AWS and ClickHouse, and its transfer safeguards) and OpenAI Ireland Ltd. (realtime speech and assistant processing, with API data not used for training unless the customer opts in, abuse-monitoring logs of up to 30 days, and its current subprocessor list naming Microsoft, CoreWeave, Oracle Cloud, Google Cloud, AWS, Cloudflare, Snowflake, Confluent and Cerebras). New subprocessors require advance notice and an objection period. Each provider entry states its current position, including that European routing and reduced retention still require verification.

DD on Clinical and Operational EvidenceNo named deployment and no performance claim a reader can check. A figure published with no source sits here rather than higher.
Vendor Published

No named deployment and no measured result. The home page cites a Swiss medical assistants survey (1,063 respondents) and four quotations from practice staff drawn from third-party publications, which describe front-desk overload rather than how this product performs.

The terms describe account access by private invitation, paid onboarding and a 30-day live pilot, and the trust page lists checks confirmed with a clinic before patient calls begin; no clinic, call volume, transfer rate or outcome is published. A public demonstration line answers calls, which shows capability rather than use.

AA on AI Safety and PHI StewardshipRetention windows, training use and de identification are all stated specifically enough to be contradicted. Safety engineering, meaning guardrails, hallucination mitigation and how a safety event is handled, does not gate this grade: no vendor in this index publishes it, so every note on this axis states that gap rather than leaving it implied.
Vendor Published

Retention, training use and de-identification are each stated specifically enough to be contradicted. Retention: raw call audio is not intentionally stored; transcripts, caller identifiers, health-related free text and handoff payloads are scrubbed after 30 days; the reduced operational call record is deleted after 365 days; audit records are kept 365 days and application logs 14; clinic agreements may set shorter periods, and backups expire on a documented schedule.

Training: the company does not train its own models on call data, sell it or use it for advertising, and the model provider's API data is not used for training unless the customer opts in, with default abuse-monitoring logs of up to 30 days until reduced-retention controls are verified. De-identification: sensitive content is stripped from call records at 30 days, and account data is removed or anonymized when an account closes. Safety engineering, such as how a misheard detail is caught or how a safety event is reported, is not described.

Regulatory and Compliance
BB on HIPAA and BAA PostureBusiness associate status is stated and supported by a substantive privacy document, with the agreement or its scope not fully published. For a vendor outside the United States, an equivalent regime documented to this depth grades here. A vendor whose product does not process protected health information grades here too when it says so plainly and explains the scope, with a service privacy document behind it: stating a position a buyer can rely on is the posture this axis grades, and the band above is closed to it because there is no agreement to publish.
Vendor Published

United States health privacy law does not reach this service; its Swiss equivalent is stated and documented in depth. The privacy notice separates the website and account service, for which the operator is controller, from patient calls, for which the clinic is normally controller and Vite Clinic acts as processor on documented instructions; it notes that call content can reveal health data and be covered by Swiss professional secrecy, and requires the clinic to disclose AI use, obtain consent and offer a human route.

The terms require a signed data processing agreement before live calls, bind staff to confidentiality for data under professional secrecy, and commit to incident notification and deletion at service end; the trust page says contractual transfer safeguards do not by themselves resolve professional secrecy. The processing agreement is available only as a draft in a security pack on request.

DD on Security Certifications and Trust CenterControls are asserted with nothing independent behind them, or nothing is published. Read the note before concluding anything: this is the grade most often corrected on a second pass, because assurance material frequently sits on a parent domain or inside an old announcement rather than on the product pages.
Vendor Published

Controls are described and nothing independent stands behind them. The trust page, with a last review date of 27 July 2026, lists HTTPS across the site, application and APIs, named organization memberships controlling access, audit records for sensitive account and clinic actions, encrypted backups, signed deployments with a documented rollback path, operational logs designed to avoid call content, and a documented incident response.

No certification, external audit or penetration test is claimed, and the security pack (architecture diagram, access controls, draft processing terms, impact assessment and incident plan) is available on request.

BB on FDA and Regulatory StatusThe pathway is stated and in progress, or a clearance is named without the vintage and scope a buyer needs to match it to the product on offer.
Vendor Published

A regulatory position is stated and the marketed capability matches it. The terms say Vite Clinic 'is an administrative communications tool. It is not a medical device, clinician, diagnostic service, emergency line, or substitute for professional judgment', forbid configuring it to diagnose, prescribe or give patient-specific medical advice, and require the clinic to keep emergency instructions and alternative contact paths; the trust page and privacy notice add that it makes no automated medical diagnosis or triage.

The marketing matches: the home page shows callers with symptoms, medication reactions or a worsening child sent straight to a person, so a clinician or clinic staff member decides every medical call. The boundary to hold is the classification itself, since a medical call treated as routine never reaches staff.

DD on AI Governance and Bias DisclosureNothing published on how model behavior is governed or tested. Multilingual operation with no subgroup performance sits here when the vendor markets recognition quality as a strength, because a caller the system failed to understand leaves no complaint and no record.
Vendor Published

Multilingual operation is sold as a strength and nothing is published on how the assistant performs by language. The home page says it 'speaks 40+ languages and can switch during the same call' and supports Switzerland's four national languages and Swiss German.

No per-language accuracy, transfer rate, evaluation method or test results are published, and a caller the system fails to understand hangs up without leaving a complaint, so a clinic cannot see a gap by language unless it is measured. The trust page cites the Swiss data protection authority's guidance on AI and states that the service makes no automated diagnosis, triage or legally significant decision, and the clinic reviews the assistant's behavior before live calls.

CC on AI Liability and RecourseMechanisms exist that let someone challenge an output, such as audit trails, source traceability or review before commit, with nothing standing behind the output and no route for the harmed party.
Vendor Published

Mechanisms exist to check what the assistant did, and nothing stands behind its output on the published terms. Clinic staff see call history, outcomes and transcripts, audit records cover sensitive account and clinic actions, the clinic reviews the assistant's behavior before live calls, and booking requests are not confirmed appointments unless an enabled integration confirms them.

The terms promise no error-free operation unless a signed service level says so, place any liability cap and service credits in the order form, and exclude indirect loss. The right under Swiss data protection law to correct inaccurate data runs to the clinic as controller and is not a commitment by the vendor. The operator is a sole proprietorship registered in France, so the practical value of recourse against it is a buyer's question.

Integration and Deployment
DD on EHR and Interoperability DepthNo integration evidence. A connector described as available on request grades here until one exists.
Vendor Published

Integration is a process to be carried out per clinic, not a connector that exists. The terms say the clinic introduces Vite Clinic to its practice management system provider, Vite Clinic builds the agreed connector and targets completion within three business days once usable access and documentation arrive, and practice management actions are limited to what the provider exposes and the clinic approves; until an integration is enabled, 'a request is not a confirmed appointment'. The home page describes booking and follow-ups kept in the clinic's system. No practice management system is named, no completed connector or marketplace listing is published, and no clinic is live.

BB on Deployment Model and Data ResidencyOptions and residency are stated with isolation or the processing path left open.
Vendor Published

Residency and the cross-border path are both stated; isolation is not. Persistent application data, the database and encrypted backups are hosted with Infomaniak in Switzerland. The privacy notice and trust page state plainly that live audio and call content are processed separately: Twilio calls use a United States route until European routing in Dublin is verified, and OpenAI processing may be global until European processing, reduced retention and the contract amendment are verified, adding that 'regional configuration is not proof that every data category stays in that region'. A clinic choosing the service for Swiss residency gets it for stored data today, not for live calls. Tenant isolation is not described and the production backup window is a launch check.

Commercial
BB on Commercial TransparencyA price or a pricing basis is published without full tiers, so a buyer can size the cost before making contact.
Vendor Published

A price and unit of charge are published, and the route in is a conversation. The home page states CHF 200 per 100 calls after onboarding and 'pay for calls, not minutes'; the terms define when a call is billable (it connects, ends normally, contains real conversation and is not a provider or technical failure) and say onboarding is a separate paid item priced in the order form, with usage billing starting only when the live service is activated.

Accounts are by private invitation after direct contact, followed by a 30-day live pilot that ends in a decision to continue, expand, adjust or stop. Onboarding is not priced publicly, and liability caps and service credits sit in the order form.

CC on Setting and Specialty CoverageCoverage is claimed broadly without specifics, or stated clearly with nothing validating it yet.
Vendor Published

The product handles front desk calls, answering routine patient calls, booking and changing appointments and recording callbacks and follow-ups in the clinic's practice management system, and passes medical and sensitive calls to staff.

Coverage is claimed narrowly and stated clearly: outpatient clinics and multi-site clinic groups in Switzerland, with Switzerland's four national languages and Swiss German named and 40-plus languages claimed, and per-site rules for hours, practitioners and emergency instructions. Nothing validates it yet: no clinic, specialty or site is named, and account access is by private invitation ahead of a first pilot. The site also says it is 'available in English or French', a narrower statement than the language claim.

Alternatives

Alternatives to Vite Clinic

Vendors in the same categories as Vite Clinic whose graded profiles look most alike, with a line on what each product does.

Similar is not the same, so check that each one does the job you need. No vendor pays for placement.

Paratus Health builds generative voice agents for outpatient facilities, medical practices, and dental groups.

AI voice agents for patient access and revenue cycle calls.

ActiumHealth is the healthcare patient communication product of Syllable, which acquired it in March 2024 and runs it as a division.

Marisa.Care, based in Belo Horizonte, Brazil, sells AI agents to hospitals, clinics, health plans and laboratories in Latin America.

Hello Patient (Patient Engagement Technologies, Inc.) sells AI agents, led by an assistant called Mia, that handle patient conversations by voice, text and web chat, inbound and outbound…

Conversational AI agent platform for health systems and payers, covering the call center, website, text messaging and mobile apps.

Ordered by how closely the graded profiles match across the fifteen axes, inside the same categories. See how each axis is graded in the methodology.

Commercial

Pricing

Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.

Entry Price Pricing Basis BAA Tier Implementation Source
CHF 200 per 100 calls
Per call: CHF 200 per 100 calls after onboarding; billable-call definition in the terms Not applicable. United States health privacy law does not reach this service. The vendor describes a data processing agreement, a caller notice and a professional secrecy review confirmed with the clinic before patient calls begin, and acts as processor on the clinic's documented instructions. Paid onboarding, priced in the order form; not published Vendor Published

Published on the home page: CHF 200 per 100 calls after onboarding, charged per call rather than per minute. The terms define a billable call (connects, ends normally, contains real conversation, not a provider or technical failure), make onboarding a separate paid item priced in the order form, and start usage billing only when the live service is activated after a 30-day pilot. Accounts are by private invitation after direct contact; a public demonstration line is free. Ask for the onboarding fee, included calls, overage rules and the order form's liability terms.