All client work
Case study 06 · AI voice agent · Retell AI · GPT-4.1 · Make · GoHighLevel calendar

A bilingual voice agent that books the class

The same Barcelona Pilates studio wanted its phone line answered like its DMs. We built Sophie, an inbound voice agent on the studio's Spanish number: she explains the classes, collects and spells back the caller's details, checks the live calendar, offers another slot if the first is taken, and books the free assessment.

Live on a Spanish phone lineSpanish and EnglishReal-time availability checkPost-call data extraction
2
languages, matched to the caller
0.8-1.3 s
model latency
$0.14
per minute to run
5
fields extracted after every call
Client
Pilates studio, Barcelona (name withheld), via a Spanish marketing agency
Our role
AI engineer: Retell voice agent, booking function and GoHighLevel calendar
Timeline
January to March 2025
Stack
Retell AI · GPT-4.1 · Make · Airtable · GoHighLevel calendar
How a call works

From hello to booked, in about two minutes

The prompt is built around one goal, a booked free assessment, with a fixed order so the agent never checks the calendar before it has a name and an email it trusts.

01
Greet
Answers in the caller's language, Spanish or English.
02
Understand
Pilates, functional training or both.
03
Collect
Full name and email, spelled back letter by letter.
04
Check slot
A custom function checks the live calendar through Make.
05
Offer
If the time is taken, two nearby slots to choose from.
06
Book
Confirms date and time; a confirmation email follows.
Retell AI · Agent

One prompt, one tool, one goal

A single-prompt agent on GPT-4.1 with a native Spanish voice. One custom function does the real work: it posts the requested time to a Make webhook, which checks and books the GoHighLevel calendar and returns open slots.

Retell agent configuration with role, objectives and booking rules
Sophie in Retell (studio name hidden)
Accuracy

Spell it back

Emails are read back letter by letter before the domain, the most common place voice bookings go wrong.

Objections

Budget and time handled

The free assessment answers price worries; evening and weekend slots answer schedule ones.

Errors

Fails out loud, politely

If the calendar check fails, she says so and rechecks the details instead of guessing.

Make · Under the hood

Two scenarios behind the voice

During the call, checkAvailability hits the booking scenario: OpenAI turns the spoken time into a timestamp, the caller is found or created in GoHighLevel, and the slot is booked or two alternatives come back. When the call ends, a second scenario logs it to Airtable and updates the contact.

Make scenario for the checkAvailability function: format the time, find or create the contact, book or return open slots
checkAvailability: format the time, find or create the contact, book on the calendar, or return open slots
Make end-of-call scenario: duration and cost logged to Airtable, contact updated, returning callers recognised
End of call: duration and cost logged, contact updated; returning callers recognised at call start
A real booking

Slot taken. Booked anyway.

A call on the live line: the first time asked for was taken, so she offered two others, the caller picked a different day, and the booking went through in 2 minutes 15 seconds. After every call Retell extracts the caller's name, email, reason for calling, chosen time and whether a booking was made.

Retell post-call analysis with extracted fields, personal data hidden
Post-call analysis (phone, email and name hidden)
Outcome

Every call ends as data

Live on the studio's Spanish phone line. Callers get answers and a booked assessment without waiting for staff, and the studio sees outcomes, not just recordings.

$0.14
per minute, voice and model included
2:15
from hello to booked on the call shown
5
fields extracted after every call
2
languages, matched to the caller
Stack

Retell · GPT-4.1 · Make · Airtable · GoHighLevel

Custom function, post-call extraction and logging, calendar booking and confirmation email.

Design

Confirm before you book

The calendar is only queried once the name and email are confirmed.

Pair

Same studio as the chat agent

Built alongside the DM agent in case study 05, so phone and chat book the same way.

What we would tell you

Three things we learned

01
Order the steps, not just the words.
A fixed sequence stops the agent booking against a misheard email.
02
Always have a second slot ready.
Offering alternatives is what turns a taken time into a booking.
03
Extract structured data from every call.
A transcript nobody reads is worth less than five clean fields.

The full case study as a PDF

The full write-up with the screenshots above, formatted for printing or forwarding. Client details are hidden in the PDF too.

Download the PDF

Missing calls, or answering the same booking questions all day?

Tell us what you are trying to automate or move. We will say what fits, what does not, and what it would cost.

Book a free 15-minute call
More case studies
Case study 01
Outbound WhatsApp AI agent for a real-estate agency
15 n8n workflows in production · 11 WhatsApp templates approved by Meta · 9 Postgres tables on Supabase · 0.8% failure rate across all workflows
Case study 02
Keap to GoHighLevel migration for Fresh Start Health Retreat
8,000+ contacts deduplicated and cleaned · 45,750 logged API calls, 0 rate limits · 4 wks from hire to Keap switched off · 5.0 Upwork review plus a video testimonial
Case study 03
Landing page rebuild in the GoHighLevel funnel builder
2 program pages rebuilt, two brands · 4 funnel steps each, call to booking · 3 custom code blocks, all documented · 7 wks from scope to owner sign-off
Case study 04
GoHighLevel agency build for an energy-sector marketing agency
1,592 newsletter sign-ups processed · 8 sub-accounts in one agency · 7 lead automations for a contractor · 5.0 review from the agency that brought us in
Case study 05
AI chat agent on WhatsApp and Instagram for a Pilates studio
3,279 conversations handled · 2,644 AI replies delivered · 465 message bursts batched into one reply · 3 studio locations routed automatically
Case study 07
Multi-agent AI voice system on Retell, n8n, Supabase and GoHighLevel
46+ client sub-accounts on one build · 1.49M+ records behind the system · 5 min from a dropped call to an AI callback · 10 call outcome categories
Case study 08
AI front desk GoHighLevel snapshot a US platform resells to home-service businesses
26 workflows live on the first client · ~1 hr to deploy the next client · 25 s from missed call to text-back · 1st attempt: A2P approved
Book a free callhello@olventra.comWhatsApp usHire us on Upwork