If a caller wants to book time with your business, the useful version of an AI receptionist doesn't just take a message and promise a callback. It offers real times, writes the appointment into your calendar while the caller is still on the line, and reads the details back so both sides leave the call knowing what was booked. That's how AlmaTalk handles inbound booking. Here's exactly how it works, and where the honest limits are.
What "books during the call" actually means
When a caller asks for an appointment, the agent looks at your availability and offers open times. When the caller picks one, it creates the event and adds it to your calendar before the call ends. AlmaTalk writes to Google Calendar, Outlook, or Cal.com, so the booking shows up in the same calendar your team already lives in — no separate app to check.
The agent answers 24/7, so a booking can happen at 11 p.m. on a Sunday without anyone on your side lifting a finger. The caller hears a confirmation spoken back to them, and the event lands in your calendar with the details captured on the call.
It respects your working hours
The agent won't offer a Tuesday at 2 a.m. or a slot on a day you're closed. It books against the working hours you set, so the times it offers are times you'd actually take.
It can book per-staff, not just "the business"
If different people handle different work, AlmaTalk supports per-staff schedules, so the agent offers times that fit the right person's calendar rather than a single shared one. You can also configure service routing so a given service type is auto-assigned to the person who handles it — this is opt-in, so you turn it on and set the rules when it fits how you operate. Configured well, a caller asking for one type of appointment is booked with the right staff member without having to know anyone's name.
Rescheduling and cancelling by phone
Booking is only half of it. Callers change plans, and AlmaTalk can confirm, reschedule, or cancel an existing appointment over the phone. Before it touches anything, it verifies the caller's number — a simple guard so someone can't move or cancel a booking that isn't theirs. Once verified, the change is made against the same calendar the booking lives in.
This matters because reschedules are where a lot of front-desk time goes, and they usually happen after hours or during your busiest stretch. Handling them automatically, with a verification step in front, keeps your calendar accurate without a person mediating every change.
The honest part: inbound calendar checks refresh on a schedule
Here's the caveat worth understanding before you rely on this. AlmaTalk writes bookings to your calendar promptly, but its view of what's already on your external calendar refreshes on a schedule — roughly every half hour — not the instant something changes. It is not a real-time mirror of your calendar.
In practice this rarely bites, because the agent's own bookings are tracked as it makes them. The edge case is an event someone adds directly to Google Calendar or Outlook a few minutes before a caller phones in: the agent may not have picked it up yet and could offer that slot. If your team frequently blocks time by hand right before it fills, leave a small buffer, or add those blocks a little ahead. For the normal flow — the agent booking, confirming, and rescheduling — the calendar stays consistent.
What the caller experiences
Booking is one part of a call, not the whole thing. A few AlmaTalk capabilities make the booking feel less robotic:
- Bilingual EN/FR. The agent can start bilingual, and you can configure it to detect the caller's language and continue in it, with a distinct voice per language. This is opt-in per agent.
- Returning-caller recognition. It can recognize a repeat caller by their number and greet them by name in the language they last used, so a rebooking doesn't start from zero.
- Escalation with context. If a call needs a person, the agent can transfer to someone and hand off the context, rather than making the caller repeat themselves.
- Reminders and follow-ups. After a booking, AlmaTalk can send appointment reminders in your timezone and language on the channel you choose, and run multi-step follow-up sequences — which is where a lot of no-shows quietly disappear.
After the call
Each call produces a post-call summary. Caller memory — name, topics, follow-ups — is captured after the call from the transcript, not mid-call, and stored on our servers with configurable retention. Calls can also be auto-tagged against your own service categories and urgency levels, again after the call, so your booking history is organized the way your business thinks about work. Call recording and transcript storage can be turned off per agent, and a spoken "this call may be recorded" disclosure can be enabled if you want it (it's off by default).
What it costs, plainly
AlmaTalk billing has two parts: a monthly or yearly plan that includes a set credit allowance, plus usage metered in credits (call time is metered in seconds, with a minimum of one credit per call). Paid plans have overage enabled by default, so calls beyond your allowance keep working and are billed as usage. Everything is charged in CAD, and there's no setup fee.
Getting started
You can have AlmaTalk build a draft agent from your own website, then review it before it goes live — so the first version already knows your services and hours. Connect Google Calendar, Outlook, or Cal.com, set your working hours and per-staff schedules, decide whether to turn on language detection and service routing, and test it with a call to yourself. Once it's answering, it books, reschedules, and reminds — day or night — while your calendar stays the single source of truth.