> ## Documentation Index > Fetch the complete documentation index at: https://docs.incident.io/llms.txt > Use this file to discover all available pages before exploring further. # Reassigning escalations > Move an escalation to different responders, either manually or automatically. Every reassignment works the same way. The original escalation stops, and a new one starts against the new targets, linked to the one it came from. The new escalation is genuinely new rather than a continuation, so it starts at the beginning of whatever it was sent to and follows that target's own levels, branches, and working hours. Acknowledging it is what stops the paging. ## Two ways to reassign A person can reassign an escalation when it reaches the wrong team, and an escalation path can be built to reassign on its own when nobody acknowledges. Redirect a live escalation to the right people, from the dashboard, Slack, Microsoft Teams, or the mobile app. Add a Reassign step to an escalation path, so an unacknowledged escalation hands over to another path. ## How they differ | | Manually | Automatically | | ----------------------- | --------------------------------------------- | --------------------------------------------- | | Who starts it | Someone responding to the escalation | The escalation path, when nobody acknowledges | | Set up in advance | Nothing to set up | A **Reassign** step on the path | | Can be sent to | An escalation path, users, or a Catalog entry | Another escalation path | | The original ends up as | **Reassigned**, and resolved if you choose to | **Expired**, because nobody acknowledged it | The difference in that last row is the one worth remembering. A manual reassignment is somebody deciding to redirect a page, so the original is closed out deliberately. An automatic one is the path running out of people to try, so the original expires. See [escalation statuses](/on-call/escalation-statuses) for what each status means. Reassigning is different from **Escalate to next level**, which advances the *same* escalation to the next tier in its existing path. A reassignment always creates a new escalation.