Guests

Hospitality Service Recovery: Fix, Make Right, Follow Up

Handle guest complaints with a clear sequence: listen, assess the impact, restore service and consider proportionate compensation. Give your team approval limits, follow-up messages and a record that distinguishes completed work from verified recovery.

Sixto team21 min read

Aparthotel photo: guests

Recover the stay, not the review

Listen, assess the impact, fix the problem, consider proportionate compensation, follow up and prevent a repeat. That is service recovery in hospitality: responding to a failure by restoring what the guest needs and working to rebuild trust, without promising satisfaction.

Whether you own or manage an aparthotel or short-term rental in Colombia, work at reception or lead housekeeping, keep three jobs separate:

  • Restore the service: give the guest back the use of whatever failed.
  • Recognize the disruption: consider the actual impact and a proportionate response. A repair does not erase what happened.
  • Prevent a repeat: turn the incident into an operational correction, not just an apology.

Before offering anything, ask: What does the guest need now? Can they still use the accommodation? Who owns this case? Make that person clear to the team, even when someone else carries out the remedy.

Tip: Recover the stay, not the guest’s silence. Never make help, compensation or a refund conditional on removing or changing a review.

No response guarantees satisfaction or a better rating. Your goal is a useful remedy you can verify, not a promise of a positive review.

Listen, establish the impact and identify risks

1. Acknowledge what the guest is experiencing

Reflect the guest’s words without arguing or treating an unverified report as established fact. If they say, “The noise kept me awake,” acknowledge the lost sleep. Do not downgrade it to “a minor inconvenience.”

For a confirmed failure: “We’ve confirmed that the air conditioning isn’t working. I understand the heat is stopping you from resting.”

For an unverified report: “You’re hearing noise from the neighbouring apartment and it’s keeping you awake. I’ll check what’s happening.”

Acknowledging the impact does not confirm the cause. Ask focused questions, not a string of questions that makes the guest feel cross-examined.

2. Establish what is happening now and check for risk

Start with: “What’s happening right now?” Then establish whether anyone may be at risk and whether the problem is ongoing.

If the report suggests danger, put safety before compensation. Follow the property’s emergency procedure and involve the appropriate emergency authorities. Check that your procedure reflects local guidance from the alcaldía and emergency authorities in your Colombian municipality. Do not improvise technical safety instructions.

3. Identify the affected service and immediate need

Ask only what helps you decide the next step:

  1. Which service or space can’t you use?
  2. When did the problem start, and is it still happening?
  3. What do you need to be able to do now?

For example, if a guest reports an unclean bathroom in unit 305, establish whether they can use it and whether they need to leave shortly. Those details affect priority. Do not request documents, photographs or personal information unless they are necessary to handle the case.

4. Summarise the facts and name the case owner

Keep reported information separate from verified facts. “Guest reports a dirty bathroom” is different from “housekeeping lead verified the bathroom condition.” Record what still needs checking without assigning blame.

Confirm: “You can’t use the bathroom and need to leave shortly. I’ll coordinate the check and be your contact for this case.”

Tip: Before ending the conversation, confirm the immediate need and name the person responsible. Listening without ownership leaves the problem unresolved.

Share necessary details only with the people handling the case. Keep guest names, identity documents and stay details out of open staff chats.

Fix the problem or agree the next update

An estimated repair time is not a promise of restoration. It depends on diagnosis, parts and confirmed availability. Your next update is a commitment you can control. Agree who will contact the guest, through which channel and at what time, even if the repair is still pending.

1. Assign, check and test

  1. Name one case owner. They can coordinate with maintenance and reception while remaining responsible for guest communication. Assigning the repair does not transfer responsibility for updates.
  2. Check resources before making an offer. Confirm who can attend, which alternative is available and whether you have permission to provide it. If a technician has not confirmed attendance, do not announce an arrival time.
  3. Agree access arrangements. If the work requires entry to the accommodation, obtain permission and agree entry conditions under the property's procedure. Reporting a fault does not itself give permission to enter.
  4. Offer a usable alternative. Explain what it provides and its limitations. Ask whether it meets the guest's immediate need. Something being available does not make it suitable.
  5. Test the result. Have the person handling the repair check that it works, then confirm that the guest can use the service. A completed task is not enough to close the case.

Tip: Promise the next communication, not a repair that still depends on someone else. If the estimate changes, update the guest without waiting for another complaint.

Worked example: an access code fails

