Reservation management
Reservation calls interrupt the same staff members who are serving the people already on site. The caller wants a clear answer about a date, time, party size, room, session, or resource. The business needs accurate contact details and a booking that reflects current capacity. A voicemail or handwritten note is not enough when availability can change before someone calls back.
An AI phone agent can handle a defined reservation flow: collect the request, check availability through an approved connection, confirm the caller's choice, and record the result. It can also handle permitted changes or cancellations when the connected system exposes those operations. Capacity rules, exception policies, and allocation decisions remain with the business. Restaurant, hospitality, venue, and service businesses apply those rules differently; ThunderPhone's industry guides cover those operating details while this page stays with the reservation function.
A concrete reservation call
Consider a caller trying to reserve a table for a family dinner.
Agent: Thank you for calling Harbor Room. I am the restaurant's AI phone assistant. I can check reservation availability. What date, preferred time, and party size should I look for?
Caller: Friday around seven, for six people.
Agent: Thank you. Do you have any seating needs the restaurant should know about?
Caller: We need space for a wheelchair.
Agent: I will include that in the request. The approved reservation system shows an opening at six thirty and another at seven forty-five. Would either work?
The agent reads only availability returned by the connected source. After the caller selects a time, it collects and confirms the name and phone number, repeats the date, time, party size, and seating note, then attempts the booking. It says the reservation is confirmed only after the operation succeeds. If neither time works, it can offer the separate waitlist management flow or route the caller to staff, depending on the business's policy.
For a consultation room, equipment rental, class, or venue tour, the fields change but the pattern does not: identify the resource, check current availability, confirm the exact selection, and write only through an approved operation.
How to configure the workflow on ThunderPhone
Start by identifying the source of truth. Appointment-like reservations may fit Cal.com or Google Calendar. Capacity-based inventory may require a business-controlled tool exposed through Zapier MCP, another remote MCP server, or an existing REST workflow. If no connected operation can read and write current availability, configure the agent to take a reservation request for human confirmation rather than claim a booking.
The agent prompt should define:
- the opening disclosure and the kinds of reservations it may handle;
- required fields, such as date, time, party or group size, resource, location, name, and contact details;
- which preferences or access needs to collect without promising an assignment;
- how many available options to read and when to offer alternatives;
- a confirmation step before creating, changing, or canceling a reservation;
- language for full availability, integration errors, duplicate bookings, late requests, and policy exceptions;
- when to offer a waitlist, record a callback request, or transfer to staff; and
- a rule never to invent availability, fees, deposits, cancellation terms, or special accommodations.
Attach approved hours, directions, reservation policies, accessibility information, and stable frequently asked questions to the agent's knowledge base. ThunderPhone supports text, Markdown, CSV, PDF, and DOCX documents, selected per agent, and the agent can search attached knowledge during a call. Keep live availability in the connected reservation source rather than a static file.
Use an inbound demo U.S. number during testing. Demo numbers are inbound-only and not intended for production. Production numbers can be brought through supported direct VoIP connections or manual SIP configuration, and verified imported numbers support inbound and outbound calling. Cold transfer can route a caller immediately; attended warm transfer requires an eligible production number capable of an outbound SIP leg.
For integrations, attach only what the flow needs. Cal.com or Google Calendar can support time-based booking. Google Sheets can support a simple request queue. Slack can notify staff about exceptions. REST or webhooks can deliver completed call data to the business's system. ThunderPhone can add a remote MCP server by URL, synchronize its available tools, and attach it to an agent; the server must support streamable HTTP. The external system still controls which operations and inventory are available.
Test successful booking, no availability, a changed party size, an ambiguous date, a duplicate name, a cancellation, an accessibility request, and every integration-failure path. ThunderPhone supports browser mic tests, AI-caller simulations, reusable scenarios, graded call logs, and regression suites with pass-rate gates. Simulations are billable real calls, and the charge appears before a run.
What to measure
Measure whether the reservation record matches what the caller and the source of truth agreed:
- successful requests, confirmations, changes, and cancellations;
- corrections to date, time, name, contact details, or party size;
- duplicate or missing reservations;
- callers offered an unavailable option;
- waitlist and human-handoff outcomes; and
- tool failures or staff rework by reservation type.
Grade the call for explicit confirmation and accurate language after the write attempt. A low transfer rate is not automatically good if the agent is concealing uncertainty. Related workflows include rescheduling and cancellations and an FAQ answering line. See appointment setting for the underlying scheduling concept.
Where a human remains necessary
Staff should handle overbooking decisions, exceptions, complex resource combinations, disputed cancellations, special-event terms, and any accommodation the system cannot confirm. Payment handling remains outside this phone flow. If a reservation requires a deposit or another payment step, route the caller to the business's approved human or external process. When availability data is missing or stale, the honest outcome is a request pending human confirmation, not a promised reservation.