An AI phone agent for the desk that answers everything
A hotel phone rings against the clock. Call volume peaks in the late-afternoon arrival window, when the desk is checking in a line of guests, and again at night, when many properties do not staff the desk at all. The caller might be tomorrow's reservation, a guest upstairs who needs towels, or a planner sizing up a forty-room block — and the person best placed to answer is helping somebody standing in front of them.
ThunderPhone gives a hotel, inn, or management company an AI phone agent that works both directions: inbound coverage for reservations, guest requests, and property questions, and outbound campaigns for the confirmation and reminder calls the desk never has time to place. It answers from documents and connected systems you approve and transfers to a person the moment a call needs one — so it quotes your cancellation policy and your pet rules rather than inventing plausible-sounding ones.
You define what it may say, what it must collect, and when it must hand off — and it never takes payment-card details.
What a hotel phone agent can handle
Reservation booking, changes, and cancellations
Booking calls are the core of hotel phone traffic, and they follow a predictable script: dates, room type, number of guests, special requests, name, and contact details. The agent can walk through that intake conversationally, check availability and book through a connected reservation system, property-management API, or calendar — via HTTP tools, MCP servers, or webhooks — and repeat the details back before confirming. Modifications and cancellations run the same way: locate the booking, make the change the system permits, state the cancellation policy as written, confirm the result.
Rate and availability questions — from approved content, not guesswork
"What are your rates?" is a harder question at a hotel than it sounds, because the honest answer usually depends on dates and demand. The agent answers from two safe sources: the approved material you attach — rate ranges, packages, what the rate includes, deposit and cancellation terms — and a connected system when one exposes live availability or pricing. When neither source answers, it says so and offers a transfer to reservations, a callback, or the booking link. It never improvises a number.
Front-desk overflow — and the overnight desk you don't staff
Many properties only need the agent to answer the calls the desk cannot reach: it picks up when the line is busy, during the check-in rush, or on the overnight shift a smaller property leaves unstaffed. Callers get an answer instead of voicemail; the morning desk gets a queue of clean, categorized follow-ups instead of a blinking light. Because ThunderPhone supports SIP trunks and bring-your-own numbers, the published number stays exactly as it is; the overflow rule lives in the telephony setup.
Guest-service requests routed to the right department
In-stay calls are mostly small and time-sensitive: extra towels, a room that will not cool down, a dripping faucet. The agent can capture the details a work order needs — room number, issue, urgency as the guest describes it — and route by category: a webhook task into the property's ticketing or housekeeping system, a message to the right team, or a transfer to engineering for anything flagged urgent. The guest states the problem once, and it arrives at the right department as data rather than a relayed note. Anything on the property's emergency list skips the queue and follows the escalation path you configure.
Pre-arrival confirmation calls, placed outbound
Reaching guests a day or two before arrival is standard front-office practice — and the first task a busy desk drops. An outbound campaign can call upcoming arrivals, confirm the stay, capture the arrival time, note requests the property wants to know about in advance — an early check-in hope, an accessible room, a crib — and relay each answer by webhook so the desk and housekeeping can plan the day. Voicemail detection can leave your configured message or retry on the schedule you set. The property remains responsible for consent, identification, calling windows, and other applicable outbound-calling laws.
Late check-out, amenities, and property questions from the knowledge base
Many hotel calls are questions the website already answers: check-in and check-out times, parking, pool and gym hours, breakfast, pet policy, airport shuttle. Attach the property's own documents — policies, amenity descriptions, event packets, local-area guides, up to 5 MB per text file and 50 MB per PDF or DOCX — or import pages straight from the website by URL, and the agent searches that material mid-call. For late check-out, it states the policy and fee as written and — where the property's system exposes the action — records or books the request; otherwise it files it for the desk to approve. When the pool hours change, update the document and the phone answers change with it.
Group, event, and room-block inquiry intake
Group business arrives as a structured inquiry — dates, room-block size, meeting space, food-and-beverage needs, budget range, decision timeline — and it is expensive to lose to a slow response. The agent can run that intake on the first call, answer questions from the property's event and wedding packets, and schedule a follow-up with the sales manager through a connected calendar, so the complete inquiry arrives as structured data the hour the planner called. Contract terms, negotiated rates, and anything involving payment go to a person.
Wake-up and reminder calls
Wake-up calls are a front-office standard that ties up a person at the least-staffed hour. On an eligible production number, the agent can place them on schedule with the property's configured script and log each outcome, so the desk can see that the 5 a.m. calls happened. The same mechanism covers reminder calls the property defines: a shuttle departure, a spa appointment, a checkout-time reminder.
Multilingual guests on one number
A hotel is where language coverage earns its keep. International guests hit the phone at exactly the moments language friction hurts most — booking, arrival logistics, a problem in the room — and no desk can staff fluency in every guest language around the clock. ThunderPhone supports 47 voice languages: set a primary language and additional languages for your guest profile, and the agent switches mid-call when a caller changes to one of them — no separate line, no translation app across the desk. The same booking rules and escalation paths apply in every language, and every call produces a reviewable transcript.
Multi-property routing for groups and management companies
A group can run one front-door agent that identifies which property the caller wants, answers from property-scoped documents, and books against the right system or transfers to the right desk. Common requests can flow to a shared reservations team with the property attached; on-site requests route to the property itself; event inquiries from any location can land with one central sales team. The agent can also navigate keypad menus and wait on hold when calling out through a property's existing phone tree to reach staff.
Sample hotel call flow
Agent: Thank you for calling the Meridian Harbor Hotel. Are you calling about a reservation, a current stay, or something else?
Caller: I have a room booked for Thursday. I wanted to add a night, and my flight gets in around 11 p.m. — is that a problem?
Agent: Not a problem — I have noted the late arrival on your reservation. May I have the name on the booking?
Caller: Amara Diallo.
Agent: Thank you. I see the reservation for Thursday for two nights, and the same room is available for Saturday night at the rate shown on your booking. Shall I add it?
Caller: Yes, please. And is the pool open in the evening?
Agent: The pool is open until 10 p.m. daily. I have extended your stay through Sunday checkout, and you will receive an updated confirmation.
The extension happened through a connected system, the pool hours came from the property's own documents, and the arrival note reached the desk as structured data. A deposit on a card would have gone to staff — the agent never takes card details.
Features that matter in a hotel
Booking actions through connected tools
Agents can call HTTP APIs and MCP tools during a conversation. If the reservation platform or property-management system exposes an action — check availability, create, modify, cancel — the agent can use it and confirm the result. Completed calls post structured results to your endpoints, signed with HMAC-SHA256 and retried automatically, so a briefly unavailable endpoint does not lose a booking.
Your numbers, your telephony
Bring the property's existing numbers through a supported VoIP connection or SIP configuration; verified numbers handle inbound and outbound calling. A web widget can put the same agent on the property's website, so a guest comparing dates at midnight can ask a question without dialing.
Transfers that respect the desk
Cold transfers route a caller immediately. Warm transfers, available on eligible production VoIP or SIP numbers, keep the guest on hold while the agent privately briefs the recipient — "guest in 412, no hot water, second call" — and connect only if the person accepts. If nobody picks up, the agent returns to the caller, takes a message, or follows the configured fallback.
Every call reviewable, every change testable
With recording enabled, calls produce recordings, transcripts, and grading, so a manager can skim how the overnight line was handled. Before a prompt change goes live, run AI-caller simulations of the scenarios that worry you — a cancellation dispute, a midnight arrival, a caller who switches languages mid-sentence — and keep graded scenarios as a regression suite so a change never quietly breaks the escalation script. A/B experiments can compare two greetings or booking flows on live traffic.
What the agent should not do
Guardrails are part of the configuration, and some are platform policy:
- No payment-card details, ever. Deposits, holds, and folio payments are completed by staff or by the property's existing booking and payment systems. The agent explains the policy, collects everything else, and hands off.
- No invented rates or availability. If no connected system or approved document answers the question, the agent says so and offers the configured alternative — a transfer, a callback, or the booking link.
- No improvised policy. Cancellation terms, pet rules, and fees are stated as written; exceptions route to a person with authority to grant them.
- Compliance stays configurable. ThunderPhone's public posture is GDPR and HIPAA compliant; the property still controls recording settings, retention, guest notices, and where call data is sent, and remains responsible for its own obligations.
What would this cost each month?
Suppose a property handles 2,000 AI-assisted calls per month, averaging 3 minutes each:
2,000 calls × 3 minutes = 6,000 minutes per month
- Spark:
6,000 × $0.02 = $120/month - Bolt:
6,000 × $0.05 = $300/month - Storm:
6,000 × $0.09 = $540/month
That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.
The arithmetic is illustrative. A limited-service property fielding mostly amenities calls will run shorter; a group running pre-arrival campaigns and event intake will run longer.
Frequently asked questions
Can a ThunderPhone agent book and change hotel reservations?
Yes, when connected to a reservation system, property-management API, or calendar that exposes those actions. The agent can check availability, book, modify, or cancel, and confirm the result. Without an integration, it collects a complete structured request and delivers it to the desk by webhook.
Can it quote room rates?
It answers from the approved material you attach or from a connected system that exposes live pricing. When neither source answers, it says so and routes the caller rather than inventing a number.
Can it take a deposit or hold a card for a booking?
No. The agent states the deposit policy, books where the connected system allows it, and transfers the caller to staff or the property's existing payment flow. Payment-card details are never collected by the agent.
Can it handle guest requests like housekeeping and maintenance?
Yes. It captures the room, the request, and the urgency, then routes by category — a webhook task into the property's ticketing system, a message to the right team, or a transfer for anything flagged urgent. Emergencies follow the escalation path you configure.
Can it place wake-up and confirmation calls?
Yes — individual outbound calls or campaigns on an eligible production number, with voicemail detection and retries. The property is responsible for consent, identification, calling windows, and other applicable outbound-calling laws.
What languages can it speak with guests?
ThunderPhone supports 47 voice languages. Configure a primary language plus additional languages, and the agent can switch mid-call when a guest changes language, provided the selected voice supports the configured set. The same policies apply in every language.
Can one agent cover several properties?
Yes. It can identify the property the caller wants, answer from property-scoped documents, book against that property's system, and transfer to the right desk — or route reservations to a shared team and event inquiries to central sales.