In this illustrative example, the night receptionist receives a report that the code for unit [redacted] does not work. They take ownership and verify the guest's identity and authorization through the property's access procedure. They do not ask another guest to let the person in or share someone else's credentials.

After verification, the receptionist confirms an approved temporary option: a backup key issued through the established procedure. They explain how to collect it and check that the guest actually entered. Handing over a key does not prove successful entry.

If no technician is available, the receptionist does not invent a visit. They keep the case open and agree the next update. If the backup key also fails, they stop treating it as a solution. They check another authorized, available option or escalate to the shift lead while retaining responsibility for updates.

Message to agree the next update

Subject: Update on [problem]

Hi [name], we have confirmed [verified situation]. We can offer [confirmed alternative], which provides [use and limitation].

[Case owner] will contact you through [channel] at [agreed time], even if the repair is still pending. [If a confirmed estimate exists: The estimated repair time is [timeframe], subject to [condition].]

Would this alternative meet your needs while we work on the problem?

Match compensation to the impact

Restore the service and assess the impact separately. Replacing a faulty item fixes what should have worked. It does not necessarily address what the guest missed. Equally, not every failure automatically calls for a refund.

Before making an offer, establish which service was affected, for how long, how seriously and how much of the stay remains. Ask what the guest needs now. An alternative only counts if it is available and genuinely usable.

Separate four decisions

  1. Fixing the failure: provide the service that should have worked, such as replacing a broken remote control. Do not frame this as a favour.
  2. Reimbursing verified expenses: assess a cost connected to the failure, with supporting evidence and context. Do not promise to cover any purchase without reviewing it.
  3. Offering a goodwill gesture: acknowledge disruption with something useful that you can deliver. This does not replace the repair or a refund assessment.
  4. Considering a refund: review the service the guest could not use, booking terms, applicable rights and the booking channel's process. Internal approval does not mean the guest has received the money.

Use this table to assess the case, not as an automatic compensation schedule:

Impact Remedy to consider Evidence and approval needed Limitations
An amenity fails Replacement or an equivalent alternative; consider goodwill for additional disruption Advertised amenity, confirmed fault and availability; approval under the property's policy A late replacement may be useless if the guest is leaving
An essential service cannot be used Restoration, a usable alternative and assessment of related expenses or lost service Duration, affected use and expense records; approval from the designated decision-maker A partial workaround does not necessarily address the full impact
The unit is unusable Assess relocation or alternative accommodation and the corresponding refund decision Verified condition, availability and acceptance of the alternative; relevant operational and financial approval Do not offer unconfirmed inventory or assume relocation fully resolves the impact

Check whether the offer actually helps

Ask: does it address the specific disruption? Can the guest use it? Can you deliver it without creating another problem?

For example, late checkout offers little to someone who must leave early for a flight. It is also unsuitable if the next arrival or housekeeping schedule prevents you from delivering it. Find another verified option rather than reaching for a standard perk.

Tip: Match compensation to the actual impact, not the volume of the complaint. Similar complaints can need different remedies when duration, guest needs or available alternatives differ.

Before deciding, check booking terms, channel procedures and applicable consumer guidance from Colombia's Superintendencia de Industria y Comercio. Your internal policy structures decisions. Do not present it as overriding applicable rights.

Define who can approve each remedy

Give reception a written authority matrix they can access during the shift. Approval, execution and payment confirmation are separate steps. Assign responsibility for each. Not every case needs to wait for the owner.

1. Complete the authority matrix

Copy this template and replace the bracketed fields. Your property sets the limits, not this guide. Specify whether each limit applies per case or per reservation.

Action Front-desk authority Manager approval Financial approver Backup when unavailable
Replace items Within [stock rules and limit] Outside delegated scope [Purchasing approver] [Role and contact]
Arrange maintenance Request [authorized services] Spending above [limit] [Spending approver] [Role and contact]
Move a guest Within [authorized conditions], with availability verified Exceptions to those conditions [Approver for charge differences] [Role and contact]
Offer goodwill Within [limit and conditions] Beyond delegated limit [Cost approver] [Role and contact]
Issue a refund Submit only with [applicable permission] Under [approval policy] [Financial approver] [Role and contact]
Arrange alternative accommodation Check options without committing unauthorized spending Under [scope and limit] [Payment approver] [Role and contact]

