DEV Community

VoiceFleet
VoiceFleet

Posted on • Originally published at voicefleet.ai

Building an AI Phone System for Medical Clinics — What We Learned

Monday morning, 8:01 AM. Twelve patients call a GP clinic simultaneously. Two receptionists. Ten callers hear a busy tone or wait 6+ minutes. Three hang up and try another clinic.

This is a daily reality across Ireland (and probably wherever you are). We've been building AI phone answering at VoiceFleet and medical clinics turned out to be one of the most interesting — and challenging — verticals.

The Technical Problem

Medical clinic phone traffic has a brutal pattern:

  • 8:00–9:30 AM: 40–60% of calls missed or abandoned
  • 12:30–2:00 PM: Lunch cover gap → voicemail
  • After 5:00 PM: Closed, no coverage
  • Mondays: Up to 50% call abandonment

This isn't a staffing problem you can solve with more receptionists. The spikes are too sharp and too short. You'd need 6 staff for the 8AM rush and 1 for the rest of the day.

What the AI Handles

The interesting engineering challenges:

Prescription Repeats (25–35% of all calls)

"I need a refill on my blood pressure medication." This is the low-hanging fruit — identity confirmation, medication lookup, logging the request, telling the patient when to collect. Automating this alone cuts phone volume by a third.

Appointment Booking

Real-time calendar integration. Same-day urgency detection. New patient registration with PPS number collection. Cancellations that automatically open slots.

Urgent Call Triage

This is the hard one. The system needs medical urgency protocols — chest pain, breathing difficulty, signs of stroke need immediate routing to a clinician. Getting the triage logic right is critical because the stakes are literally life and death.

Test Results

"Are my blood results back?" — Check status, schedule doctor callback if ready, give expected timeline if pending, route abnormal results directly to GP.

What Surprised Us

  1. Prescription refills are the killer feature. We expected appointment booking to be the main draw. Turns out reducing "can I get a refill" calls by 90% is what clinicians care about most.

  2. Patient trust is higher than expected. We assumed older patients would resist AI. In practice, they prefer getting an immediate answer to waiting on hold for 8 minutes.

  3. GDPR compliance is table stakes, not a differentiator. Every medical practice asks about it. None of them will proceed without it. It's just a checkbox.

  4. Multi-language is a real need in Ireland. Polish, Portuguese, Mandarin — Dublin GP clinics serve diverse populations and phone support in those languages was previously impossible without multilingual staff.

The Stack

We use conversational AI (not IVR/phone trees) with real-time scheduling integration. Irish phone numbers, EU data processing, natural accent options. Starts at €99/month.

If you're building in healthtech or dealing with similar call-routing problems, happy to share more about the triage logic and scheduling integration.

Live demo here if you want to hear how the conversation sounds.


What's the hardest part of building phone/voice AI in your experience? Triage? Integration? User trust?

Top comments (0)