Test and publish
Test calls, versions, and putting an agent live safely.
Everything you change in the builder goes into a draft. Callers only hear what you publish. This page covers publishing, rolling back, placing test calls, and the checks to run before a client’s agent takes real calls.
Plan: Publishing and test calls need an active Wozena subscription. Test calls also need a plan that can place calls.
- Retell is connected. See Connect Retell.
- An active Wozena subscription.
- For an agent that belongs to a client, an active subscription for that client.
- A prompt (or a built flow). See Build an agent.
Draft and published#
| Draft | Published | |
|---|---|---|
| What it is | Your working copy. Every edit saves here. | The version pushed to Retell that callers hear. |
| Phone numbers | Can’t be routed to an agent that has never been published. | Numbers can route to it. |
| Test calls | Not available. | Available, using the published version. |
| Public share link | Not available. | Available for client-owned agents. |
The agent card in the builder shows “Live” once a version is deployed, or “Not deployed yet”. After the first publish, keep editing freely: callers stay on the published version until you publish again. As the settings panel reminds you, “Changes save to the draft — publish to go live.”
Publish an agent#
- Check the draft is savedThe prompt editor should show “Saved”. Settings save on their own.
- PublishIn the builder header, click “Publish” for a new agent, or “Publish changes” for one that’s already live. A summary lists what changed since the last publish (for example Prompt, Voice or “2 steps edited”) and offers “Test first”. When nothing has changed the button reads “Published”.
- Confirm it workedYou see “Published” or “Changes published”. Open “History” to see the new deployment marked “Deployed”.
Pressing “Publish changes” when nothing has changed is harmless.
Who can publish
- Users who can build agents.
- Your agency needs an active Wozena subscription.
- For a client-owned agent, the client also needs an active subscription. If they haven’t subscribed, you’ll see “This client hasn't subscribed”. See Billing clients.
When a plan or subscription is missing, an “Upgrade to continue” window explains why, with “View plans”.
When publishing fails#
Every publish attempt is recorded. If Retell rejects a deployment, a red banner appears at the top of the builder: “Last publish failed.” followed by the reason and “Fix the issue and publish again — the agent stays in draft until a deploy succeeds.”
| Message | What to do |
|---|---|
| “Add a prompt before publishing — the agent has nothing to say yet.” | Write a system prompt. See Write the prompt. |
| “Voice provider not connected — connect it to publish.” | Connect Retell in Provider Connections. |
| “Upgrade to continue” or “Subscribe to continue” | Your agency, or the agent’s client, needs an active subscription. See Your Wozena plan. |
| The failure banner with a reason from Retell | Fix what the reason names, such as an invalid setting, then publish again. Hover a failed deployment in History to see its error. |
Version history and restore#
Click “History” in the builder header. For prompt agents it has two lists:
- “Draft versions”: a version is saved as you edit the prompt. The one you’re on is marked “Current”.
- “Deployments”: each publish, marked “Deployed”, “Failed” or “In flight”, with the agent version and when it happened.
- Pick a versionIn “Draft versions”, hover the version you want and click “Restore”.
- ConfirmConfirm “Restore version N?”. “Its content becomes a new draft version — history is kept.”
- Publish itRestoring only changes the draft. Click “Publish changes” to put the restored version live.
Conversation flow agents have their own History panel with version restore inside the canvas.
Place a test call#
Test your latest changes before callers hear them: nothing you try here goes live until you publish. Open “Test” in the builder header. It has a voice call and a text chat.
- Open TestIn the builder, switch to “Test”. For a published agent, choose “Latest changes” (your draft) or “Live version” (what callers get).
- Fill in variables (optional)If the prompt uses dynamic variables, the voice call shows a field for each one, filled with its default. Change any “Value for this test” to try a different caller.
- Start the callAllow microphone access, then click “Start web call”. The status moves from “Connecting…” to “Listening” and “Agent speaking”.
- End and reviewClick “End call”. The call appears in the agent’s “Calls” mode with its recording, transcript and analysis.
In “Text chat”, type as the caller. You see each reply and which functions the agent used. Functions run for real, the same as on a call. Click the restart button to start over.
| What you see | Why |
|---|---|
| “Publish to test” | The agent has never been published. Publish it first. |
| “Call capability needed” | Your plan, or this workspace, can’t place calls. |
| A message that you have reached the calling limit for this plan | The workspace has used its call minutes. |
Go-live checklist#
Run through this before a client’s agent takes real calls.
- Retell is connected with the webhook key. Check which key.
- The client exists and has an active subscription.
- The agent belongs to that client, not the agency workspace, unless you mean to share it.
- The prompt covers role, goal, tone, guardrails and when to transfer, and the first words suit the business.
- Voice and language are set, and “Max call length” is sensible.
- Any “Transfer call” function points at a number someone answers.
- Knowledge bases are attached and show “Complete”.
- Post-call analysis fields and the success metric are set.
- The agent is published and “History” shows “Deployed”.
- You’ve placed test calls covering the common questions, an after-hours question, and a transfer.
- Each test call appears in Calls with a transcript. If not, check the webhook key.
- The phone number is assigned to the client and routed, with business hours and closures set.
- You’ve called the real number from a phone and heard the agent answer.
Route a number to go live#
Publishing doesn’t connect a phone line on its own. An agent answers real calls once a number routes to it.
On a conversation flow agent, “Phone routing” in “Global settings” handles the simple case: “Add number” lists this workspace’s numbers that aren’t answering calls yet and routes the one you pick to the agent. Numbers that already answer for another agent or follow business hours are changed on Phone Numbers:
- Open the numberGo to Phone Numbers and click the number. From the agent, the “Phone routing” section links there too.
- Assign it to the clientA client’s agent can only answer that client’s numbers. Use “Reassign client” on the “Settings” tab if needed.
- Route and saveOn the “Routing” tab, choose the agent as the “Answering agent”, set after-hours handling if you use business hours, and click “Save routing”.
- Check who answersClick “Test route” to see who answers right now, then call the number.
For every routing option, see Phone numbers.
Troubleshooting#
Callers still hear the old version
You saved but didn’t publish, or the last publish failed. Check for the red banner and the latest entry in “History”.
The number won’t route to the agent
You’ll see a message that the agent isn’t published to your voice provider yet. Publish it, then save the routing again.
The Test button is missing
It only appears for users who can place calls. Open the “Test” tab to see the reason; the text chat is available to anyone who can edit the agent.