AI appointment setter
A platform to build an AI appointment setter that answers the phone
An AI appointment setter on the phone needs three things from its platform: it answers on your own number, reads and writes appointments in the calendar or booking system you already use while the caller is on the line, and hands over to a person when a request does not fit. VoiceDock gives you that layer. Your booking system stays the source of truth, and the assistant reaches it through webhook tools to your own API or through your own MCP server. It can also call out to confirm or remind. Agencies, software companies, telecom providers and businesses with their own developers build on it, and we build it with them.
Book, move, cancel and confirm · your own calendar or booking system · € 0,07/min orchestration · EU-hosted platform layer
Who builds on it
Teams that put booking on the phone
The booking logic stays theirs. VoiceDock handles the phone line, the conversation and the calls into their systems.
Software companies with a booking product
If your product already holds the calendar, a phone assistant on top of it lets your customers' callers book without staff picking up. Under your own brand with white-label voice AI; the partner page is where to start.
Agencies building for appointment-based businesses
You build the booking flow per client, on that client's own booking system, and keep the client relationship. How agencies work with us.
Telecom and VoIP providers
Add an appointment assistant to the lines you already serve, over your own SIP trunk, with an organisation and a price per customer. Telecom and VoIP providers.
Businesses with their own developers
Your developers connect the assistant to your booking system through its API and keep ownership of the rules. The developer page covers the API, the SDK and our MCP server.
How a booking call runs
From the question to a confirmed appointment
Every step that touches your agenda is a tool call to your own system. The assistant asks, your system decides.
- 01
The caller asks for an appointment
The assistant answers on your own number. If your server returns context through the assistant-request webhook before pickup, a returning customer does not have to spell out their name. Recognising the caller. - 02
The assistant checks availability in your system
A tool such as check_availability calls your endpoint with the date range and the service. Your system answers with open slots. A synchronous tool call has to answer within ten seconds, so return a few concrete options rather than the whole calendar. Tool calls on a live phone line. - 03
It proposes, the caller chooses
The assistant offers two or three slots in plain language and checks the one the caller picks: day, time, service and name. - 04
It books, moves or cancels
A second tool writes the appointment in your system and returns a confirmation. Moving and cancelling work the same way, each with a tool you define. Custom tools. - 05
It confirms, or hands over
The caller hears the booked appointment read back. When a request does not fit, such as an urgent case or a special arrangement, the assistant transfers to a colleague. - 06
Confirmations and reminders by phone
For a confirmation call, start an outbound call through the API with the appointment details, or run a campaign over a list. On outbound calls, voicemail detection can leave a message or hang up. Outbound calls run from your own number; managed numbers are inbound only.
What you set up
Five things to have in place
Most of the work sits in the connection to your booking system. The rest is configuration.
| Part | How it works on VoiceDock |
|---|---|
| Your booking system's API | The calendar or booking system stays where it is. The assistant reaches it through your own API, a webhook endpoint you host, or your own MCP server. How a connection is built. |
| Tools for availability and booking | One tool per action: check availability, book, move, cancel. Each gets a clear description so the model knows when to use it. With your own MCP server, allowed_tools lists the tools the assistant may call. |
| Rules for what it may book | Lead times, services that need a person, checks against double bookings. Enforce these in your own system and not only in the prompt: your endpoint can refuse a slot and say why. |
| Phone number | Your own number over a SIP trunk, for inbound and outbound calls. A managed number for testing is available on request, inbound only. Phone numbers. |
| Follow-up | The end-of-call report with a summary, and call analysis fields such as whether an appointment was booked, so your team sees the outcome without listening back. |
Before you go live
Decisions that make or break phone booking
Booking by phone fails on details. Settle these before real callers do it for you.
Which system decides what is free
Let your booking system decide. The assistant asks and writes; it does not keep its own copy of the calendar. That way a booking made at the front desk and one made by phone never collide.
What it says when your system does not answer
A booking system can be slow or down. Decide what the assistant does then: take the request and promise a callback, or transfer to a person. Handing over when something fails.
Reading the booking back
Dates and names are where phone bookings go wrong. Have the assistant repeat day, date and time before it books, and let your system return the stored slot so the assistant reads back what was actually saved. The wait while it checks is part of the latency budget of a phone call.
What a minute costs
Orchestration is € 0,07 per minute, model usage is at cost or on your own keys, and telephony is billed per leg. Our pricing page lists the rates, and what a voice agent costs per minute explains the meters.
Related
Read next
FAQ
Questions about an AI appointment setter
What is the best platform to build an AI appointment setter that answers the phone?
One that answers on a real phone number, books in your existing calendar or booking system during the call instead of in a separate agenda, and transfers to a person when a booking does not fit. VoiceDock is built for that: tools to your own API or MCP server, warm and cold transfer, outbound calls for confirmations, and published pricing. If you are comparing, our pages on Vapi, Retell AI, Bland AI and Synthflow set them next to VoiceDock.
Does it work with our calendar?
If your calendar or booking system has an API, yes. The assistant reaches it through webhook tools to your own endpoint or through an MCP server you run. VoiceDock does not ship a fixed list of calendar connectors; the connection is built for your system, together with us if you want. How that is built.
Can it reschedule and cancel, not only book?
Yes, with a tool for each action. The assistant picks the right one from the conversation, and your system carries it out. Custom tools shows the format.
Can it call customers to confirm or remind them?
Yes. Start an outbound call through the API with the appointment details, or schedule a campaign. Outbound calls run from your own number. See outbound calls and campaigns in the docs.
What if the caller wants something the assistant cannot book?
It transfers the call to a colleague. In monitored mode it waits until someone answers and stays with the caller if nobody does. Warm transfer.
Can we offer this to our own customers under our brand?
Yes, through white-label, which is arranged with us. Telecom and VoIP providers and chatbot platforms have pages of their own.
Where is the booking data processed?
The appointments stay in your own booking system. The call itself runs through orchestration, dashboard, API and storage on EU infrastructure, and hosting and sub-processors are listed in the Trust Center.
Connect your booking system with us
Plan a call to go through your booking system's API and the rules for what the assistant may book, or create an account and test on prepaid credit. The AI receptionist page covers the rest of the phone line.