A loyalty program lives at the front desk. That's usually where it dies
We've seen programs with brilliant 80-page strategy docs, properly built tiers, three-year economics — that died six weeks after soft-launch.
The reason is always the same: the front desk didn't know what to say to the guest. When the guest asked "what do I get?" — the answer was "we have a loyalty program, ask the manager". When the manager wasn't around — the guest walked away uninterested. The program became invisible.
Where it breaks in practice
Scenario 1: Check-in
Guest arrives, holds Silver status. The front desk doesn't know that:
- Silver gets priority for upgrade when available
- Silver gets a welcome drink at the bar
- Silver shows a tier badge in the system right in front of the receptionist's eyes
None of it activated — the guest doesn't feel the difference. A year later they think: "Why am I in this program? I got nothing."
Scenario 2: Check-out
The guest is leaving. This moment is the most important communication touchpoint of the year: tell them how many points they earned, total balance, what's needed to reach the next tier.
If the front desk says "thank you, goodbye" — the program is invisible. If they say "you've earned 4,580 points, you're 6 nights from Gold, book your January stay now" — that's retention in action.
Scenario 3: A complaint
Guest is unhappy. The loyalty program has a "service recovery" mechanism: front desk can issue compensation points instantly (e.g. up to 2000 without escalation).
Most hotels never configure this. The complaint escalates to a manager, the guest leaves frustrated. With a playbook and authority at the front desk — the complaint is defused in 2 minutes and becomes a loyalty story.
What must be in the operations playbook
1. Scripts for 8 common scenarios
Check-in (gold tier), check-in (new member), check-out, complaint, points dispute, opt-out, gift-status request, family account.
Each script — 3-4 sentences with concrete words. Not "tell them about the program", but "'Mr Smith, as our Gold guest, we've prepared a suite one floor up. If it works for you, we can settle you in right now.'"
2. Authority matrix
Who can issue compensation points? Who can credit points manually? Who can change a tier?
Without a clear matrix — all questions go to the GM. GM is overloaded. Does nothing. Program dies.
Right approach: front desk 0-2000 pts (no escalation), supervisor 0-10000 pts, manager 0-50000, GM beyond.
3. Tier-aware system prompts in the PMS
When a guest is in the system, the PMS should show the front desk:
- Tier (big badge)
- Preferences (diet, room temperature, favourite floor)
- Progress to next tier
- Date of last visit
- 3-4 conversation hooks: "usually books in March", "anniversary Feb 14"
4. Daily huddle template
Every morning — 5-minute huddle: "today we're checking in 2 Gold and 1 Platinum, X, Y, Z prepared for them. One guest has an anniversary."
Without this huddle, tier info is useless — the receptionist can't access it during check-in because they don't remember.
5. Monthly KPIs for the front desk
What we measure:
- % of guests whose tier is mentioned at check-in (target: 95%+)
- % of check-outs with points mention (target: 80%+)
- Average compensation pts per complaint (target: minimise)
- % of gift-status registrations on the spot (target: 40%+ of eligible)
What we do in the implementation phase
We stand up the platform — that's technical tasks. In parallel (not sequentially!) we write the operations playbook for the front desk, run 2 three-hour training sessions with scripts and role-play, set up a metrics dashboard for the GM, run weekly check-ins for the first 6 weeks after launch.
This isn't extra. It's part of launching. Without it, a technically perfect program becomes a dead asset — the software works, but nobody uses it.
The most common component of our project that surprises hoteliers is that we actually run training sessions and write scripts. Most loyalty software vendors consider this "outside their scope". We consider it the single most important scope.
