The Service Standard That Conflicts With the Script
Your full-service hotel has a brand standard requiring agents to answer the phone within three rings and to use a scripted greeting that includes the brand name, the agent's name, and an offer of assistance. During a sold-out convention week, the desk is handling a line of 9 guests, a group check-in of 40 arriving in 20 minutes, and a phone queue of 14 calls. An agent, Dev, has been skipping the script to clear calls faster and has been answering in two rings; his call-handling time is 40% faster than the team's. A guest at the desk complains that Dev 'didn't even say the hotel name' and seemed rushed. The brand shopper is scheduled this week.
1. Is Dev's shortcut a service failure, a reasonable adaptation, or both? Reason it through against the purpose of the standard.
Read the worked answer
Separate the standard's purpose from its form. The purpose of the three-ring rule is to keep callers from abandoning and to signal that the hotel is responsive; the purpose of the greeting is to orient the caller and create a human connection. Dev's two-ring answer serves the first purpose better than the standard. His skipped greeting serves it worse - the desk guest's complaint shows the cost: the caller/guest doesn't know who they reached or feel acknowledged.
So it's both: a defensible adaptation on speed and a genuine failure on acknowledgment. The reasoning to state: when a standard's form conflicts with its purpose under load, the right move is to protect the purpose, not to abandon the standard wholesale. Dev optimized for throughput and dropped the element that carries the relationship. The fix isn't 'follow the script exactly' or 'ignore the script' - it's identifying which parts are load-bearing (name, hotel, offer of help) and which can be compressed under pressure.
2. What do you tell Dev, and what do you change about the standard's application during peak?
Read the worked answer
To Dev: recognize the speed - his throughput is real and useful - then name the gap: the guest couldn't tell what hotel she'd reached or that he was listening. Give him a compressed version for peak: hotel name, his name, and 'how can I help' in a single breath, no filler. That preserves the load-bearing elements while honoring his efficiency.
For the standard's application: define a peak-mode protocol - full greeting when the queue is under a threshold, compressed greeting above it - and make sure the brand shopper window is covered by the full version. Brief the whole team on the same protocol so Dev isn't singled out as the one who broke a rule while others quietly do the same.
The principle: standards should specify the non-negotiable core and allow documented flexibility at the edges. Undocumented flexibility becomes inconsistency; documented flexibility becomes a service culture.
3. The desk guest who complained is still at the desk. How do you recover her in the moment without undermining Dev?
Read the worked answer
Step in without contradicting Dev in front of her. Acknowledge her directly: 'I'm sorry - you should have heard the hotel name and felt welcomed, especially after waiting in that line.' Take ownership at the property level rather than blaming the agent. Then give her something concrete: expedite her check-in, confirm her reservation details, and offer a small gesture appropriate to the wait (a beverage, a late checkout if available).
After she leaves, debrief with Dev privately - not as discipline but as a shared look at the moment: what did she need, and what would have met it in five seconds? The principle: recover the guest in public, coach the agent in private. Undermining Dev at the desk would damage his standing with the team and teach him to hide mistakes rather than fix them.