Hear the options.
Preview TTS voices across providers before you commit the config.
Playground
Test hard. Ship calm.
Talk to your agent from the browser — no phone number required. Iterate the draft safely; only the published version answers live callers after you buy and assign a line.
Break it before callers do.
Playground is where you test voices and configurations. Agent settings also include a Test Call panel — same idea: your mic, a live conversation, hang up when you’re done.
Roleplay in-browser.
Click Test, connect, and talk — interrupt, push edge cases, no PSTN required.
Publish, then go live.
When the draft sounds right, publish. Buy a number and assign only that published agent.
Playground voices
Pick a voice. Talk to it.
The Playground route (`/w/:id/playground`) is built to test voices and agent configurations before anyone dials your business line.
- Cycle voices and hear tone differences in context
- Validate pronunciation and pacing for your industry
- Keep iterating without touching the live number
Test Call panel
Configure. Mic test. Iterate.
From agent settings, open Test Call: the panel connects your browser mic over WebSocket so you can hear the voice and behavior you configured — then hang up when you’re satisfied.
- No phone number required for the test
- Same STT / LLM / TTS stack you configured on the agent
- Test calls consume credits like real calls
- Production keeps running on the last published version
Draft freely. Publish deliberately.
Wirevox separates the draft you edit from the published snapshot that answers live calls. Playground and Test Call let you stress the draft without putting unfinished prompts on a public number.
DRAFT
Safe to change
Prompt, voice, model, functions, and knowledge edits auto-save to draft. Callers never hear them until you publish.
PUBLISHED
What goes live
Publishing creates a version snapshot. Inbound calls always load that published config — not the draft open in your browser.
NUMBER
After you’re ready
Buy a Telnyx number, assign it only to a published agent, and the line answers 24/7 on that snapshot.
First agent path
From zero to a tested line.
Getting Started walks you from creating an inbound agent through Test Call, then Numbers — the playground sits in that loop so you never skip validation.
01 / CREATE
Inbound agent.
Pick a template or start blank. Configure prompt, voice, STT, and functions.
02 / TEST
Browser call.
Open Playground or Test Call. Mic on, talk through real scenarios, hang up.
03 / PUBLISH
Snapshot the draft.
Review changes and publish so live routing has a stable version.
04 / GO LIVE
Buy & assign.
Search Numbers by country or area code, purchase, assign the published agent.
What to validate
Use the mic for the hard parts.
A good test call is not a polite hello — it is the awkward moments you want the agent ready for before a real customer dials.
01
Greeting and barge-in.
Speak over the agent mid-sentence. Confirm interruptions feel natural before you publish.
02
Functions and knowledge.
Ask for booking, transfer, SMS, or policy answers so tools and retrieval fire in the sandbox.
03
Voice and language fit.
Preview voices in Playground; confirm the language and tone match how your front desk actually sounds.
04
Then — and only then — assign a number.
Assignment requires a published agent. Unfinished drafts stay off the public line.
— Why it matters
Same stack. Safer until you publish.
No live risk
Iterate the draft while the published agent keeps answering the assigned number unchanged.
Seconds to tweak
Change prompt or voice, re-test from the browser, publish when the amber “unpublished changes” indicator is gone.
Credits apply
Test calls use the same usage path as production — cost follows your STT + LLM + TTS stack.
FROM THE DOCS
Section 1 — Getting Started
Playground in the sidebar, Step 5 Test Call (browser mic, no number), and Step 6 buy & assign when ready.
Try a sandbox agent with us.
On the demo we’ll break your script on purpose — then fix it before anyone dials.