A guest's video spreads online: a hotel's first 24 hours of crisis communication

A hotel crisis management plan is a short written set of decisions made before a guest video spreads: who speaks for the hotel, who checks the facts, how the guest is contacted in private, and what three sentences go public. The first 24 hours work when the plan is rehearsed, not improvised, and when guest data stays private.

The video is ten seconds long: a wet floor, a raised voice at the desk, a room that was not cleaned. By evening a news site has embedded it, and the hotel's first reply, typed quickly, has become the second story. This guide gives you a working hotel crisis management plan you can write this week: how to tell a crisis from a bad review, what to do in the first hour, how to approach the guest in private, what the public statement says, and what never to do with guest data.

What counts as a crisis, and what is just a bad review?#

A crisis is a claim that is spreading, is being checked by people outside the hotel, and can move bookings. A bad review is one guest's opinion that sits still on one page.

Apply three tests before you open the crisis plan. First, is it spreading beyond the original post: shares, news sites, aggregator accounts. Second, is it checkable: a video, a document, an incident report, something a journalist can verify independently. Third, does it name the property or a member of staff. If all three are true, it is a crisis. If only one is, it is reputation work.

A single low score with a written complaint belongs in the normal weekly routine, not in the crisis plan. That routine is described in hotel online reputation management: a weekly routine for a small team, and it should stay calm, repeatable and boring. The crisis routine is different: short, serious, and used rarely.

Most real crises have a factual core. Something did happen, a wet floor, an argument, a missed cleaning, and the argument is about how the hotel handled it afterwards. This is why the plan focuses on checking and fixing, not on arguing.

Decide in advance which role may declare a crisis, usually the general manager or the owner, and name a deputy for nights and weekends. A duty manager at 02:00 should not be waiting for a committee. Write the threshold down in one sentence, for example: "the plan opens when a claim about this property is being shared outside its original page and names the hotel or a staff member." A plan used too often stops being believed.

What should happen in the first hour?#

In the first hour the hotel stops unverified detail from spreading: one person owns the response, one log holds every fact and timestamp, and nothing is published until the core claim is checked.

Name the incident owner for the day, usually the general manager or the duty manager, with a named deputy and a phone number that is actually answered. If the owner is the incident owner, the deputy is the person who can act when the owner is asleep or on a plane.

Open one log and keep it in one place. Time, source, what was seen, who was contacted, what was decided. This log becomes the record for counsel, insurers and the week-after review, so write it as if a stranger will read it, because one will.

Check in this order: does the footage show this property, what date, is the guest identifiable, and what do the reservation record and any incident report say. The reservation record answers whether the person was a guest at all; the incident report answers whether staff already knew. If there is no incident report, that fact goes in the log too.

Before speaking to anyone outside, write three lists: what is known, what is claimed, and what is unknown. The unknown list is the one that gets hotels into trouble, because the pressure is to fill it with guesses. Leave it empty and say so.

Give the front desk and the switchboard one sentence they can say, so five people answering the phone do not produce five versions. Something like: "We are aware of the video, we are looking into it, and our manager will have a statement today." Then tell the owner and the relevant department heads once, in writing, and keep the channel quiet.

Set a review time, for example 90 minutes, so the owner does not disappear into the problem and stop deciding. At the review time, decide: publish now, or check one more thing first.

How should the hotel deal with the guest first?#

The guest is contacted privately, by a named person, before the hotel says anything in public. The conversation is about the stay and the fix, not about the video.

Use the channel the guest booked through, plus a direct call if a number is on file and the guest has not asked for no contact. Open with the specific thing, not with policy: what the hotel understands happened, and what it is doing about it now. A guest who has posted a video has already concluded that normal channels failed; a policy paragraph confirms it.

Offer only what the hotel can actually deliver: a refund, a room move, a repair, a re-inspection, a written follow-up with a date. Do not make deleting the video the first request. It turns a service complaint into a fight and gives the guest a reason to post again, this time about the hotel trying to silence them.

Record what was offered and what the guest answered in the log, in the guest's own words where possible. Keep the exchange private: no screenshots of the chat, no guest names in internal group chats that get forwarded. If the guest asks for money in exchange for removal, that decision goes to the owner with counsel, never to the person on the phone.

What should the public statement say?#

A first public statement does three things in three sentences: it says what the hotel knows, what it has already done, and how to reach it. It does not argue with the guest and does not admit liability.

Sentence one acknowledges the specific situation without repeating the accusation as established fact. Sentence two states an action already taken, in the past tense, with a role or a date attached, not a promise about the future. Sentence three gives a named channel for the guest and for anyone else affected, for example a direct address monitored by a person.

