Record the current state, not just the history
A long ticket thread does not necessarily show what the next person should do. Summarize the reported issue, the checks already completed, the current customer impact and the next agreed action. Keep observations separate from assumptions that still need investigation.
Make escalation usable
Document which issues the incoming team can handle and which require another owner. An escalation should include a contact route, the circumstances for using it and the information the recipient needs. Review those details when staffing or service responsibilities change.
Close the loop with the customer
Agree who sends the next update and when it is due. If the work is waiting on a customer, vendor or internal approval, say so in the handover. Clear ownership of the next communication helps prevent a technical investigation from becoming a silent queue.