2.2 The LEARN Service-Recovery Model

Key Takeaways

  • LEARN is a five-step recovery framework: Listen, Empathize, Apologize, React/Resolve, Notify/follow-up.
  • Listening comes first—interrupting with solutions or excuses escalates frustration.
  • Empathy and apology address emotion; React/Resolve addresses the practical fix within empowerment.
  • Notify/follow-up closes the loop with the guest and, when needed, with teammates so the problem does not recur unseen.
  • Worked scenarios at the front desk, in a restaurant, and at a tourism attraction all follow the same LEARN sequence.
Last updated: August 2026

The LEARN Service-Recovery Model

When something goes wrong, guest-facing staff need a sequence they can remember under stress. LEARN is the recovery framework most widely used across the lodging industry—it originated in major-brand service-recovery training and is now standard vocabulary in hospitality education and CGSP preparation. AHLEI's own element name for this work is Recovery: Turn It Around; LEARN is the step sequence people use to carry it out. It organizes recovery into five steps:

LetterStepCore action
LListenGive full attention; let the guest finish; capture facts and feelings
EEmpathizeShow you understand the impact on this guest
AApologizeOffer a sincere, ownership-based apology
RReact / ResolveTake concrete action within empowerment; escalate if needed
NNotify / follow-upConfirm resolution with the guest; loop in teammates/systems so the issue stays fixed

LEARN is not a rigid script you recite robotically. It is a decision order: emotion and understanding before debate; action after apology; follow-up after the fix. Skipping steps is how recoveries fail even when a discount is offered.


L — Listen

Listening is the most skipped step when associates feel attacked. Under pressure, people jump to defending the property, correcting the guest’s story, or pushing a quick coupon. That usually raises the temperature.

Strong listening behaviors:

  • Stop other tasks when safe to do so; face the guest; open posture
  • Use short acknowledgments (“I see,” “Go on”) without hijacking the story
  • Paraphrase key facts: “So the shower had no hot water and you already waited twenty minutes for engineering.”
  • Ask clarifying questions only after the guest has had space to speak
  • Take notes if the issue is complex (names, room numbers, times)

Weak listening behaviors:

  • Interrupting with “But our system shows…”
  • Looking at the computer the entire time while the guest talks
  • Finishing the guest’s sentences
  • Grouping this complaint with “all guests complain about that”

Listening goals are twofold: (1) the guest feels heard, and (2) you gather accurate details so the fix matches the real problem.


E — Empathize

Empathy is recognizing the impact of the failure on the guest’s trip, meal, or day—not merely restating the fact. Empathy language is specific:

Generic (thin)Empathic (stronger)
“That’s too bad.”“I can see how frustrating it is to arrive exhausted and find the room isn’t ready.”
“I understand.” (said flatly)“Missing the start of the tour after planning this for months would upset anyone.”
“It happens.”“You planned a celebration dinner—this delay is not what you deserved tonight.”

Empathy is not agreeing that every demand is reasonable. You can empathize with inconvenience even while later explaining a policy limit. Empathy is also not saying “I know exactly how you feel” when you do not; focus on the situation’s impact rather than claiming identical personal experience.


A — Apologize

A sincere apology accepts that the guest’s experience fell short. Useful elements:

  • Ownership: “I’m sorry we didn’t have your table ready at the time we quoted.”
  • Specificity: Name the issue rather than a vague “sorry for any inconvenience.”
  • No poison pills: Avoid “I’m sorry you feel that way,” which sounds like blame dressed as apology.
  • No over-explaining yet: A brief apology first; detailed logistics come in React/Resolve.

Apologies can come from the associate who hears the complaint even if another department caused the error. Guests hear “we” as the brand; they do not want a finger-pointing tour of internal silos.


R — React / Resolve

This step turns words into action. React means you respond promptly and visibly; Resolve means you pursue a fair fix.

Typical resolution tools (within property rules):

  • Correct the product (remake, re-clean, repair, rebook)
  • Reduce wait impact (lounge access, complimentary beverage, priority in queue)
  • Adjust the commercial outcome (discount, upgrade, refund portion—if authorized)
  • Provide alternatives when the original promise cannot be kept
  • Escalate with a warm handoff when limits are reached

Resolve with the guest’s goal in mind. Ask: “What would make this right for you?” Sometimes the guest wants speed more than a free item; sometimes they want acknowledgment more than money. Match the remedy to the harm when you can.

