Connect Twilio numbers to your AI voice agent
Bring an eligible voice number from your Twilio account into VoiceForge, assign a published agent and test the routing. If you are looking for Twilio BYOC, first distinguish external-carrier trunking from importing a number that Twilio already hosts.
Better together.
Connect the systems behind every conversation.
A caller asks
Your agent understands the request
A tool responds
Validate permissions and inputs
An action is recorded
Keep the outcome in context
Connection reference: Twilio documentation for Bring Your Own Carrier. Reviewed September 26, 2026.
Twilio number import, Elastic SIP Trunking and BYOC
These describe different setups. Number import connects a number from your Twilio account. VoiceForge uses Twilio Elastic SIP Trunking for its configured voice path. Twilio BYOC connects an external carrier to Programmable Voice; it is not automatically enabled by importing a Twilio-hosted number. If keeping another carrier is essential, confirm the supported architecture before changing service.
Prepare the account and number
Confirm you control the Twilio account and that the intended number supports voice. Record its existing routing and who depends on it. Check account permissions, billing readiness and the VoiceForge workspace before connecting. Use a test number first when changing a business-critical call path.
Connect, assign and test
Connect the Twilio account, select an eligible number and assign the published agent intended for that business. Review the routing status and complete any required configuration. Call the real number from another phone, confirm the correct greeting and test the intended outcome. A successful browser conversation does not verify the carrier path.
Verify booking, transfer and fallback
Test each action you enable using the actual calendar or destination. Check that a booking exists before treating it as confirmed. Test what callers hear when the agent or destination is unavailable and document how staff recover an unresolved request. Measure response time in your setup rather than relying on a universal latency promise.
Keep messaging configuration explicit
Voice routing and SMS are separate workflows. If you need missed-call text-back, configure the messaging-capable number, trigger and reply destination with the responsible provider or CRM. Verify delivery and duplicate handling before offering the workflow to customers.
Understand the charges and launch scope
Review current VoiceForge plan charges alongside Twilio number, carrier and usage charges. Start with one number and one workflow, inspect call outcomes and keep a record of the configuration that passed testing. Confirm external-carrier requirements with support before treating Twilio BYOC as part of that launch.
Questions, answered.
Is importing a Twilio number the same as Twilio BYOC?
No. VoiceForge can connect voice-capable numbers in your Twilio account using its Twilio integration. Twilio Bring Your Own Carrier is a separate product for connecting an external carrier to Twilio Programmable Voice. Do not assume importing a Twilio number configures an external-carrier BYOC trunk.
Do I need to port my number away from Twilio?
For an eligible number already in your Twilio account, the integration configures routing without moving ownership to VoiceForge. Review existing routing before activation because connecting an agent changes where calls go. A number held with another carrier needs a separate compatibility and routing review.
Can I use the same number for voice and SMS?
Check the number capabilities and your messaging configuration. Connecting voice routing does not set up missed-call text-back or reply handling. Test SMS separately with the provider or CRM responsible for messaging.
What about compliance on BYOC calls?
A carrier connection does not remove your obligations for call purpose, permissions, disclosures or opt-outs. Review the rules and platform controls for your intended calls before launch; a successful technical connection is not a compliance determination.
Hear the difference.
Then build your own.
Start with a free workspace. Review your agent. Test before you publish.