Operating note · 3 min read
Why “we’ll get back to you” is not a handoff
A handoff is a structured transfer of context and responsibility. A vague promise simply gives both the customer and the team another thing to wait for.
What the receiving owner needs
- Who the customer is and what they want to hold or decide.
- What has already been said and which facts are confirmed.
- The decision or approval now required.
- Any timing constraint or customer expectation.
What the customer needs
They should know who is checking the point, when they will hear back, and what happens next. This is especially important when the issue is availability, a pricing exception, or a special request.
A useful pattern: “I’m checking that with our events manager now. I’ll update you here by 4pm today. If it is available, would you prefer a Wednesday or Thursday viewing?”
What to avoid
Do not forward a screenshot without context. Do not use a group chat as the only record. Do not give the customer a time promise that nobody owns. A simple written handoff record prevents all three.