Your numbers, Bland's voice stack.
Bland runs transcription, the language model, and speech on its own infrastructure, so agents on your Twilio numbers respond in 200 milliseconds with no third-party AI provider in the call path.
Bland + Twilio
Keep your Twilio numbers and run them on Bland's self-hosted voice stack: agents answer in 200ms, and your Messaging Service keeps handling SMS.
What Bland does inside Twilio.
Keep your Twilio numbers.
Generate an encrypted key from your Account SID and Auth Token, and the numbers in that Twilio account show up in Bland, ready to import from the dashboard or the API.
Outbound calls on your caller ID.
Pass the encrypted_key header on a Send Call request with your Twilio number as from. Leave from empty and Bland picks one of the imported numbers for you.
Inbound calls answered by an agent.
Upload your Twilio numbers as Bland inbound numbers and attach a pathway or persona. Calls to the number customers already know reach the agent.
SMS on your Messaging Service.
For bring-your-own numbers, register the A2P campaign in Twilio and enter the Messaging Service SID, which starts with MG, in the number's messaging settings.
Geo permissions stay in Twilio.
International calling on imported numbers follows the Geo Permissions of the Twilio account they came from, so that policy lives where it already does.
How it deploys.
Copy your Twilio credentials.
In the Twilio Console, copy your Account SID and Auth Token, and confirm the numbers you want are active in that account.
Generate an encrypted key in Bland.
In the Bland dashboard, go to Add-ons, then BYOT, and generate a key from your SID and token. Save the encrypted_key right away; it is shown once, for security.
Import your numbers.
Select the Twilio numbers listed under BYOT and import them, or use the Create Encrypted Key and Upload Inbound Phone Numbers endpoints.
Test both directions.
Send a call with the encrypted_key header and your Twilio number as from, then dial the number to check that the inbound agent answers.
Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.
Drop Bland into your editor.
MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.
curl -X POST https://api.bland.ai/v1/calls \
-H "Authorization: $BLAND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+14155552120",
"task": "Qualify refi lead",
"voice": "june"
}'
Frequently asked questions.
Can I use my existing Twilio phone numbers with Bland?
Yes. Generate an encrypted key in Bland from your Twilio Account SID and Auth Token, then import the numbers from the BYOT page or through the API. Calls then run on your existing numbers while Bland runs the voice agent.
How do I place an AI call from a Twilio number?
Include the encrypted_key header alongside your Bland API key on the Send Call request, and set from to the imported Twilio number. If you leave from empty, Bland picks one of that account's imported numbers automatically.
Can Bland send SMS through my Twilio account?
Yes, with Enterprise messaging. Register your A2P campaign in Twilio, then enter the Messaging Service SID on the number in Bland. Numbers bought from Bland are linked to a Messaging Service for you, so this step only applies to your own numbers.
How do international calls work on imported Twilio numbers?
Imported numbers inherit the Geo Permissions of their Twilio account, so the calling policy you already manage in Twilio carries over. Enable the destination country in Twilio's voice Geo Permissions and the agent can call it.
Do I need a Twilio account to use Bland?
No. You can buy numbers from Bland, and per-minute pricing already includes telephony. Connect Twilio when you want to keep numbers, caller ID, or messaging setup you already have there.
Should I connect Twilio or a SIP trunk?
Connect Twilio if your numbers already live there and you want them in Bland quickly. Use a SIP trunk if calls run through your own carrier, PBX, or contact center and you need DIDs, extensions, or transfers back over SIP.
Related integrations.
See every integration on the integrations hub.
With our team
Our FDE team scopes the integration with you.
They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.
On your own
Or drop Bland into your editor.
The Bland MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly. Free sandbox, no credit card.