What I built on it
- An AI receptionist product on a Hawaii number. The line ran from spring 2026 until I shut it off on September 5, 2026.
- A second number in July 2026 for a demo of a home-services booking agent. I ran scripted test calls against it to try to break the agent: a caller reporting a gas smell mid-booking, a caller reading a phone number digit by digit, a caller going silent.
- Text messaging code inside a spa booking tool and a small CRM.
- A two-way texting add-on for Pipedrive where each customer brings their own Twilio account. I built it and never deployed it.
How a live AI call is wired
A call hits your Twilio number. Twilio asks your server what to do, and your server answers with a short XML reply that says "open a stream." Twilio then holds a WebSocket open to your server and pushes the caller's audio through it as 8 kHz mu-law, the same encoding phone networks have used for decades. Your code sends audio back down the same socket.
Things that cost me time:
- Custom parameters you attach to the stream do not arrive in the WebSocket URL. They arrive inside the first
startmessage. - To let a caller interrupt the agent, you send a
clearmessage, which dumps whatever audio Twilio has queued. Without it the agent talks over people. - I send audio in 640-byte chunks, which is 80 milliseconds each at phone quality.
- When I added the second number, the first one broke. My lookup matched a number against one config field and my setup code wrote it to another. The first line had only ever worked because it was the only one, through a default I forgot existed. One tenant hides a lot of bugs.
The numbers that keep billing
A local number costs $1.15 a month whether or not anyone calls it. That sounds like nothing. Then you write an account-deletion feature.
My first version deleted the customer's channel record from my database and stopped. The number stayed rented on my Twilio account with no record pointing at it. I caught it reading the code before release. Every customer who left would have cost me $1.15 a month forever, with no way to tell which numbers were dead short of an audit. The fix is a release call to Twilio before the delete, written so that "already gone" counts as success.
Texting: the part that never shipped
US carriers require businesses to register before they text from a regular 10-digit number. The program is called A2P 10DLC. You register a brand, then a campaign that describes what you will send, and carriers review it.
My brand was approved. My campaign was still marked in progress on April 22, 2026, and it never cleared while the product was live. I took SMS out of the marketing copy instead of promising a channel I could not turn on. If texting is the core of your product, start registration the day you start building. Budget weeks.
Twilio's current fees for it: $4.50 one-time for a low-volume brand or $46 for a standard one, $15 one-time to vet each campaign, then $1.50 to $10 a month per campaign depending on use.
US prices on November 14, 2026
| Item | Price |
|---|---|
| Inbound call, local number | $0.0085 per minute |
| Outbound call, US | $0.0140 per minute |
| Inbound call, toll-free | $0.0220 per minute |
| Local number | $1.15 per month |
| Toll-free number | $2.15 per month |
| Media Streams | $0.0044 per minute |
| ConversationRelay | $0.07 per minute |
| Call recording | $0.0025 per minute |
| SMS, each way | $0.0083 per segment plus carrier fees of $0.0025 to $0.005 |
For an AI agent built on Media Streams, the Twilio share of an inbound minute is $0.0129. On my line, speech and the model cost more than the phone call did. The full per-minute math is on the voice platform comparison.
ConversationRelay is Twilio's newer option. Twilio handles speech recognition and voice, and your server only exchanges text. I priced it for a project in October 2026 and did not build on it, so I have no field notes.