2. Check before making an offer

  1. Verify stock, actual availability and suitability. An empty unit is not necessarily ready for a guest.
  2. Identify who approves and who carries out the remedy. For refunds, check the booking channel's permissions and processing procedure. Name the person who will execute and verify payment.
  3. For an exception, contact [responsible person and method], then [backup and method] if unavailable. Keep one named case owner.
  4. Record the decision and agreed next update. At handover, name the person taking over and check that they can access the outstanding commitment.

While approval is pending, you can confirm who is reviewing the request and when you will provide the agreed update. Keep approved, processed and received distinct. Do not tell a guest that money has arrived without evidence.

3. Escalate exceptions

Has the failure happened again? Does the remedy exceed your authority? Will the alternative meet the guest's actual need? Take verified facts and available options to the approver when an exception is needed. Do not repeat an unsuitable offer simply because reception is authorized to make it.

Apply the playbook to cleaning and repeated failures

Illustrative case: bathroom cleaning in unit 305

The guest says, “There’s hair in the shower, and I don’t want to use it like this.” Do not reduce that report to a minor housekeeping complaint. Establish whether the guest can use the bathroom and how another cleaning visit would affect their plans.

  1. Acknowledge and arrange verification. Say, “I’ll coordinate a check and a fresh clean. May we come in while you’re there, or would another time work better?” With permission to enter, the housekeeping lead verifies the reported hair. Keep that observation separate from anything the team has not checked.
  2. Agree on a workable intervention. Ask when the guest needs the bathroom. Confirm who will clean it before offering a timeframe. If the guest refuses entry, ask what would make access acceptable: their presence, a different time or another available arrangement. Record the refusal and the reason, not an assumption that the guest is being difficult.
  3. Inspect before handing the bathroom back. The housekeeping lead checks the reclean. Reception then asks whether the guest could use the bathroom and whether anything remains unresolved. A completed cleaning task is not proof of restored service.
  4. Assess the actual disruption. Did the guest have to postpone a shower? Was their rest interrupted? Did the remedy arrive while it was still useful? Use those answers to assess any goodwill gesture within the property's approval rules. Putting the bathroom right is not itself compensation.

The housekeeping lead owns the cleaning check. Reception remains the case owner and handles the next guest contact. Closure evidence includes the inspection, the guest's response and any outstanding commitment. If there is no reply, record “cleaning verified, guest confirmation pending”, not “guest satisfied”.

Illustrative case: hot water fails again in unit 402

The guest says, “Someone already fixed it, but it’s cold again.” The earlier repair is part of the history. It is not evidence that the current problem has been resolved.

  1. Reassess the failure. Reception acknowledges the recurrence and arranges another check with permission to enter. In this example, maintenance confirms that hot water has failed again. Ask what the guest needs now and how the remaining stay is affected.
  2. Verify the whole relocation option. Before offering a move, reception checks that another unit is available, clean and has working hot water. Check capacity, access and the guest's particular needs. An empty unit is not necessarily a suitable replacement.
  3. Get approval and agreement. The manager approves the move under the property's policy. Reception explains the verified option and coordinates the move only if the guest accepts. If they decline, ask what does not work for them before proposing something else.
  4. If no replacement unit is available, the manager checks alternative accommodation and the booking conditions before making an offer. Reception keeps ownership and agrees on the next update while that check happens. A search for accommodation is not a confirmed booking.
  5. Verify the result and assess compensation. Consider the repeated failure, lost service and disruption of moving when seeking approval for compensation. Record both approval and delivery status. Follow up to confirm whether the guest could use the hot water. Keep that response as evidence without assuming satisfaction.

Tip: Do not close a recurring failure using evidence from the first repair. Verify that the current remedy actually works.

What to do when the remedy fails or is rejected

A failed remedy changes the case. Reassess the current impact: what still does not work, what the guest has lost and whether the alternative remains useful. Do not repeat an offer simply because it already has approval.

1. Acknowledge the failure and reset ownership

  1. Name what failed without defending your intentions.
  2. Preserve relevant messages, maintenance records and approvals. Separate reported facts from verified findings; do not rewrite the history.
  3. Name an escalation owner and a backup. That person also owns the next agreed update.
  4. Verify the next option before offering it. Is it available? Does it meet the need? Who can approve it?

Tip: When the remedy fails, change the plan, not just the wording.

