Vendor-neutral, vendor-interactive
You did not build your voice agent from scratch. You built it on Retell, Vapi, or ElevenLabs. Testzilla works the same way: it is the testing layer you plug in alongside the platforms you already use, not another platform you have to migrate to.
Vendor-neutral but vendor-interactive
Section titled “Vendor-neutral but vendor-interactive”Testzilla does not care which provider you chose. It drives your real agents on those providers: it places real phone calls, opens your live chat widget in a real browser, and runs real WebRTC voice sessions against the agent you actually shipped. The results reflect what your users get, not a simulation.
- Bring the agents you already have. Point Testzilla at an existing Retell, Vapi, or ElevenLabs agent. No rebuild, no migration, no SDK lock-in.
- Plug in alongside, not on top. Testzilla is the testing layer. Your agent keeps living on its provider; you keep shipping the way you already do.
Platforms Testzilla reaches today
Section titled “Platforms Testzilla reaches today”Testzilla connects through four connection types, and the platform coverage differs by surface:
- Voice and phone — Retell, Vapi, and ElevenLabs. Phone tests run through your Retell or VAPI telephony; Web Voice runs a WebRTC session against Retell, Vapi, or ElevenLabs.
- Web Chat — a real chat widget in a real browser, with automatic widget detection. Retell, Intercom, Drift, and Crisp have full implementations; Zendesk, Tidio, and LiveChat are partially scaffolded; and a heuristic generic connector inspects the DOM for any other widget vendor.
So beyond the three voice providers, Web Chat can drive many widget vendors — and fall back to a generic connector when it meets one it does not recognise.