Your practice phone picks up. Even when the waiting room is full.
Patients call, the receptionist is busy. Your agent takes the call, answers questions about office hours, prescriptions, and referrals, and books appointments. In emergencies, calls are routed to the practice immediately.
by Sven Pflüger · Founder & CEO, Rinqo·Last updated:
Notice under EU AI Act Article 50:On the first ring, the agent says clearly: you're talking to an AI. Just ask, and the agent connects you to a human.How we use AI
What does the AI phone assistant do for Medical Practices?
The AI phone assistant for medical practices answers every incoming call, handles questions about office hours, directions, prescriptions, and referrals, books appointments through calendar integrations, and identifies emergencies by keywords and tone. Urgent cases are routed immediately to the practice or the on-call medical service.
EU-Sovereign · GDPR · AI Act
Made in Germany. Hosted in Europe. AI-Act-ready before the deadline.
GDPR-compliant on EU servers
All calls, transcripts and knowledge data are processed encrypted on Hetzner Cloud in Falkenstein and Nuremberg, no US Cloud Act exposure, no third-country transfer. DPA in place.
LLM inference: Microsoft Azure OpenAI Service (Microsoft Ireland, Sweden Central, EU Data Boundary) as single-AI backbone — OVHcloud as opt-in Pure-EU failover
Speech: Deepgram in EU setup + KugelAudio (German company, EU-hosted)
Auto-deletion after 30/90 days, configurable per org
AI Act Art. 50, implemented before 2 Aug 2026
From 2 August 2026 every AI system must disclose to end users at the start of the conversation that it is AI-based. Rinqo enables this by default everywhere, before the deadline, not after.
Voice: mandatory disclosure as first audio frame, before any answer
Chat/Email: AI label in footer and subject
Synthetic audio will be machine-watermarked once Code-of-Practice (June 2026) ships
Penalty: up to €15M or 3 % global annual turnover (whichever is higher)
Sources: GDPR Art. 28 + 32 · EU AI Act Regulation 2024/1689 · BfDI guidelines.
Why Medical Practices need an AI agent.
Practice management observations from the German market show: an average practice handles around 50 calls per day at an average call duration of 3.5 minutes, that adds up to nearly three hours of daily phone time, often distributed across just one or two medical assistants. Roughly half of all calls revolve around appointments. According to KBV figures only about 20 percent of appointments are booked online, the rest still flows through the phone. The peak hits Monday morning and after holidays: appointment requests, prescription refills, and acute complaints all arrive at once. Callers stuck on hold hang up and call the next practice, or land in the on-call service, which amplifies the bottleneck. This is not a staffing problem but a structural peak-load problem, and that is exactly what an AI phone assistant solves: it scales in parallel, never drops a call, and stays reachable Monday at 8:15 a.m.
Patients hang in the queue and hang up
The receptionist is juggling the front desk and the phone at the same time
After hours and on weekends, nobody is reachable
Routine prescription requests block the line for real emergencies
“
When the phone rings after a holiday, we simply can't handle every patient in the first two hours. The ones that slip into the hold queue are gone.
How the Phone Agent for Medical Practices.
Your AI phone assistant answers every call within seconds, even when all lines are busy. It answers questions about office hours, directions, and insurance acceptance, captures prescription requests in a structured way, and books appointments through your calendar integration. For emergencies it recognizes keywords like chest pain, shortness of breath, or bleeding and routes immediately to the practice or the on-call service. After every call you receive an email summary, caller, concern, next step.
~50calls per day in an average practice (practice management observation)
~50%of calls revolve around appointments (practice management observation)
Rinqo picks up every call. At night, on weekends, always.
Why Rinqo for medical practices, three hard facts on GDPR, sovereignty and AI Act.
Patient data is not marketing data. Anyone choosing a phone system with AI for a medical practice doesn't check voice quality first, but who has access to the conversation, where it's stored, and whether the practice stands clean before the state data protection authority on a data breach report. Three facts that technically and legally separate Rinqo from US voice AI platforms and classic IVR solutions, and why each of these points becomes non-negotiable for practices from August 2026.
GDPR Art. 9 + 32
Patient data stays in Germany, physically and contractually.
Rinqo processes all calls exclusively in EU data centers: Hetzner Falkenstein and Nuremberg for app, database, knowledge index and voice pipeline (ISO 27001:2022 certified, valid since September 2025). Speech-to-text via a speech recognition service in an EU setup or optionally Faster-Whisper on own Hetzner server. Voice synthesis via a German provider with EU hosting — content is not processed outside the EU. The data processing agreement (DPA) per Art. 28 GDPR is digitally signable by default and part of every plan. Patient record data doesn't enter the system anyway, the agent is phone assistant, not anamnesis tool. On a state data protection authority request or a GDPR inquiry your practice stands clean.
Hetzner Falkenstein (DE), ISO 27001 · DPA Art. 28 included
EU Sovereignty
AI models run on European GPUs, not on US cloud.
The language model sits primarily at Microsoft Azure OpenAI (Microsoft Ireland, Sweden Central, EU Data Boundary, EU region) with automatic fallback on OVHcloud Roubaix as opt-in failover. We don't use OpenAI directly, no Google Gemini, no Anthropic-US. This aligns with the updated joint recommendations from the German Medical Association (BÄK) and KBV on medical confidentiality and data processing (status October 2025), which explicitly require EU servers for external data processing. We are also prepared for the next stages of the EU AI Act: training obligation under Art. 4 in force since February 2025, operator obligations for high-risk healthcare AI under Art. 26 effective 2 August 2026 (Annex III) and 2 August 2027 (MDR pathway). Scaling phase 4: fully self-hosted on own Hetzner GPU nodes from ~1,000 customers, then no call leaves the Rinqo Hetzner VLAN.
Microsoft Azure OpenAI (Microsoft Ireland, Sweden Central) + opt-in failover providers (EU fallback) · no US LLMs
AI Act Art. 50 (effective 02.08.2026)
Transparency obligation fulfilled, before it becomes mandatory.
From 2 August 2026, Article 50 of the EU AI Regulation requires every practice using an AI-supported phone assistant to ensure the calling person can recognize they are talking to an AI. Rinqo handles this automatically: every outgoing call strand begins with an audible disclosure line (example: "This is the digital practice assistant of Dr. Müller, I am an AI."), wording is customer-voice-compliant editable. On the marketing side we show the disclosure as disclosure strip above the first demo. This is not compliance theater but a trust line: openly communicated AI is generally accepted well in practice, patients give the system a chance because they know what they're dealing with.
Audio disclosure per call · Visible hint in marketing · Editable per brand voice
Rinqo vs. classic solutions for medical practices.
Most practices compare three options today: a classic IVR menu from the German telephone provider, a US voice AI platform with German language model, or simply the answering machine. Here's the honest overview.
Feature
Rinqo
from €99 net/mo
DE IVR
classic phone system
US Voice AI
international providers
Answering machine
Classic
Answer calls individually
Free dialog, AI
Menu only
Free dialog, AI
Recording only
GDPR + EU data center
Hetzner DE, DPA incl.
DE provider
US cloud, Cloud Act
Local
AI Act Art. 50 disclosure
Auto & editable
,
Manual config
,
Calendar appointment booking
Cal.com, Google, PVS
Custom setup needed
Emergency triage + 116117
Default
Custom config
DE IVRs are stable but cannot conduct dialogues. US voice AI is dialogue-strong but legally vulnerable in DACH per Schrems-II. Answering machines are conversion killers. Rinqo is the only option that combines free AI dialogue, GDPR compliance, AI Act disclosure and native calendar booking, making it the consistent choice for medical practices in 2026.
What your agent does for Medical Practices.
Office hours and directions
Appointment booking and cancellations
Prescription requests
Referrals
Emergency routing
Features of the Phone Agent
Answers common questions automatically
Books appointments directly in your calendar
Qualifies inquiries and captures contact details
Routes complex cases to your team
Speaks 20+ languages
Learns from your website and documents
Honest answers to real concerns.
The four questions every practice owner asks us before they start.
Can the agent really identify an emergency?
The agent listens for keywords like chest pain, shortness of breath, unconsciousness, and for tone of voice. On suspicion, the call is routed immediately to your practice lead or the on-call service. Triage is intentionally conservative, when in doubt, the agent escalates.
What happens to patient data?
All transcripts run encrypted on EU servers (Hetzner Germany) and are deleted after a configurable retention period (30 days by default). Rinqo is GDPR-compliant with a data processing agreement in place. Diagnoses or findings are never requested, the agent is a phone assistant, not an anamnesis tool.
Does it integrate with my practice management system?
The agent books appointments through calendar integrations (Cal.com, Google Calendar). Direct connections to practice management systems like medatixx, T2med or CGM are in the works. Until then, sync your PMS calendar with Google Calendar once, 15 minutes in any practice.
What if the agent can't answer a question?
It says so honestly, captures the request structured, and offers a callback from your practice team. You see all open items immediately in the dashboard and can update the knowledge base in a minute, next time the agent can answer.
Frequently asked questions about the Phone Agent for your industry Medical Practices.
Yes. Your agent recognizes emergencies based on keywords and tone of voice. In those cases, the call is immediately routed to the practice or the on-call service.
Rinqo works via a phone number you assign to your practice. Appointments can be synced through calendar integrations. Direct integration with practice management systems is in the works.
Your agent is available 24/7. It answers questions, takes appointment requests, and directs callers to the on-call medical service in case of emergencies.
Multi-channel for your industry
Rinqo for Medical Practices, all channels
Telephone, chat and email from one platform: business case, ROI, GDPR and integrations.
Sven builds Rinqo from a simple observation: most AI tools are designed in San Francisco and sold in Berlin. The workshop in the Black Forest, the veterinary practice in Salzburg, the family hotel in Tyrol get software that doesn't speak their language. Rinqo flips that. On European servers, set up in ten minutes, in twenty languages. With templates built by the industries themselves.
