Nova Wholesale BridgeThe AI voice market is moving fast enough that any platform you pick today is unlikely to be the one you want in eighteen months. Models improve, pricing changes, vendors get acquired, and something you have never heard of turns out to be better at your specific use case.
That is not a reason to wait. It is a reason to build so that changing your mind is cheap.
Two things that get bundled and shouldn’t
An AI voice deployment has two distinct layers:
The agent layer. The model, the voice, the prompts, the conversation logic, the tooling. This is where your product lives and where the market is moving fastest.
The telephony layer. Numbers, trunks, routing, carrier relationships, call records, compliance registrations. This changes slowly and is genuinely annoying to move.
Some vendors will happily sell you both. It is convenient, and for a pilot it is fine. The problem arrives when you want to change the agent layer and discover the telephony layer is attached to it.
What being locked in actually costs
If your numbers are issued by your agent vendor, switching means porting. Porting takes days, needs documentation, and is a project rather than a decision. In practice teams do not switch. They stay on a platform they have outgrown because moving means renegotiating their phone numbers.
Beyond the numbers:
- Your call records live in their system, so historical analysis does not come with you
- Your compliance registrations are tied to their numbers
- Your routing logic is expressed in their product’s terms
- Pricing conversations are one-sided, because they know what leaving costs
None of that is malicious. It is just what happens when two layers get merged.
Why we deliberately do not do the agent layer
We carry voice traffic. We do not build voice agents, and we are not planning to.
That is not modesty, it is positioning. Because we have no agent product, we have no incentive to make one platform work better than another, and no reason to make leaving difficult. ElevenLabs, Vapi, LiveKit, Retell and a custom build all connect the same way, over SIP.
If you switch platforms, you repoint the trunk. Your numbers, routing, call records, and carrier relationships stay exactly where they are. The switch is a configuration change rather than a migration.
What that looks like in practice
- One number, any agent. A DID can point at whichever platform you are using this quarter.
- Run two at once. Split traffic across platforms to compare them on real calls rather than demos. Genuinely the fastest way to evaluate.
- Fall back to humans. The same trunk can route to a queue when an agent is unavailable or a caller asks for a person.
- Keep your own records. CDRs come from the carrier layer, so your call history is continuous across platform changes.
The test worth applying to any vendor
Ask: if we leave you in six months, what do we have to move?
If the answer is “your prompts”, that is a healthy dependency. If it includes your phone numbers, your call history, and your compliance registrations, you are not choosing a platform, you are choosing a landlord.
Try it against something else
If you are evaluating agent platforms, we will set up a trunk and a number you can point at any of them, including two at once. Compare on your own traffic rather than on anyone’s demo.