The voice assistant that answers your patient line and checks appointments through a permissioned HIS connection
For patient services and contact center teams: the assistant takes repetitive booking and information calls, so your team can focus on the calls that need a person.
Common problems on the phone line
Busy lines at peak hours
Appointment calls bunch up at the same times of day; callers wait in the queue or hang up and call again.
The same questions every day
Questions about departments, doctors, directions and opening hours fill the team's day with repeated answers.
After-hours calls go unanswered
Appointment requests that come in outside working hours wait until the next day or are never recorded.
How it works in this sector
Every call follows the same four steps; the assistant acts only with defined permissions.
- 01 / 04
Greets
Greets the caller and listens to the department and appointment request.
- 02 / 04
Understands and verifies
Verifies identity with the details your organization defines.
- 03 / 04
Takes action
Checks available slots through the permissioned HIS connection.
- 04 / 04
Confirms or hands off
Asks the caller to confirm the choice; hands medical questions and emergencies to the team.
What the assistant takes on
Supports appointments and call routing through permissioned hospital system connections.
- Department and doctor information
- Available appointment slots
- Reminders and operator handoff
- Appointment confirmation after identity verification
- Call summary written to the record
Example call
A fictional scenario: what the caller says, what the assistant understands and how it replies.
- Caller
- “I would like a cardiology appointment tomorrow afternoon.”
- Detected request
- Appointment request · Cardiology · Tomorrow afternoon
- Assistant response
- After identity verification, I can check available slots. You must confirm your choice before an appointment is created.
Healthcare scenarios are administrative only, not diagnosis or treatment. Emergencies follow the institution's routing procedure.
Illustrative example · Not live system data
Related integrations
The assistant connects to your systems only with defined permissions; your PBX setup is reviewed during discovery.
HIS · CRM
API access only with defined permissions
Inbound and outbound calls
Answering, information and confirmation calls
Operator handoff
Calls that need a person, plus fallback routing
Call summary to the CRM
The call summary is written to the relevant record
Runs on your own server
- Your data stays in-house.
- A single GPU server is enough.
- Several calls at the same time, on the same system.
The architecture supports your compliance processes with restricted API access, configurable retention and operator fallback. Compliance depends on the deployment configuration, data processing practices and your organizational procedures.
The path of a call
- 01Phone lineNetgsm 0850 · SIP Trunk
- 02PBXAsterisk
- 03Your serverSTT → LLM → TTS
- 04Your systemsHIS · CRM
Frequently asked questions
- Does the assistant answer medical questions?
- No. Healthcare scenarios are administrative only; no diagnosis or treatment advice is given. When a medical question comes up, the call is handed to the relevant team.
- Which hospital systems does it connect to?
- The assistant connects to your HIS and CRM through APIs, only with the permissions your organization defines. Connection details are agreed during discovery.
- Does voice data leave the organization?
- No. Speech-to-text, response generation and speech synthesis run on your own server; your data stays in-house. Calls arrive through your telephone carrier and PBX.
- What if the agent can't resolve a request?
- Calls that need a person are transferred to an operator, with fallback routing in place.
Request a demo
Your sector is preselected in the form. Briefly describe your call scenario, and we will schedule an online meeting at a time that suits you.
Let's plan your phone line together
In a discovery call we go through your call flows and the systems to connect.
* Footnote: Latency values were measured on real call recordings (from the moment the caller stops speaking until the first sound arrives, server side). Internet latency adds 0.05–0.3 s. Word error rate was measured on the public FLEURS-tr dataset (200 sentences, 8 kHz telephone audio). Language support is at model level. Live validation was done in Turkish; in other languages, voice and recognition quality may vary by language.