Tenant-safe routing
Each Vapi endpoint resolves cleanly to the right org, client, or location before downstream automation runs.
Vapi integration live now
Vapi, with a real control layer.
Vapi handles the voice experience. Voxfra handles the routing, tenant isolation, operational context, and downstream stability that serious deployments need.
Why this matters
Vapi is the conversation layer. Voxfra is the operating layer.
Teams usually discover they need this when call handling works but the surrounding operation starts to bend: more tenants, more locations, more reporting, more workflows, more risk.
Stable metadata envelope
Every event carries the same operational context so workflows, analytics, and audit trails do not depend on brittle ad hoc lookups.
One control plane
You keep Vapi where it belongs while Voxfra owns routing, governance, and the operational boundary around it.
Expansion path
The boundary is designed so you can add future provider support without rebuilding the rest of your stack.
Rollout pattern
A clean path from first endpoint to repeatable operations.
The goal is not just to connect Vapi. It is to make that connection reusable, traceable, and safe across every client or location you onboard after the first one.
Create the client endpoint
Provision a Vapi webhook URL for the tenant, location, or brand that should receive its own routing context.
Attach it in Vapi
Set the server URL at the assistant level so the correct Voxfra endpoint receives the end-of-call report.
Route into workflows
Voxfra enriches the event and hands it to the rest of your system in a way that remains stable as the business scales.
Operate with confidence
Tracing, isolation, and repeatable onboarding become platform behavior instead of manual discipline.
Support status
Current provider rollout
Vapi is the active production integration today. Additional providers are queued deliberately so the control layer stays reliable instead of sprawling.
Vapi
Production webhook ingestion available today
Retell
Queued by customer demand
Bland
Queued by customer demand
LiveKit
Queued by customer demand
ElevenLabs
Queued by customer demand
Next step
If your Vapi deployment is starting to feel operationally expensive, that is the signal.
The answer is not more glue. It is a cleaner boundary around ingestion, routing, and workflow execution.