<?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/45f6e3ed650c4620aa3949e53cb86760&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/45f6e3ed650c4620aa3949e53cb86760-b27e381b5bf105ea.gif</thumbnail_url><duration>1468.666667</duration><title>Programmable Phone Numbers for Voice AI</title><description>This Loom explains why voice AI requires a programmable phone number instead of a regular mobile or landline number. It describes how programmable numbers are virtual, software controlled resources in the cloud that can be configured through APIs and routing logic, often via SIP trunking and webhooks for AI interactions. The video compares buying numbers through a retail AI platform versus purchasing directly from carriers like Twilio or Telnix, emphasizing trade offs in portability, carrier level API control, and long term dependency on the platform. It also recommends controlling the carrier account that owns the number and choosing local, voice capable numbers that match the recipients, with one dedicated number per inbound voice AI agent. In the end, it stresses verifying current number availability, per minute rates, regulatory requirements, porting rules, and platform connectivity before committing.</description></oembed>