A support request may need more than one specialist, but the requester should not have to coordinate the transfer. When responsibility moves between teams, retain the original context and make the next owner explicit. A forwarded email by itself is not a completed handoff.
Package the useful context
Include the equipment identity, reported observation, authorized actions already taken and the reason for transfer. Link to the original ticket and approved supporting records. Avoid asking the requester to repeat details already captured accurately. If important information is missing, identify who will obtain it instead of leaving the receiving team to infer the gap.
Confirm receipt and the next step
Have the receiving team acknowledge the handoff through the established support process. Tell the requester which contact route now applies and whether the original reference remains in use. Keep coordination responsibility clear if several teams are contributing. At resolution, connect the outcome to the original request so the history does not end at the transfer. Review requests that move repeatedly for an unclear scope or ownership boundary.
Practical takeaway
Transfer the record and the responsibility together. Keep one understandable route for the requester even when several specialists are involved.