The everyday problem
A broad phrase such as end-to-end support can leave both teams with different expectations. The daily work still needs explicit boundaries. Scope should explain which tasks are included, which decisions remain internal, and how unfinished work moves between the two organizations.
A practical approach
Define tasks, queues, systems, and completion criteria in operational language. Include exclusions and examples of edge cases. Review the scope with the staff who will manage the handoff so that unclear responsibilities surface before the engagement starts.
Try this with your team
Take one task in a draft scope and describe its input, output, owner, and stopping condition. Ask both teams to confirm the same interpretation.