Messaging guests on WhatsApp during the stay: one line, clear rules and consent

A hotel WhatsApp line is one business account the hotel owns, answered on hotel devices by a named person each shift, with every request logged in the guest's record. Service messages about a stay need no separate consent when the guest gave a number to be reached; marketing needs prior consent under Law No. 6563.

It is 23:40 and a guest writes to the number printed on the booking confirmation: the air conditioning is loud and the baby cannot sleep. The message lands on a receptionist's personal phone, and she is off tomorrow. This article shows how to set up WhatsApp for hotels properly: one owned line, a named person per shift, reply times you can staff, the consent line between service and marketing, a never-send list, and a way to get every conversation into the guest's record.

Why do guests message the hotel on WhatsApp instead of calling?#

Because the app is already open on their phone and a message does not require both people to be free at the same moment. Messaging is asynchronous: a guest can send a photo of a safe that will not lock at any hour, and the desk can answer when it has hands free. The number is usually already in the guest's phone, taken from the booking confirmation or the agency's message thread, so it is the shortest path the guest can see.

A personal phone breaks the record. Nothing is visible to the manager, nothing survives a shift change, and nobody can say afterwards what was promised or by whom. It also breaks continuity of employment: when the staff member who set the account up leaves, the conversation history and the guest contacts leave with them. A personal number also blurs the boundary between service and friendship, and guests keep using it months after checkout for requests the hotel never agreed to handle.

The manager's real problem is not the app. It is that the hotel has no single answer to the question: what did we promise this guest, and who promised it.

Who should answer the hotel's WhatsApp line, and from which device?#

The hotel owns the number, the device stays at the desk, and one named person per shift is responsible for it. There are two ways to run it. The WhatsApp Business app on a hotel-owned phone or tablet at the desk is simple and manual, with one device answering. The WhatsApp Business Platform, usually run through an approved provider, gives several people a shared inbox and adds message templates. Choose by volume and by whether two people must answer at the same time.

Register the number to the hotel, not to an employee's personal SIM, and keep the SIM card and the account recovery details in the hotel's possession, not in someone's drawer. Define who may answer what: a housekeeping supervisor can answer a request for extra towels, but not a question about the bill. Write the split down so nobody guesses at 02:00.

Ban personal phones in writing. If a staff member has already given a guest their own number, move that guest to the hotel line with one short message and log the move. Keep the device charged, locked and in one place, so that the line does not go silent because a phone went home in a pocket.

What reply times can the hotel actually keep?#

Commit to a window you can staff on your quietest night, and separate acknowledging a message from resolving it. Run two clocks, not one. Acknowledgement means a person has read the message. Resolution means the request is done, or refused with a reason and an alternative.

Publish one acknowledgement window and one resolution expectation. For example: messages are read between 07:00 and 23:00, answered the same day, and a maintenance request is answered with a visit time rather than a promise to look into it. Give out-of-hours messages an automatic reply that states when a human will answer and gives the front desk phone number for genuine emergencies such as a leak, a lockout or a safety issue. Messaging is not the emergency channel; the desk phone is.

On the WhatsApp Business Platform, the 24-hour customer service window opens and resets with each message the guest sends; inside it a business may reply without a template, outside it only approved templates may be sent, according to WhatsApp's Business Messaging Policy (opens in a new tab) (23 September 2026). That shapes what you can promise: a message a guest sends at 02:00 is easy to answer at 08:00, while a message you want to send two days after checkout needs a template. If you use any automated reply inside that window, the same policy requires a clear way to reach a person, such as transfer to a human agent, a phone number or an email address.

Measure before you publish. For two weeks, count messages per hour and the gap between the guest's message and the first human reply, then set the promise just below what you actually achieved.

Service messages versus marketing: what consent is needed?#

Messages about a service the guest has already bought need no separate consent when the guest gave a number to be reached; anything that sells needs prior consent. Under Law No. 6563, Articles 6 and 8, commercial electronic messages may be sent only with the recipient's prior consent, no separate consent is needed for messages about changes to, use of or maintenance of goods or services already supplied when the recipient gave contact details to be reached, and recipients may refuse commercial messages at any time without giving a reason (T.C. Cumhurbaşkanlığı Mevzuat Bilgi Sistemi, Law No. 6563 (opens in a new tab), viewed 1 November 2026).

