> For the complete documentation index, see [llms.txt](https://docs.voiceb.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voiceb.ai/product-updates/june-2026-voiceb.ai-product-release.md).
# June 2026 — VoiceB.ai Product Release
***
June moved VoiceB **from engineering-operated to operator-owned**.
Where May closed the contact gap — making sure every submitted lead actually gets reached — June changes who runs the system. **Agent Studio is now available to admin users**: the full agent lifecycle — create, configure, test, publish, and maintain — moves out of engineering and into the hands of the people who own the campaigns.
Until now, standing up a new agent or changing a live one meant an engineering ticket. That worked when deployments were counted on one hand. It does not scale to a platform signing multiple new enterprise logos every month.
The objective: **make agent creation and maintenance a configuration task, not an engineering project.**
***
**🚀 Key Highlights**
* **Agent Studio for admin users** — create, configure, and maintain autonomous agents end-to-end from the console, with no engineering involvement required
* **Structured script editing with version control** — typed Script Blocks, full change history, diff, and one-click restore on every edit
* **Routing and transfer as configuration** — human-handoff rules managed as tool settings, kept separate from the agent script
* **Callback retry hardening** — reliability and scheduling fixes across the Click-to-Call Retry Policy released in May
***
**✨ Agent Studio — The Full Agent Lifecycle, Now in Admin Hands**
Agent Studio is the operating console for autonomous agents. With this release, users with the admin role run the complete lifecycle without touching code or opening a ticket:
* **Create agents** — spin up a new agent from scratch, defining its goal, role, and conversation objectives through structured Script Blocks
* **Edit live scripts safely** — every change is auto-versioned with full history, diff, and restore, so a production agent can be edited with the same rigor as production code
* **Configure outcomes and tags** — define the outcome taxonomy and custom tags the Outcome Engine applies to every call
* **Manage routing and transfers** — transfer-to-human logic is configured as a tool, independent of the script, so routing changes never require rewriting the agent
* **Connect knowledge** — attach and update the agent's knowledge base, including web-scraped content
* **Publish and monitor** — push changes live and follow performance in the Campaign Dashboard, per outcome, tag, and agent
[Agent Studio →](https://docs.voiceb.ai/agent-studio)
*Images: Agent Studio — agent overview and creation view*
**What changes in practice**
| Before June | With Agent Studio for admins |
| ---------------------------------------- | ----------------------------------------------------------- |
| New agent = engineering ticket | New agent = admin configures it in the console |
| Script change = request, wait, deploy | Script change = edit, diff, publish — and restore if needed |
| Routing change = code change | Routing change = tool configuration |
| Onboarding gated by engineering capacity | Onboarding gated only by campaign readiness |
The result is speed exactly where it matters most: client onboarding and iteration on live agents. Changes that took days now take minutes — with a full audit trail underneath every edit.
*\[Screenshot: Script Blocks editor with version history panel]*
**Who gets it**
Agent Studio ships behind role-based access. Script editing, outcome configuration, routing, and publishing require the **admin** role; analyst and viewer roles keep read access to dashboards, transcripts, and recordings. Every published change is logged with author, timestamp, and version for full auditability.
***
**🔧 Improvements & Fixes — Callback Retries**
May introduced the Click-to-Call Retry Policy. June hardens it with fixes from the first weeks of production traffic:
* **Business-hours edge cases** — retries scheduled exactly on a window boundary now snap forward correctly, including across weekends and timezone offsets
* **Retry-chain reliability** — transient telephony failures no longer interrupt an active retry sequence; the chain resumes with the correct attempt index
* **Accurate retry indexing** — the `retry n/m` index in the Campaign Dashboard is now consistent across all failure outcomes
* **Duplicate-attempt prevention** — safeguards against double-dialing the same lead when multiple triggers fire in a short window
***
**Final Takeaway**
June was about **ownership**.
April made VoiceB easier to find, evaluate, and deploy. May made sure that once a lead raises its hand, it gets answered. June puts the operation itself in the operator's hands — autonomous agents are now created, changed, and maintained by the people running the campaigns, with version control and audit trails underneath every edit.
The engineering bottleneck on agent creation and maintenance is gone. What remains is the work that matters: making every conversation convert.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.voiceb.ai/product-updates/june-2026-voiceb.ai-product-release.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.