When a guest's AI assistant contacts your hotel: what staff may share and confirm

An AI assistant acting for a guest is a third party. Staff may give public facts and general prices in writing, but nothing about a named guest's booking, payment or stay until identity is verified through a channel the hotel already holds. Changes and confirmations need the guest, not the assistant.

A message reaches the reservations inbox asking to move a booking two days later, and it is signed by software acting for the guest. The desk has a rule for travel agents and a rule for a guest's secretary. It has none for this. After reading, you will have one rule, one script and one log entry that cover an AI assistant contacting a hotel the same way they cover every other third party.

What is actually happening when software contacts your hotel?#

Software that acts for a traveler is now being pointed at businesses, and it lands in the same inbox and on the same phone line your staff already answer. Google announced on its official blog an AI-powered calling feature in Search: Search can call local businesses, described as ranging from pet grooming to dry cleaning, to get pricing and availability information on the user's behalf (Google blog, "More advanced AI capabilities are coming to Search", 16 July 2025 (opens in a new tab)). The same announcement says the feature was starting to roll out to all Search users in the US, with higher limits for subscribers, and that businesses stay in control through their Business Profile settings.

What the announcement does not say matters just as much: nothing about hotels, nothing about Türkiye, no volume of calls, no outcomes. Read it as a signal of shape, not a forecast.

Two shapes reach a hotel: a written request, by email, OTA message or a web form, and a spoken one, an automated caller with a synthetic voice. Separate two jobs inside them. An assistant shopping anonymously for prices is a sales inquiry. An assistant acting for a named guest who already holds a booking is a data question. The answer to each is different.

Staff do not need to classify the technology. They need to classify the request, which is a skill the desk already has. If you want the longer arc of how bookings themselves arrive through these channels, read what reaches the front desk when an AI assistant books a hotel.

How do you tell an AI assistant from a person on the phone?#

Usually you cannot, and the procedure should not depend on it. What matters is whether the caller is acting for a named guest and can prove it.

Some signals appear in writing: a self-description such as acting for a named guest, a request phrased as a tidy list of questions, a reply address on a platform domain, or a refusal to give any direct contact for the guest. Some appear on the phone: a flat, evenly paced voice, no background noise, and no answer to an unexpected question about the guest's own preferences. None of these is proof of anything.

Do not build a detection test. Synthetic voice detection is unreliable, and a wrong guess either blocks a real guest's helper or waves a bad caller through. Instead, ask the two questions you would ask any third party: the booking reference, and a way to reach the guest on a channel the hotel already holds. Record the channel itself, the email domain, the phone number, the time. That record is what a supervisor needs an hour later.

If the caller will not or cannot identify the guest, the request is an anonymous inquiry and gets the anonymous answer.

For the phone side generally, the habits in a call standard for in-house guests, wake-up calls and messages carry over unchanged.

Is an AI assistant a third party under your own rules?#

Yes. An assistant is software acting for someone else, so it sits in the same category as a travel agent, a secretary or a relative, and the same rule applies: nothing about a named guest leaves the desk until the person asking is verified as entitled to it.

KVKK, Türkiye's personal data protection law, puts the duty on the controller. Article 12 requires the data controller to take all necessary technical and administrative measures to prevent unlawful processing of and access to personal data, and makes the controller jointly responsible for those measures with anyone processing data on its behalf (mevzuat.gov.tr, Law No. 6698, consolidated text (opens in a new tab)). That makes "who may I tell" a data protection question, not a courtesy question. The answer does not change because the asker is software.

One distinction matters for your paperwork. The assistant's operator is not your processor; it works for the guest. Your processor is whoever runs your own systems. If the operator sits abroad and guest data would go to it, Article 9 as rewritten by Law No. 7499 in 2024 applies: a Board adequacy decision, or appropriate safeguards such as a standard contract announced by the Board, notified to the Authority within five business days of signing. Confirm your own case with your legal adviser.

Write the rule down once, so a night-shift receptionist and a reservations manager give the same answer at 02:00 and at 10:00. A fuller walk-through of guest data requests sits in guest data requests under KVKK: a front office procedure.

What may staff answer without the guest?#

Public facts and general prices, in writing, exactly as to any anonymous caller.

Public facts include the address and directions, check-in and check-out times, parking, pet policy, pool and spa hours, accessibility, whether there is a lift, and restaurant hours. General prices include your published or standard rate for the dates asked, availability at the level of "yes, we have rooms of this type", and what the rate includes. Never give the guest's own rate, a group or contracted rate, or anything that reveals another guest's arrangement.

Send it in writing even when the question came by phone. A price dictated to a caller cannot be checked later, and an accepted offer needs a record. Treat a request for a quote as a new inquiry with its own expiry, not as a change to an existing booking. If the request compares several date ranges, answer it, but keep the quote dated and time-limited so it cannot be used months later.

The mechanics of turning such inquiries into reservations are covered in phone, email and WhatsApp booking requests and how to turn them into reservations.

What always needs the guest?#

Anything that touches the guest's booking, money or personal data waits for the guest, on a channel the hotel already holds.

Date changes, cancellations, name changes and room moves all wait. Confirming that a named person is or will be staying waits too: that is personal data, and in Türkiye every stay also involves a guest identity notification (KBS) and personal data under KVKK. Payment, refunds, card details, deposits, and any charge added to a bill wait. Invoices, folios and any document carrying the guest's name and spend wait.

Two tools carry the weight. The known-channel rule: a change comes through the channel the booking came through, or from the guest's own verified contact, never from a new address that merely claims authority. The callback test: if the guest can be reached on the number or address already on the booking and confirms, the assistant's request can proceed; if not, it waits.

A screenshot, a forwarded email or a claim of authorization is not proof. Authorization claimed by the caller is not verification.

What does the desk actually say? A short script#

Three sentences cover every third-party request, whether the caller is a person or software.

Line one sets the frame: "I can help with general information and our published rates. Anything about a specific booking needs the guest's confirmation." Line two asks for the two things: "Could you give me the booking reference, and the best way to reach the guest on the contact we already have?" Line three moves it to writing: "I will send what I can by email now, and pass the rest to the reservations manager."

Then stop. Do not argue about whether the caller is a robot, and do not explain your security rules to it. When pushed, repeat line one word for word; repetition is the whole technique. Hand over to a supervisor when money, a complaint or a guest already in the building is involved. Use the same script for a travel agent, a secretary and an assistant. One rule, one wording, no exceptions to remember at 02:00.

How do you log it, and who do you tell?#

Log the contact like any third-party request, then pass it to the people who own your channel settings and your booking system.

Record the time, the channel, what the caller said it was, what was asked, what was given, any booking reference, and the staff member. Pass it to the reservations manager the same day: a pattern of these requests is a channel question, not a front desk question. Tell whoever owns your business profile and channel listings, because the settings that decide what is published about your property are the same ones that decide what an assistant can read.

If the contact tried to obtain guest data under a false pretense, treat it as a possible data incident and take it to your legal adviser immediately. KVKK (kişisel verilerin korunması kanunu) requires controllers to notify the Board and affected individuals in the event of a data breach; your adviser will confirm the specific timeline and procedure for your facility. Do not brief staff on penalty amounts; the procedure is what they need, and the amounts are a question for your legal adviser. Review the log monthly: which requests were answerable, which were refused, and whether the script held under pressure.

What to do next#

Write the third-party rule down this week, add the three script lines to it, and hand the same page to reservations, front office and the night shift. The technology will keep changing; the test, "can this person prove they are entitled to this guest's information", does not.