The practical line is whether the message is about the stay in front of the guest. "Your room is ready", "your transfer moved to 06:30" and "your bill is ready" are service. A spa discount tomorrow, a rate for next summer and a come-back-in-October offer are commercial.

WhatsApp's own rules sit on top of the law: a business may contact someone only after receiving opt-in permission, and it must respect any request to block, stop or opt out (WhatsApp, Business Messaging Policy (opens in a new tab), 23 September 2026). Two rulebooks apply at once, and the stricter one wins.

Under KVKK Article 10, when you collect the number you must tell the guest who the data controller is, why the data will be processed, to whom and why it may be transferred, the method and legal basis of collection, and the guest's rights (T.C. Cumhurbaşkanlığı Mevzuat Bilgi Sistemi, Kanun No. 6698, Madde 10 (opens in a new tab), viewed 1 November 2026). A short notice at check-in plus a link in the confirmation email does this; a line buried in a long form does not. Keep a record of each consent: date, channel, the exact wording the guest agreed to, and how they can withdraw it. A screenshot of a chat is not a consent record.

Cross-border transfer questions and the legal basis that fits your own case belong to your counsel. This article does not decide them, and neither should a receptionist.

What should never be sent or accepted by message?#

Card numbers, identity photos and anything about another guest never travel through a chat thread. Never accept a full card number with its security code, a photo of a passport or identity card, bank account details, medical information, or another guest's name or room number.

The reason is mechanical, not moral: a chat thread is copied to every device signed into the account, may be backed up outside the hotel's control, and is read by whoever is holding the phone at that moment. If a guest sends a card photo anyway, do not forward it, do not type the number into a reservation note, delete the message where the platform allows, and move the payment to the desk or to a payment link the hotel controls.

Identity is checked in person at the desk. A photo sent by message is not a substitute for that check, and the desk should say so politely rather than accept it. Never send another guest's room number, a door code, a screenshot of the rooming list, or a staff member's personal phone number. Do not put several guests into one thread, even for a group booking; a group chat shares every reply with everyone in it.

How does a WhatsApp conversation end up in the guest's record?#

Every message that contains a request or a promise becomes a logged item with an owner and a closing time, and the thread itself is not the record. Log at the moment of reading, not at the end of the shift: what was asked, who owns it, when it is due, and what exactly was promised. A note written six hours later is a summary, not a record.

Promises are the risky part. "We will move you to a quieter room tomorrow" is a commitment with a time attached; it belongs where the next shift looks, not in a chat that scrolls. Treat the message as a request like any other, with an owner and a closing state, so that the same discipline covers the phone, the desk and the app, as described in logging, assigning and closing each guest request.

Answer in the language the guest wrote in. If nobody on shift can, say when someone can, rather than sending a machine translation of a promise nobody can keep; a language plan for your guest mix covers this in detail. On the guest profile, store the number together with the consent record and a note that this is the guest's preferred channel. Close the thread at departure instead of keeping it open as a marketing list. At checkout, send one short closing message and point the guest to email or the guest app for anything that comes later, so the line stays a service channel.

Other channels: email, SMS and a guest app#

Use each channel for what it is good at, and keep one record behind all of them. Email carries detail: confirmations, documents, pre-arrival information and anything the guest may want to keep or forward, as covered in what to send guests before arrival. SMS is short and time-critical and works when mobile data is off, which makes it a reasonable fallback for a changed transfer time, and a poor place for a paragraph.

A guest app puts the bill, room service, spa bookings, requests and offers in one place, and a request made there arrives with the room number already attached, which a chat message does not. AI Otel's guest app is built: every hotel gets its own guest app, installed from the browser with no app store, with the bill, room service, spa bookings, requests and offers in one place. It is a web app, not a native app, and not every guest will use it, so it sits beside the other channels rather than replacing them. Whatever the guest chooses, the request log, the guest record and the consent record stay the same; only the door changes, as the channel comparison explains.

What to do next#

Write the one-page line this week: who owns the number, who answers on each shift, the acknowledgement window you can staff, the service-versus-marketing line, and the never-send list. Then read your next ten conversations against it, log every request and promise they contain, and have counsel check the consent wording before the first commercial message goes out. If you want to see how a guest app sits beside your WhatsApp line, request a briefing at https://ai-otel.com/contact.