June 12, 2026 • 4 min read
AI & Automation Specialist
I design AI-powered communication systems. My work focuses on voice agents, WhatsApp chatbots, AI assistants, and workflow automation built primarily on Twilio, n8n, and modern LLMs like OpenAI and Claude. Over the past 7 years, I've shipped 30+ automation projects handling 250k+ monthly interactions.
If you enjoy the content that I make, you can subscribe and receive insightful information through email. No spam is going to be sent, just updates about interesting posts or specialized content that I talk about.
You bought a US number, opened the Twilio Console, and hit a wall of products you never asked for. The number sits there doing nothing, and every guide assumes you already know which of the twenty menu items you actually need.
This guide takes you from that exact point to a Flex instance you can call and text, with a real agent picking up. It is the path from a raw number to a working contact center, written from production and not from the docs team. The screenshots walk each step, and the parts that trip people up (the ones that look like bugs and are actually settings) are called out where they happen.
I run Twilio communication systems in production, including one that handles around 3000 messages a day, so the gotchas in here are the ones that cost me real time, not theoretical ones.
The guide covers the whole chain, in order:
If you bought a Twilio number and have no idea what to do with it next, this is written for you. It is also for the developer evaluating Flex before putting a client on it, and for the founder or team that wants the real cost and the real constraints before committing, not the sales version.
It is not a Flex plugin or customization guide. It stops at the point where inbound voice and SMS work, which is exactly where most people are stuck.
No. Voice works almost immediately, but a US long code cannot send SMS to US phones until it is registered under A2P 10DLC. Unregistered US-bound messages are not delayed, they are blocked, and you get error 30034. The guide shows you how to tell whether this is your problem.
For voice, no. For US SMS through A2P 10DLC, you need a US tax ID (EIN). There is a Sole Proprietor option that works with a US address, but it allows only one number per campaign. If you are outside the US with no EIN, that is the wall to plan around, and the guide explains your options.
There is a free development plan that includes a block of free active user-hours per month, enough to build and demo a real setup. Production runs on either pay-per-use, charged per active user-hour, or a flat per-seat subscription with unlimited hours. The guide breaks down all three and which one fits which usage pattern.
Yes, for the part this guide covers. Wiring your number into Flex for inbound voice and SMS is Console and Studio configuration, no code required. Custom plugins and deeper customization come later and are out of scope here.
Campaign review runs roughly 10 to 15 days. If you need US SMS, start the registration first so it is approving in the background while you set up the rest.
Almost always one of three things: you are not set to Available in the Flex UI, your number points at the wrong Studio Flow, or that flow does not end in the Send to Flex widget. The guide has the full checklist.
Grab the full PDF, follow it end to end, and you will have inbound voice and SMS working on the number you already paid for.