Practical guide • Blink editorial team
When a request changes teams, who owns the next step?
A practical handoff review for finding missing context, unaccepted work and customer updates that fall between teams.
Published 3 October 2026
Follow the request across the boundary
Many service problems become visible when work moves between support, a branch and a specialist team. Each team may complete its own step while the customer still has no answer. Choose one journey and draw the transitions. Record what the sending team believes it has completed and what the receiving team needs before it can act. These two definitions often differ. A handoff review makes the difference explicit, so the discussion can focus on the procedure rather than on which team worked harder.
Define acceptance separately from sending
An email sent or a ticket reassigned is evidence of dispatch. It is not necessarily evidence that the receiving role accepted the work. Define how acceptance becomes visible in the tools you already use. The recipient may need to confirm ownership, identify missing information or reject a request that reached the wrong queue. Make rejection informative: explain the missing condition and the correct route. Otherwise the sending team may repeatedly forward the same incomplete request while the customer waits for an action that has not started.
Preserve the context that changes the decision
A good handoff describes the customer's intended outcome, relevant facts, checks already completed and the decision still required. It should not force the next colleague to reconstruct the entire conversation, nor include every available detail without purpose. For an illustrative booking change, the receiving team may need the current booking reference, requested change and any eligibility check already performed. Agree the actual fields with the people who use them. Verify information where necessary and avoid carrying personal details into channels that do not need them.
Keep customer communication owned
The team performing the internal task and the team updating the customer may be different. Name both responsibilities. An advisor should know whether to wait for the specialist's decision, provide a progress update or explain that further information is required. Internal uncertainty should not become an unsupported promise. If the specialist cannot act, define who communicates the revised next step. The customer should not need to identify your organizational boundaries or call each department to discover where the request has gone.
Test the exception, not only the normal route
Review what happens when the receiving role is absent, the case arrives outside operating hours, a system is unavailable or two teams disagree about ownership. Decide who resolves the disagreement and where the request remains visible meanwhile. Do not insert arbitrary escalation deadlines; use the operating commitments agreed for the journey. Run the same scenario with the people on both sides of the boundary. Differences in their interpretation identify what the procedure still needs to clarify before it becomes reliable in daily use.
Turn the review into a bounded improvement
Write the observed gap, the proposed change, its owner and how you will check it. A useful improvement might be an acceptance step, a clearer queue rule or a standard context field, depending on the evidence. Review subsequent cases to see whether the customer made progress and whether colleagues understood the responsibility. Public online discussions about transfers provide examples of frustration, not a measurement of your own operation. Blink CX Pulse can help establish a journey map, gap analysis and baseline. Begin by describing the transition that seems unclear and the decisions the diagnostic work should support.
Sources and further reading
- GOV.UK: Understand users and their needs
- Public discussion: channel conversations losing context (anecdotal)
References consulted during preparation in October 2026. The guidance is editorial advice, not Blink client results or service commitments.