video1.0<iframe src="https://www.loom.com/embed/53b7c94361e04f4bba03267a675b82a8" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/53b7c94361e04f4bba03267a675b82a8-2d519d250db72427.gif163.037This Loom explains the new feature for re-assigning escalations when someone receives a page but the issue should be handled by another team or person. When an escalation initially pages Ed but he is unavailable and it pages the presenter instead, the presenter can acknowledge it or re-assign it. The Loom notes that re-assigning is also possible from Slack, where the product asks who to route to and reuses any custom Escalate form setup, including searching for escalation paths, users, features, or services. It also mentions the escalation context is pre-filled from the original alert, with an option to rename it before handing off.