<?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/5b9e27b7ef714b50a56305cb84430b84&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5b9e27b7ef714b50a56305cb84430b84-fe10adebf60b7dbb.gif</thumbnail_url><duration>162.366667</duration><title>Every dynamic variable in voice agent needs a fallback</title><description>This Loom explains why every dynamic variable in an agent prompt should include a fallback mechanism. It contrasts prompt A, where unresolved placeholders for current date and time, next appointment, and account balance cause the agent to read variable names, making the conversation sound robotic. It then shows prompt B with fallback responses for each dynamic variable so the agent says something else when values fail. The video demonstrates the improved spoken flow when current time, next appointment, and account balance cannot be resolved at runtime.</description></oembed>