
Appointment requests
Collect the required information and follow your practice's appointment workflow to help patients automatically schedule where possible.
AI administrative assistant for your practice
Lebi answers your patient calls, handles the recurring ones according to your workflows, and gets each request done - from confirmed appointment to a structured request with the right colleague.
Your team stays in control and has more time for patients.

The bottleneck
Calls peak as soon as the practice opens. Staff get interrupted while helping patients. People call again because they could not get through the first time. And hiring extra assistants is harder than ever.
Lebi changes that.

No more busy lines
Lebi can handle many patient calls at the same time, so patients can reach your practice even during peak calling times.
Why your practice needs Lebi
Your team stays with patients, not the phone. Lebi gives you back the time that used to disappear into callbacks and repeated questions.
“I'd like an appointment.”
Lebi books a suitable slot where possible.
“I need a repeat prescription.”
Lebi collects a structured request for the right colleague.
“Can you call me back?”
Lebi creates a structured callback request.
Complex or unclear request
Lebi hands over to your team.
Everything is visible in your dashboard.
What Lebi can handle
Lebi identifies what the patient needs and follows the workflow your practice has configured.

Collect the required information and follow your practice's appointment workflow to help patients automatically schedule where possible.
Ask your predefined questions and send the request to the right team member in a structured format.
Lebi does not approve medication or give medication advice.

Collect the relevant details and create a timely and structured callback request for your team.
Provide predefined information such as opening hours, preparation instructions and other common practice information.
After the call
Every request arrives in your dashboard as a structured summary. From there your team can copy the outcome into the patient record & generate a draft of the administrative follow-up. Lebi prepares; your team reviews and decides.
Your practice decides what Lebi handles, when a human takes over, and what happens after the call.
Repetitive communication follows a defined workflow and Lebi helps get it done.
How it works
We start with the way your practice already works, then configure Lebi around your workflows, questions, rules and handovers.
Step 01
Map your workflows
Write down how your front desk handles each request today. Lebi turns those routines into a clear map.
Step 02
Configure your rules
Start from healthcare-specific templates and adapt questions, wording, hours, routing, recipients and handovers.
Step 02
Configure your rules
Start from healthcare-specific templates and adapt questions, wording, hours, routing, recipients and handovers.
Step 03
Let Lebi handle the routine
Lebi follows the configured workflow. Anything unclear, complex or outside the agreed route follows the handover your practice defines.
Your practice defines the process.Lebi follows it consistently.
Call Lebi and have the conversation a patient would have. It takes about a minute.
Lebi identifies itself as an AI assistant at the beginning of every patient conversation.
The call above is only the patient-facing part. Behind it are your workflows, your routing rules, structured requests landing where your team works, and a dashboard they control.
The call is what patients experience. The platform is what your team works in.
It only takes 20 minutes
With Lebi on your side
Routine calls no longer have to interrupt reception and practice staff every time.
Patients can reach the practice during busy periods - even when several people call at once - and outside opening hours, following the route your practice defines.
Recurring requests arrive structured instead of being scattered across calls, notes and callbacks.
Your team can focus on people at reception and patients in the practice, complex conversations and work that genuinely needs human attention.
Control & Safety
Your practice determines what Lebi asks, what information it collects, what happens next and when a member of your team should take over.
Questions and information
Define what Lebi asks for each workflow.
Routing and recipients
Decide where different requests should be routed.
Opening hours and exceptions
Configure different routes based on time, situation or request.
Human handover
Decide when Lebi should stop and your team should take over.
Tasks
Lebi handles administrative requests. Medical judgement stays with your team.
No medical advice
Lebi does not advise patients on diagnosis or treatment.
No urgency decisions
Lebi does not assess symptoms or decide how urgently someone needs care.
No guessing
Anything outside the configured workflow follows the fallback or handover your practice has defined.
Handover rules
Your practice remains the controller. Lebi processes patient data only for the workflows you configure.
Patient data stays in the EEA
Processed in the EEA for the entire conversation path.
Audio is not stored
Calls are not stored as audio. Conversations are transcribed so your practice can review each request.
Transparent AI
Patients are told at the start of every conversation that they are speaking with an AI assistant.
Documented processing
We provide a data processing agreement and the product-side documentation your practice needs to document processing.
Data
Built with practices
Every practice works differently. Lebi can be configured around the workflows and recurring patient communication that matters in yours.

Appointments, prescription requests, predefined question lists - for example collecting the standard information for a urine test drop-off, callbacks and recurring administrative questions.

Appointments, rescheduling, recalls, new-patient requests and standard practice questions.

New-patient enquiries, predefined intake information and appointment requests while therapists stay focused on treatment.

Psychotherapy-, veterinary practices and other outpatient care where recurring patient communication can follow clearly defined workflows and handover rules.
Shaped around real practice workflows
Lebi is being built and used together with healthcare practices in Germany and the Netherlands. We configure the product around real workflows, exceptions and the way patient communication actually happens day to day.
Who are we
Our team has spent significant time in and with practices to understand the real needs. This has helped shape the product. We have also set up a practice advisory board consisting of GPs and dentists across Germany and the Netherlands who help shape the product.
Show us how your practice handles recurring patient calls today.
We'll show you where Lebi can reduce phone pressure, help more patients get through and fit into your existing workflows. No commitment. We'll show Lebi using workflows from a practice like yours.

We're here for you. Questions before or after the demo?
Reach out and a real person will get back to you.
FAQ
What Lebi does, what your practice controls and where the boundaries are.
Yes - and they will always know it. Lebi clearly states at the start of every conversation that it is an AI assistant. Anything complex or unclear is handed to your team.
No. Lebi does not assess symptoms, does not determine urgency and uses no clinical logic. Anything complex or unclear is handed to your team.
Lebi does not assess the medical situation. It follows only the paths your practice defines - such as a direct handoff to your team or a fixed message pointing to emergency services or 116117.
Lebi does not guess. The conversation is handed to your practice team by your rules or captured as a callback request.
No. Lebi handles recurring administrative calls so your team has more time for patients on site and complex requests. Your team always stays in control.
No. Lebi works with your existing phone system. We map your current call path and choose the right setup together.
Lebi works from day one without integrations: it answers calls, structures each request and routes it to the right person. Integrations with practice systems add further benefits and are built together with the practices we work with, prioritised by operational need. We only call a system integrated when the integration actually works.
Yes, where possible. Lebi follows your practice's appointment rules and books suitable slots automatically; where automatic booking is not possible it creates a structured appointment request for your team. You decide which appointment types Lebi may book.
Audio is never stored. Patient data is processed in the EEA for the entire conversation path. Your practice remains the controller, and we provide a data processing agreement and the product-side documentation your practice needs to document processing.
Conversations are not recorded, but they are transcribed. Your practice can view full transcripts and structured summaries of requests and keeps control of the configuration.
Yes, fully. You start from specialty templates and adapt wording, questions, routing, recipients and handoffs. Opening hours, breaks, public holidays, leave and cover each get their own rule and route.
Technically Lebi can handle first conversations within minutes. A good start matters more: we begin with a focused working session on your current workflows and handoffs, and your team's time investment is typically a few hours. End to end, going live usually takes a few days depending on your setup.
Lebi currently speaks German, Dutch and English. Further languages are being added. We confirm in the demo which languages are available for your practice.
In practice, even sceptical people prefer speaking with AI to waiting a long time or not being served at all. You can roll out gradually - outside opening hours first, for example - and where possible patients keep the choice of whether to speak with Lebi.
We discuss pricing in a demo, based on the workflows and setup your practice needs. We do not currently publish packages or amounts.
Still have questions?
Contact usSupported by