Publish where the story is: the hotel's own channels and a reply under the original post where comments are open, not only a press release nobody reads. Cut adjectives, and cut the phrase about taking things very seriously when it is the whole content; say what was done instead.

Every apology, admission and liability word goes past counsel before it is posted. Apology and admission wording can be used later in a dispute, so it goes past counsel before it is posted. Acknowledging that a guest had a bad experience is not the same as admitting fault, and the difference matters.

For the wording of replies to individual reviews, the patterns in how to reply to hotel reviews: example replies by complaint type also apply under pressure: specific, short, addressed to the complaint in front of you.

Who hears what: staff, tour operators, booking sites and press#

Each audience gets one version of the same facts, sized to what they need to do, and all of them are told when there will be more.

Staff hear it first, in a short briefing at shift change: the one sentence, the person to route questions to, and an explicit instruction not to speculate. Tour operators and travel agencies get a factual note for the accounts that sell the hotel, because their call centers often hear the question before the hotel does. Booking sites and review platforms are answered through the property's own account; never open a second identity or a new profile to answer, because it reads as concealment and puts the property account at risk.

Press gets one spokesperson, a written statement, and a stated time for the next update. A refusal should be a full sentence, not a shrug: "We cannot confirm that detail today; the next update is at 17:00." Owners and investors get the same note as staff plus the log, so nobody hears a version from a friend before hearing it from the hotel.

Assume every message is forwarded. Never brief one audience with detail you would not give another.

Review platforms each score and display replies differently, so the same three sentences may need different trimming; how the Booking.com review score is built and what moves it is covered in Booking.com review score: how it is calculated and what moves it.

What not to do: guest data, camera footage, threats, deleting comments#

The fastest way to turn a service complaint into a legal problem is to publish the guest's personal data or the camera footage in order to prove the hotel right.

Under Article 12(4) of Law No. 6698, data controllers and data processors may not disclose personal data they have learned in breach of the law, nor use it outside the purpose of processing, and the duty continues after the person leaves the post. Article 12(1) requires the controller to take all necessary technical and administrative measures to prevent unlawful processing of, and unlawful access to, personal data; publishing footage to win an argument is the opposite of such a measure. Article 17(1) applies Articles 135 to 140 of the Turkish Penal Code to crimes involving personal data, and Article 136 of that Code punishes anyone who unlawfully gives personal data to another person or disseminates it with two to four years' imprisonment. Personal data may be transferred to third parties without explicit consent only where a condition exists under Article 5(2), or for special-category data under Article 6(3), and a hotel should not assume that defending its reputation qualifies; confirm the position with counsel before publishing anything. (Source: T.C. Cumhurbaşkanlığı Mevzuat Bilgi Sistemi, consolidated Law No. 6698 (opens in a new tab), 2026-11-07.) Confirm your own case with counsel.

Never threaten the guest, publicly or in a private message. The threat becomes the story and can become a criminal complaint. Do not delete critical comments to clean the thread; deletion is visible, screenshot-able and reads as concealment. Reply, or leave it standing. And do not put a staff member's name or face in public to absorb blame; that is a labor and privacy problem on top of the original one.

For what may lawfully be recorded and shown inside the hotel in the first place, see CCTV in hotels under KVKK: a checklist for notices, placement and footage.

The week after: what changed, and how to say so#

The week after is where the hotel earns the story back: one written change, checked, and said plainly to the same audience that saw the video.

Run a short review against the log: what was claimed, what was true, what the hotel did, and what it could not do. Then change one thing that can be verified: a cleaning check step, a night-shift escalation rule, a repair, a training hour with a date on it. One real change is worth more than five promised ones, because a promised change invites the question "and the other four?"

Say it in the same place the story ran, in one or two sentences, without re-arguing the video. Something like: "Following Saturday's video, the cleaning check step now runs before every check-in on that floor, signed by the supervisor." Then stop.

Update the plan with what actually slowed the response. Common findings: missing phone numbers, unclear decision rights, nobody on shift who could speak to a foreign guest and a journalist at the same time. Close the incident report and file it with the log, so the record exists if the claim returns; what belongs in that record is covered in hotel incident reports: what to record after an accident, a theft or a dispute.

Watch for a second wave for a few weeks. It usually arrives through an aggregator or a forum, not from the original poster, and the same three-sentence discipline handles it.

Write the one-page plan this week#

Do this while nothing is happening. Write the one-page plan: the named incident owner and deputy, the log template, the three-sentence shell for a public statement, the private contact checklist and the do-not list. Then walk it once with the front desk and the night manager, because the first 24 hours are decided by what was agreed before the video appeared.