What did the next teammate hear?
A fictional interview asks you to hand over two ordinary welcome-area requests.
The question
One guest request is complete. Another guest asked for an optional memento. Its availability is pending with the service lead. The next internal check is at 16:10.
- Welcome guideComplete.
- Optional mementoPending with the service lead. Internal check at 16:10.
“What should your teammate know before taking the handoff?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Separate the statuses
What would you do here? Open the move you’d make.
Give the status of each request
The strong move. This distinguishes completed work from the open item.
Describe both requests as complete
Tempting, but it misses something. The lead has yet to confirm availability for the memento.
Report only the completed request
Tempting, but it misses something. The teammate would miss the pending item.
See how a strong candidate says it
“One request is complete. The optional memento request is still pending.”
Why it works: The teammate needs to know which request still needs attention.
Step 2: Name the owner
What would you do here? Open the move you’d make.
Name the service lead and the internal check time
The strong move. That gives the teammate a clear next action.
Say the memento will arrive at 16:10
Tempting, but it misses something. The packet gives a check time only.
Ask the guest to confirm availability
Tempting, but it misses something. The service lead owns that decision.
See how a strong candidate says it
“The service lead owns the availability check. The next internal check is at 16:10.”
Why it works: The handoff gives the teammate an owner and a next check.
Step 3: Correct the repeat
Your teammate replies, “I’ll tell them the memento is confirmed for 16:10.”
What would you do here? Open the move you’d make.
Correct the pending status and check time
The strong move. The two facts keep the handoff accurate.
Let the teammate promise 16:10
Tempting, but it misses something. The availability decision is still pending.
Remove the check time from the handoff
Tempting, but it misses something. The teammate still needs to know when to check.
See how a strong candidate says it
“It is still pending. 16:10 is the next internal check. The service lead has yet to confirm availability.”
Why it works: The teammate confused the time of a check with a confirmed offer.
Step 4: Check the handoff
What would you do here? Open the move you’d make.
Ask the teammate to repeat the status and time
The strong move. The answer shows whether the correction was understood.
End after saying you passed it on
Tempting, but it misses something. The teammate’s earlier reply showed a misunderstanding.
Send the guest an availability promise yourself
Tempting, but it misses something. The lead still has the availability decision.
See how a strong candidate says it
“Could you repeat the status and the next check time? The request is pending, and we check with the lead at 16:10. The assigned person can update the guest after confirmation.”
Why it works: This gives the teammate a chance to repeat the two facts accurately.
The answer, in short
- Decision
- Correct the misunderstanding and check what the teammate heard.
- Because
- 16:10 is an internal check time. The request remains pending.
- What would change it
- A confirmed availability update from the lead would change the guest message.
Common traps
- Keep the status and check time separate.
- Ask what the teammate heard.
Check your answer
- I separated both requests.
- I named the owner.
- I corrected the promise.
- I checked the handoff.
Last reviewed Nov 11, 2026