Time transparency is part of resolving: “I will return in five minutes with an update” is better than disappearing for twenty. If you must leave the desk, tell the guest when you will be back.


N — Notify / Follow-Up

Notify has two audiences:

  1. The guest — Confirm the fix worked. Check back after the room is cleaned, the entrée is remade, or the next tour departs. Closing the loop shows care beyond the first apology.
  2. The team / systems — Log the issue, tell housekeeping, kitchen, or operations so the same guest is not failed twice, and so patterns can be fixed.

Follow-up is where loyalty is often won. A same-shift “Just checking that the new table is working for your party” or a next-morning “How was the rest of your stay after we moved you?” signals that recovery was genuine, not a performance to end the conversation.


Worked Scenario 1: Front Desk — Wrong Room Type

Situation. Mr. Alvarez booked a king suite with a rollaway for his child. At check-in he receives two queen beds and no rollaway. He is tired and irritated.

LEARN stepAssociate action
ListenLets him finish; paraphrases: king suite, rollaway for child, not what he has now.
Empathize“You’ve been traveling all day and planned space for your child—this isn’t the welcome you booked.”
Apologize“I’m sorry we didn’t deliver the room type you reserved.”
React/ResolveChecks inventory; offers a correct suite when available or a comparable upgrade; arranges rollaway immediately if stay-in-place is temporary; sets a clear ready time.
NotifyAlerts housekeeping and the night team; notes profile preference; checks with Mr. Alvarez after move.

Exam trap: Arguing about whether the website photo matched before any apology. LEARN order says listen and empathize first.


Worked Scenario 2: Restaurant — Allergy Near Miss

Situation. A guest stated a shellfish allergy; a sauce with shrimp stock is served. The guest notices before eating and is upset and scared.

LEARN stepAssociate action
ListenDoes not minimize; hears the allergy concern fully.
Empathize“That’s frightening—you trusted us with a serious allergy.”
Apologize“I’m truly sorry this plate was not safe for you.”
React/ResolveRemoves the plate immediately; informs chef/manager; remakes with verified ingredients; offers a different dish if trust in remake is low; never pressures the guest to “just scrape it off.”
NotifyDocuments allergy on the check and guest profile if appropriate; informs remaining servers; manager follow-up visit.

Safety issues jump the priority queue. Resolve may include manager involvement even if a discount alone would usually suffice for a cold soup.


Worked Scenario 3: Tourism Attraction — Missed Timed Entry

Situation. A family holds 2:00 p.m. timed tickets. Due to an earlier mechanical delay, they are still outside at 2:35. Children are hot and restless; parents blame the ticket desk.

LEARN stepHost action
ListenHears the timeline and the kids’ discomfort without interrupting.
Empathize“Waiting in this heat after planning your afternoon is exhausting—especially with children.”
Apologize“I’m sorry the entry window didn’t match what you were promised.”
React/ResolveExplains the operational delay briefly; offers next available entry or priority line if policy allows; provides water or shaded waiting if available; explores reschedule options for same-day return.
NotifyUpdates entry system notes; radio to gate staff; follows up once the family is inside (“Glad you’re in—enjoy the rest of your visit”).

Common LEARN Failures on Exams and on the Floor

FailureWhat it looks likeBetter
Solution before listening“Here’s a free dessert” while guest is mid-sentenceFinish listening; then resolve
Empty apology“Sorry you feel that way”“I’m sorry we got this wrong”
Resolve without notifyFix once, never check backConfirm satisfaction; log the issue
Empathy as agreement to everythingPromising free nights you cannot authorizeEmpathize, then resolve within limits or escalate
Defensive listeningFact-checking every detail firstFacts after connection

How LEARN Maps to Guest Service Gold

Recovery—Turn It Around—is the Guest Service Gold element. LEARN is a how-to sequence for that element. On the CGSP exam, when a scenario asks what the associate should do first, prefer listening and acknowledging over arguing policy. When it asks what completes recovery, include follow-up/notify, not only the free item. Memorize the five letters in order; practice attaching one concrete behavior to each letter so you can apply them under timed questions.

Test Your Knowledge

In the LEARN model, what does the “N” step primarily require?

A
B
C
D
Test Your Knowledge

A guest begins describing a long check-in delay. The associate immediately says, “Our computers are slow for everyone—here’s a free drink coupon.” Which LEARN mistake is this?

A
B
C
D
Test Your Knowledge

Which statement best reflects the React/Resolve step?

A
B
C
D