2. Choose the right next step

  • Missed update: acknowledge the silence, explain what you actually know and agree the next contact. Do not invent progress to fill the gap.
  • Unsuccessful repair: check the present condition and consider another intervention or an available alternative. Do not repackage the same failed fix as a new solution.
  • Unavailable manager: contact the designated backup. Reception can promise follow-up and actions within its authority, not an approval still pending.
  • Disputed facts: record both accounts and review relevant evidence without interrogating the guest. Address what you can verify while clarifying the rest.
  • Rejected offer: ask which need the offer leaves unmet. Is it unusable or insufficient? Reassess with the authorized decision-maker. Do not require a waiver or a changed review.
  • Complaint after checkout: preserve the case history and coordinate with the booking channel where relevant. Distinguish approved, processed and received refunds. Do not confirm that money has arrived without evidence.

Adapt this message only after verifying the alternative:

Subject: Next option for [case]
Hello [name], the previous remedy did not resolve [problem]. I am sorry this is still affecting you. We have [verified alternative] available, if you would like to accept it. Would that meet your needs? [Owner] will update you at [agreed time].

3. Avoid making the conflict worse

Do not argue about good intentions, blame housekeeping or suppliers, minimize disruption, promise unavailable units or use compensation to avoid the repair.

If behaviour becomes threatening, follow the property's safety protocol and consult local emergency authorities as the situation requires. Do not expose staff to danger to finish a negotiation.

Follow up without losing the case between shifts

A read message is not proof that service has been restored. A maintenance task marked complete is not enough either. Keep these states separate in your case record:

  • Message read: a read signal exists, but resolution is unconfirmed.
  • Task completed: the person assigned reports that the work is done.
  • Service restored: a check shows that the affected service works again.
  • Guest confirmation: the guest confirms that the remedy works for them.
  • Operational closure: the outcome, outstanding work and its owner are recorded.

1. Set a checkpoint around the agreed action

Choose follow-up timing that matches the remedy. For example, after replacing a remote control, check the result when the guest can test it. If a technician must visit first, agree an update even if the repair remains unfinished. Record who will contact the guest and the agreed checkpoint.

2. Verify use, not assumed satisfaction

Ask a concrete question: “Were you able to turn on the air conditioning with the replacement remote?” If the guest does not reply, record “no response to follow-up”, the contact attempt and any available verification. Do not write “guest satisfied”. Operational closure without guest confirmation can be recorded when you document its basis and any outstanding work.

3. Hand over the case, not just the conversation

Before leaving, record the incoming owner, current status, last promise, next update and missing evidence. Ask the receiving colleague to confirm ownership. Posting in a staff group is not an accepted handover.

Tip: Keep one primary record for each case. Messages support that record; they do not replace it.

Choose a tool your team can maintain

Option Best for Strengths Watch-outs
Paper Teams sharing a reception desk Simple access and face-to-face handover Restrict physical access; updates are manual and remote checking is difficult.
Shared spreadsheet Multiple shifts with digital access A common record with owner filters Limit permissions, avoid parallel copies and assign responsibility for updates.
Software Teams organizing cases and supporting evidence May bring owners, comments and files together, depending on features Check actual permissions and functions; do not assume automatic handovers or duplicate records.

No tool takes over a shift for you. Check that the incoming colleague can access the evidence they need without exposing guest details to the entire team.

Copy the case record and follow-up messages

Keep one internal record per case. Link it to the reservation rather than copying identity documents, payment details or entire conversations. Give the next shift enough information to understand what happened, what you promised and what still needs checking.

Copyable internal case record

Separate the guest's account from facts your team has verified. Mark unknowns as pending rather than filling gaps with assumptions.

Case ID: [reference]
Reservation: [internal reference]
Unit: [unit]
Report time: [date and time]
Guest-reported impact: [description]
Verified facts: [facts and evidence]
Severity: [classification and reason]
Case owner: [name or role]
Agreed next update: [date and time]
Remedy: [action and status]
Approvals: [who approved what, or pending]
Compensation status: [not proposed, pending, approved or delivered]
Verification: [test and result]
Guest response: [response or no reply]
Closure: [status and supporting evidence]
Prevention task: [action, owner and verification]

Illustrative example: access to unit 402

ID: [example case]. Reservation: [reference]. Unit: 402.
Reported: [date and time]. Impact: unable to enter.
Verified: code rejected following the property's access checks.
Severity: blocked access. Owner: night receptionist.
Agreed update: [time]. Remedy: confirmed temporary access option.
Approval: shift lead, following the internal procedure.
Compensation: not proposed; full impact still to be assessed.
Verification: guest confirms entry.
Response: access successful. Closure: access restored; preventive review pending.
Prevention: maintenance lead to investigate the cause and test access.

