<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/8f000286ab004ea4a5ef9270a8fa71a5&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/8f000286ab004ea4a5ef9270a8fa71a5-004b012156750a3a.gif</thumbnail_url><duration>235.233333</duration><title>Primary &amp;amp; Secondary On-Call | Better Stack</title><description>In this video, I walk you through the best practices for setting up on-call calendars, specifically focusing on a primary and secondary uncle system, also known as L1 and L2. I demonstrate how to create an escalation policy that automatically alerts the primary on-call person first and escalates to the secondary if the incident isn&apos;t acknowledged within 15 minutes. You’ll see how to link these calendars and set up notifications for high-severity alerts. I encourage you to check out our dedicated video on scheduling on-calls for more detailed guidance. Please take action by reviewing your current on-call setup to ensure it aligns with these best practices.</description></oembed>