The short answer
Use the hospital information system (HIS) to create a reminder job when an appointment is booked. Before calling, recheck the appointment and contact permissions. A voice agent handles confirmation; a validated call result returns to the same HIS record. Staff handle changes, uncertainty and failed calls.
The connected workflow
Reference design · Proposed steps to validate in a pilot, not a deployed customer case study.
- Appointment booked · HIS
Save the appointment ID, version, scheduled time and contact preference in a reminder job.
- Reminder due · n8n
Re-read the live appointment. Stop if it was cancelled, changed or is no longer eligible for a call.
- Call starts · voice agent
Use minimal approved context, identify the AI assistant and follow the hospital’s identity-check process.
- Response captured · agent
Separate confirmed attendance, a change request, a wrong number and an unclear response.
- Result validated · backend
Verify the callback, match the conversation to its job and reject duplicate or stale updates.
- Record updated · HIS
Save the permitted outcome. Give reception a task whenever a person must resolve the request.
What each tool does
- Hospital information system
- The source of truth for appointments, contact permissions and final booking status. Its vendor must provide an approved integration route.
- n8n + durable job storage
- Receive booking events, schedule eligible reminders, track attempts and coordinate updates through an approved API adapter.
- ElevenLabs + telephony
- Configure the bounded conversation and connect a supported phone provider, such as Twilio. Validate language and country availability.
- Reception task queue
- Give staff ownership of rescheduling requests, unclear responses and integration failures.
Check the HIS first
An HIS is a hospital information system. Ask its vendor about appointment events, supported read/write APIs, authentication and a test environment. Identify who approves access and which fields can be changed. If only scheduled exports are available, explain the delay and recheck availability before each call. Do not promise a direct integration with every HIS or write into an undocumented production database.
Book now, remind later
A booking event should create a future reminder job. It should not automatically place an immediate call unless that is the agreed confirmation flow. Store the appointment time with its timezone and choose the reminder window with the hospital. Rebooking or cancellation invalidates the old job. Claim each due job once so overlapping workers cannot place duplicate calls.
Prepare approved answers
Use a reviewed ElevenLabs knowledge base for stable administrative information: opening hours, directions and how to reach reception. Keep patient records out of the shared knowledge base. Provide appointment-specific context only for the authorised conversation. Configure the agent to avoid diagnosis, treatment advice or interpreting symptoms; those conversations go to the hospital’s established human route.
Start a controlled call
The ElevenLabs outbound calls through Twilio accepts an agent, connected phone number and destination. Pass only the context needed for this job; the ElevenLabs dynamic variables explains per-conversation fields. Before sending, recheck the appointment, allowed calling time and contact preference. Store the returned conversation reference against the job. If a request times out after submission, reconcile its status before retrying; an immediate blind retry could call twice.
Return the result safely
The ElevenLabs post-call webhooks describes callbacks after analysis and HMAC signature validation. Verify the signature against the raw body, durably store the event and deduplicate it before processing. Distinguish call delivery from appointment confirmation. Map permitted outcomes to the HIS, keep an audit reference and route uncertain summaries for staff review. A completed phone call alone must never mark attendance confirmed.
Keep booking changes explicit
For a first pilot, record “reschedule requested” and let reception complete the change. If a later version can rebook directly, expose a narrowly scoped tool that checks live availability, confirms the choice with the patient and writes through the approved HIS interface. Announce a new booking only after that write succeeds. Reject stale results from a call about an older appointment version.
Protect patient information
Use synthetic data during development. Before real patient calls, the hospital must approve identity checks, recording choices, data retention, access and applicable healthcare and calling requirements for every processor. The ElevenLabs healthcare configuration requirements is one vendor’s configuration guidance, not proof that an entire workflow is compliant. If someone else answers or voicemail picks up, avoid revealing appointment details and follow the hospital’s approved script.
Handle missed connections
A no-answer result, a failed call and an unclear reply are separate outcomes. Define a limited retry schedule, a stop condition and a staff owner. Opt-outs and wrong numbers stop further automated calls. If the HIS write fails after a successful conversation, retain the result for retry and alert reception; do not restart the call to repair a database update.
Improve the knowledge
Group unanswered administrative questions for review. A hospital owner can write and approve a reusable answer, publish it to the knowledge base and run the affected tests again. Patient details and raw transcripts stay in their authorised records with their retention rules. They are not automatically added as shared knowledge or treated as model training material.
Prove the pilot
Test a normal confirmation, a changed appointment, duplicate booking events, a wrong number, voicemail, an interrupted call and an unavailable HIS. Also replay a signed callback twice and confirm that it produces one update. Measure eligible reminders, answered calls, validated confirmations, manual follow-ups and failed writes separately. Do not claim a reduction in missed appointments until a measured pilot supports it.
Common questions
Can the agent call as soon as an appointment is booked?
Yes, an immediate confirmation call can be designed if appropriate and authorised. A reminder is usually scheduled closer to the appointment, with eligibility checked again before dialling. These are separate triggers.
Does every call train the agent?
No. Call outcomes update the appointment record. Reusable answers should enter a review process before the knowledge base changes. A transcript is not automatically suitable training material.
Sources & scope
Provider documentation checked on 20 October 2026. The workflow is our proposed implementation design; platform features, plans and integrations must be confirmed for your project.
Your next step
Send the name of your HIS, the appointment process and required languages—without patient data. We can check integration feasibility and scope a controlled reminder pilot.
Explore the related solution