Bring Your Own Twilio & Tool Failure Notification System
Quick update on what we shipped today. We made serious progress on the Bring Your Own Twilio (BYOT) rollout. Agencies can now connect their own Twilio account, pull their numbers in, and assign those numbers to the correct workspace instead of dumping everything into a confusing pile. We also added workspace-level Twilio connections, so if a client wants to bring their own Twilio account, they can do that inside their own workspace the way it should have worked from the start. You can purchase numbers 3 ways on our platform now: 1. Platform Numbers provided by Automation Studios 2. Agency BYOT Integration (agency supplied numbers to clients) 3. Client BYOT Integration (client supplies their own Twilio account) We also cleaned up number visibility across the platform. Ownership is clearer, imported numbers are easier to identify, and we fixed multiple issues around assignment, unassignment, workspace routing, and outbound AI calling. We also uncovered a deeper edge case while testing live, which is exactly why we test this stuff in the real world and not just in theory. At the same time, I'm building out a failure system. The goal is simple: when something breaks, it needs to fail clearly, surface the real problem fast. Better recovery, better guardrails, better visibility.