Connect Twilio without porting
Connect your Twilio account, import the numbers this workspace should manage, assign a published agent, and activate ElevenLabs routing in a few steps.
Describe & review
Make the instructions your own
Test a conversation
Hear it before you launch
Publish a version
Improve from real outcomes
Keep your Twilio account
Your existing numbers, billing, caller ID reputation, and ownership stay in Twilio. VoiceForge only configures the call path for numbers you select.
Simple Twilio number connection
Connect a customer-owned Twilio number, assign an agent, and let VoiceForge configure inbound and status webhooks. Calls route to ElevenLabs with no Agent Spec changes.
Global routing & compliance
Apply consent, calling-window, DNC/DND, opt-out, AI disclosure, and recording-notice checks before an outbound call is created.
No port, no lock-in
No number port is required. Start with one Twilio number, keep the rest unchanged, and activate more numbers when each agent is ready.
Cost control at scale
Use your negotiated per-minute rates, keep flat VoiceForge plans for the agent, and see telephony vs AI cost separated — predictable margin for agencies at scale.
Questions, answered.
Do I have to port my numbers to use VoiceForge?
No. The number stays in your Twilio account. VoiceForge configures its call webhooks — no port, no downtime, and no caller ID change.
Which phone provider is supported first?
Twilio is the supported production path for this release. Additional carriers can be added through the provider adapter after their routing and signature validation are implemented.
How does SIP trunking compare to Vapi telephony?
VoiceForge is BYO-first: connect Twilio, import a number, assign a published agent, and activate it. The number stays in your account and the Agent Spec needs no rewrite.
Hear the difference.
Then build your own.
Start with a free workspace. Review your agent. Test before you publish.