Case study · Healthcare · Hearing care
Every ad lead gets a live phone call within minutes
A hearing aid center was paying for Facebook leads, but its prospects (mostly older adults with hearing loss) rarely answered texts. I connected GoHighLevel to a Vapi AI voice assistant that calls the front desk, introduces the new lead and transfers the call to them, so a person talks to every lead straight away.
The call path
From form submit to a live conversation
Texting doesn't work well for this audience, and a call does. The workflow handles the dialing so front-desk staff only have to pick up and talk.
Lead submits form
Facebook Lead Form on the clinic's page fires the workflow.
t = 0Team alerted
Slack alert, tag, and an opportunity in the audiology pipeline.
secondsAI calls front desk
Vapi rings the clinic and tells staff who the new lead is.
drip: 1 per 2 minCall transferred
The assistant connects staff straight to the lead's phone.
live conversationLogged
Formatted lead sent to Google Sheets, then an email notification.
+1 min
System 1 · Capture
Instant lead capture
Leads came in at random times and waited until someone noticed them.
- Any lead form on the clinic's page triggers the workflow.
- A Slack alert goes to the team, the lead is tagged, and an opportunity is created in the Audiology Pipeline: New Lead → Consultation Booked → No-Show → Nurture → Fitted.
- Drip mode releases one lead every 2 minutes, so a burst of leads never floods the front desk with calls.
- The earlier SMS follow-up steps are still in place but disabled, ready to switch back on.
System 2 · Voice AI
AI voice call-connect with Vapi
The front desk couldn't call every lead quickly enough while also looking after patients in the clinic.
- A custom webhook sends a
POSTtoapi.vapi.ai/call, authenticated with a stored API key. - The Vapi assistant gets the lead's details as variables:
patientNameandtransferNumber. - It calls the clinic's front desk, says who the new lead is, then transfers the call to the lead.
- Staff never dial a number or copy details from a notification. They just answer and start talking.
System 3 · Logging
Every lead logged in Google Sheets
There was no simple shared record of which leads came in and which were reached.
- GHL's number formatter normalizes the phone number first.
- Name, phone and email are posted to a Google Apps Script endpoint that adds a row to the clinic's lead sheet.
- The script's response is saved back into GHL for later steps.
- After a one-minute wait, an email notification finishes the hand-off.
System 4 · Retries
Missed leads get called again
If a lead didn't pick up, they used to drop out of follow-up.
- Leads that weren't reached go into a retry queue.
- Two drip gates (9 a day and 1 every 45 minutes) spread retries across the business day.
- Each lead is sent back into the AI call-connect workflow for another live call.
How it's built
Tools and design choices
Use the channel the audience answers
For older patients with hearing loss, a live phone call works better than a text.
Staff only have to answer
The AI handles dialing, context and the transfer. A person handles the conversation.
A pace the clinic can handle
Drip gates keep calls and retries at a level the front desk can manage.
One record everywhere
Slack, the pipeline and the Google Sheet all show the same lead.