What a booking agent does
A booking agent holds the conversation that a receptionist holds now. It checks the service and the specialist, offers free time, books the visit, confirms it the day before and sends a reminder on the day of the appointment.
If a client wants to move or cancel a visit, the agent finds a new slot and frees the old one. An unusual request goes to the receptionist together with the history of the conversation.
The channels are the same ones where clients write and call now: Telegram, other messengers, the website chat, the phone. The agent covers text channels with one logic, while calls need speech recognition and a phone system; that is a separate build, described on the page about the voice agent.
Such an agent often needs no knowledge base: prices, the address and preparation rules fit into the instruction, and it takes slots from the calendar. Why this is so is covered on the page about an agent without a knowledge base.
We build such an agent turnkey for clinics, car service centers and salons, and the service is described on the page of the AI receptionist for client booking. In the pilot, the metric in the contract is the share of bookings made without the receptionist and the number of missed requests.
Connecting the calendar
For a no-code build, n8n fits: an automation platform with AI agents. Its license is the Sustainable Use License (fair-code): you can install n8n on your own server and change it, but you cannot resell it as a cloud service. How to build an agent on n8n from scratch is covered in a separate guide.
The calendar connects like this, according to the n8n documentation:
1. Add an AI Agent node and connect a model to it. The agent works only if at least one tool is connected to it.
2. Connect a Google Calendar node to the agent as a tool with the “Availability” operation: it checks whether a slot in the calendar is free.
3. Add a second Google Calendar tool with the “Create” operation (add an event): this is how the agent books a client.
4. For reschedules and cancellations, connect the “Update” (change an event) and “Delete” (remove an event) operations, and to find a client’s booking, the “Get Many” operation (all calendar events).
5. In the agent’s instruction, describe the rules: the length of services, breaks, which details to ask the client for and when to call the receptionist.
Before launch, test the agent on hard cases: a client asks for a time that is already taken, wants to book two specialists in a row, or writes “same as last time”. Check the bookings the agent made in a test calendar by hand.
It helps to keep a separate calendar for each specialist: the agent checks the right calendar instead of sorting through a shared one. In this setup, Google Calendar is good for testing the build on test bookings; for real clients, see the data section below.
Reminders and reschedules
Reminders reduce no-shows, and research confirms it. A Cochrane review (December 2013) of 8 studies with 6,615 participants showed that SMS reminders raise attendance at appointments compared with no reminders.
In practice there are two reminders: a confirmation the day before, so you have time to give the slot to another client, and a short reminder with the address on the day of the appointment.
A reminder in n8n is a separate workflow:
1. A Schedule Trigger node starts the workflow on a schedule, for example every day at a chosen hour (the “Days” interval).
2. A Google Calendar node with the “Get Many” operation takes the calendar events, and the workflow picks tomorrow’s visits from them.
3. A Telegram node with the “Send Message” operation sends the client a message: the client’s chat goes in the “Chat ID” field, and the time and address in the “Text” field.
4. Save and publish the workflow: according to the n8n documentation, a schedule node runs only in a published workflow.
If the client answers that they won’t come, the message goes to the agent, and it offers a reschedule with the same “Availability” and “Update” tools. The freed slot is visible to other clients at once.
Build it yourself or order it
On your own, in a week, you can build an agent on one calendar and one channel: booking, a reminder, a reschedule. That may be enough for a small salon or a solo specialist.
You need a developer when bookings live not in a calendar but in a CRM, a medical system or YCLIENTS, when there are several channels including the phone, and when the agent must check prepayment. How YCLIENTS connects is described in the integrations section.
A name, a phone number and a visit time are personal data, and in a clinic also health data. Under 152-FZ, Russia’s personal data law (Art. 18, Part 5), recording and storing the data of Russian citizens in databases outside the country is not allowed. So for real clients in Russia, the calendar, n8n and the model go on a server in Russia. How we do this is on the page about data security.
Our pilot: a booking agent on one process, 14 days, from $1,499, with the metric in the contract. How such an agent looks at work is described in our article on how an AI receptionist books clients.
A typical booking agent is built from open blocks. If someone charges for it as for unique development, ask what the price is made of, and pay for a result by the metric, not for hours.