How Aria books appointments
The booking flow, end to end
When a caller says they want to book an appointment, Aria walks through a predictable sequence:
1. **Identify the service.** Aria asks what the caller is looking for and matches it to one of the services in your knowledge base. If the caller describes something unclear, Aria asks a clarifying question.
2. **Check availability.** Aria calls Cal.com's API in real time to find open slots that match the service and the caller's preferred timing.
3. **Offer specific options.** Aria offers two or three concrete times rather than an open-ended "when works for you?" — offering specific slots dramatically improves booking completion rates.
4. **Confirm the details.** Once the caller picks a slot, Aria reads back the date, time, and service to confirm before booking.
5. **Book it.** Aria creates the booking through Cal.com, which writes to your connected primary calendar (Google Calendar, Outlook, or whichever calendar Cal.com is connected to).
6. **Capture the caller details.** Aria collects the caller's name and phone number (and email if the caller offers it). These go into the contact record alongside the booking.
7. **Confirm verbally.** Aria tells the caller the booking is confirmed and mentions what happens next (confirmation SMS, what to bring, where to park).
The whole flow typically takes 60 to 90 seconds on a call where the caller knows what they want. For callers who need more help deciding, Aria can spend as long as needed in the knowledge-base phase before moving to booking.
Preventing double-booking
Real-time double-booking prevention is handled by Cal.com, not by Receptionist.co directly. When Cal.com checks availability, it reads your primary calendar (the one you connected inside Cal.com — typically Google Calendar or Outlook). Any existing event on that primary calendar, whether it was created by Aria, by you manually, or by another system, automatically blocks that time slot.
This is why the setup instructions in Getting Started emphasize connecting your primary calendar *inside Cal.com* rather than separately inside Receptionist.co. Going through Cal.com means there is exactly one authoritative source of availability, and the answer is always current.
If you have a personal appointment on your calendar for Thursday at 2 PM, Cal.com returns "2 PM is not available" when Aria checks. Aria offers other slots instead. You never have to worry about Aria booking on top of something you already had scheduled.
When Aria cannot book
There are a few situations where Aria cannot complete a booking during the call:
In all of these cases, the call still creates a contact record and a transcript, so you have everything you need to follow up.
The caller experience
From the caller's side, the booking experience feels like talking to a competent human receptionist. Aria does not pause awkwardly while she "checks availability" — the Cal.com API responds in under a second, so the check is invisible. She does not read back a disclaimer before booking. She does not try to upsell. She books the appointment, confirms the details, and wraps up the call.
The only noticeable AI moment is the opening disclosure ("This is Aria, an AI assistant on a recorded line") at the start of the call. After that, the rest of the interaction is a natural back-and-forth conversation — not a scripted prompt tree and not a form being filled out.