Guest message templates

Distinguish the guest's report from verified facts, and include only commitments you can keep. These messages do not replace the internal record.

Subject: We have received your report
Hi [name]. You have reported [problem], which is preventing you from [impact]. [Case owner] is checking this. We will update you through [channel] at [agreed time].
Subject: Update on the repair
Hi [name]. The repair is still outstanding, and we cannot yet confirm when it will be complete. We can offer [verified alternative]. Would that work for you? We will update you again at [agreed time].
Subject: Is the service working for you now?
Hi [name]. We have checked [verified result]. Can you confirm whether you can now [use the service]? If the problem continues, please tell us what is happening so we can reassess the case.

Check before saving or sharing

  • Keep internal notes separate from guest messages.
  • Remove personal information you do not need.
  • Restrict access to staff handling or supervising the case.
  • Retain relevant evidence without circulating it in open staff chats.
  • Follow your property's defined retention policy. Check its suitability and your handling of personal data against current guidance from Colombia's Superintendencia de Industria y Comercio. Do not assume there is one universal legal retention period.

Measure recovery and remove the root cause

Measure your response separately from service restoration. Answering a message does not mean the service works again. A refund or the absence of a bad review does not prove that trust has returned.

Metrics you can verify

Use the same definitions across shifts:

  • Time to human acknowledgement: from the guest’s report until a person acknowledges the problem to the guest. An automated reply does not count.
  • Time to service restoration: from the report until you verify that the service works or the agreed alternative is operational. Keep unresolved cases pending. Never enter zero duration or include them as completed cases in restoration averages.
  • Promised updates delivered: updates sent by the agreed time, divided by all updates due during the reporting period. Include updates for cases that remain open.
  • Reopened cases: closed cases reopened for the same problem, divided by cases closed in the period reviewed. Use a consistent review window.
  • Compensation recorded: cases with approved compensation and a documented execution status, divided by all cases with approved compensation. Separate pending, processed and receipt confirmed.
  • Repeated incidents by cause: count new incidents linked to each verified cause during the period. Another update on an existing case is not a new incident.

Illustrative example: access to unit 402

The guest reports being unable to enter. Reception then acknowledges the problem. Later, the receptionist verifies that the guest entered using an authorized alternative. These are three separate events: report, acknowledgement and restoration.

If access works but the guest does not answer your follow-up, record operational closure without guest confirmation, not confirmed satisfaction. Keep the evidence that access worked.

1. Review cases and assign prevention work

  1. Review open, closed and reopened cases regularly. Look for recurring causes, not someone to blame.
  2. Separate a verified cause from a hypothesis. Assign an investigation where evidence is missing.
  3. Create a prevention task with a named owner. For example, correct arrival instructions after an access-code problem.
  4. Define the verification step: have authorized staff test the instructions and access before closing the task.

Tip: Close prevention tasks with evidence, not “all done.”

Do not attribute improved reviews or repeat bookings to recovery work without supporting evidence. Your records should show what changed and how you checked it, not just that someone marked the case closed.

Make the playbook ready for the next shift

1. Fill in the decisions reception needs

Before handing over, turn the playbook into something your team can use without contacting the owner for every case.

  • Name the case owner and backup. Confirm that both understand the outstanding work they are taking on.
  • Fill in approval limits for each role. Separate authority to approve from responsibility to deliver and confirm payment.
  • Verify maintenance, management and backup contacts. Specify who takes over when the primary contact is unavailable.
  • Check the refund workflow for each booking channel and who has permission to use it. Approval does not mean the guest has received the money.
  • Choose a shared record and assign responsibility for updates. The next shift must be able to find the offered remedy, agreed update checkpoint and missing evidence.

Tip: Give every promise an owner. An unattended note is not a completed handover.

2. Rehearse and check the record

  • Rehearse the illustrative access and cleaning cases. Ask reception to explain which verified options they can offer and when approval is needed.
  • Review one completed case for missing evidence: permissions, service checks and the guest's response. Record gaps honestly rather than filling them with assumptions.
  • Schedule periodic policy reviews against actual booking conditions and applicable guidance from Colombia's Superintendencia de Industria y Comercio.

3. Test the handover

Can reception offer a verified next step without the owner? Can the next shift see exactly what was promised? Is the remedy usable for this guest and available to deliver? Can someone show that service was restored?

Practical operations guidance, not legal or tax advice.

ShareWhatsAppLinkedInX