# April 2026 — VoiceB.ai Product Release
***
April moved VoiceB **from infrastructure to interface**.
Where March went deep into enterprise telephony and CRM integrations, April brings the product to the surface — the way buyers see it, deploy it, and price it.
The new Web Widget makes VOICEB deployable on any site with a single line of JavaScript and a full visual customization layer. The new Pricing Guide makes the commercial model explicit, with three plans and clean separation between outcomes, telephony, and outbound charges. And a new long-form article — *"What Happens When Lead Capacity Has No Ceiling"* — frames the strategic shift that autonomous inbound enables.
The objective: **make the platform deployable, priceable, and understandable from the outside in.**
***
**🚀 Key Highlights**
* **Web Widget Configuration** — one-line JavaScript deployment, multi-agent and multi-language at the campaign level, full visual customization, built-in compliance, real-time preview
* **Pricing Guide** — three plans (Starter, Enterprise, Corporate Custom), outcome-based ASVA pricing, transparent DDI and outbound call costs, all autonomy levels accessible on every plan
* **New Article: *****What Happens When Lead Capacity Has No Ceiling*** — strategic narrative on how unlimited autonomous capacity restructures the entire demand engine
***
**🌐 Web Widget — One-Line Deployment for SuperVoice**
The Web Widget is the primary way to deploy AI voice agents on any website or landing page. It connects visitors directly to SuperVoice agents via WebRTC — no phone number required, no app to install, no friction.
[Widget Configuration Guide →](https://docs.voiceb.ai/widget-configuration-guide)
Installation is one line of JavaScript with a unique widget ID. From the Widget Configuration page, operators can fully preview and test the deployment before going live — the preview updates in real time as settings change, and a built-in test call validates agent behavior end-to-end.
**Multi-agent, multi-language at the campaign level**
A single widget deployment can serve multiple agents across multiple languages. Operators select which agents the widget exposes, set the display order per language, and the widget automatically renders a language selector for visitors. One embed, multiple agents, multiple markets — ideal for multi-language websites and landing pages serving diverse audiences from a single deployment.
**Two display variants**
*
```
```
* **Bubble** — minimal floating bubble in the corner. Maximum discretion. Recommended for product pages, blogs, and content where the widget supplements the experience.
* **Compact** — a slightly larger floating element with a welcome message. More visible and explicit. Recommended for pricing pages, plan selectors, and checkout flows where voice engagement should be front-and-center.
**Full visual customization**
Every visual element is configurable to match brand identity:
* **Surface palette** — background, border, foreground, muted, hover states
* **Brand palette** — primary, hover, active, contrast
* **Metrics** — padding, corner radius, font size, icon size, exposed as individual numeric controls
* **Per-language text overrides** — title, greeting, agent card heading, description, and CTA button label
**Compliance built in**
Privacy Policy and Terms and Conditions URLs are first-class fields. When set, an explicit consent checkbox appears in the widget. With "Require terms acceptance" enabled, visitors must consent before initiating a call. Consent records — including the document content, up to 50 MB per document — are stored in the database, giving operators a complete audit trail of what each visitor consented to and which version of the documents was in effect. Built for GDPR, LOPDGDD, and equivalent regulatory frameworks.
**Closed-loop attribution**
Every widget load is an impression. Every interaction is a tracked click. UTM parameters from the page URL (`utm_source`, `utm_medium`, `utm_campaign`, `utm_content`, `utm_term`) are captured automatically and connect every voice conversation back to the marketing campaign that drove the visit — closing the attribution loop from ad spend to voice conversion at the conversation level.
***
**💶 Pricing Guide — Outcomes, Telephony, and Outbound, Cleanly Separated**
VoiceB pricing is outcome-based. The new Pricing Guide makes the commercial model fully explicit, with three plans available and a deliberate separation between value delivered and infrastructure consumed.
[Pricing Guide →](https://docs.voiceb.ai/pricing-guide)
**Three plans, all autonomy levels included**
| Outcome | Starter | Enterprise | Corporate Custom |
| -------------------------------------------- | ------- | ---------- | ---------------- |
| Unqualified / invalid calls | €0 | €0 | €0 |
| Qualified call transferred to human | €2.00 | €1.50 | Custom |
| Pre-sale (final step before payment) | €9.00 | €7.00 | Custom |
| Completed sale with integration confirmation | €20.00 | €15.00 | Custom |
| Minimum monthly commitment | €700 | €2,000 | Volume-based |
All plans include access to all four autonomy levels — L1 (Qualification), L2 (Intelligent Routing), L3 (Assisted Autonomous Sales), L4 (Full Autonomous Sales). Customers typically start at L1–L2 and scale over time without switching plans. Pricing scales with the outcome produced, not the level configured.
**Three components, billed independently**
* **ASVA outcome-based pricing** — what gets paid for value delivered
* **DDI / DID telephony costs** — monthly fee per inbound phone number, billed per region (USA $1.50, UK £2.50, Spain €5.50)
* **Outbound call charges** — included by default for North America, EU, UK, Oceania, and major Latin America markets
This separation is deliberate. Telephony costs vary by geography and carrier — bundling them into outcome pricing would create hidden margins that distort unit economics at scale. Finance teams need predictability and auditability on each component independently.
**What VoiceB does not charge for**
Seats. Agents. Minutes within included markets. AI tokens. Environments or sandboxes. LLM orchestration overhead. The only charges are outcomes, DDI numbers, and outbound calls outside included markets.
***
**📖 New Article — *****What Happens When Lead Capacity Has No Ceiling***
A new long-form piece on the strategic shift that autonomous inbound enables — written for CMOs, marketing leaders, and revenue operators.
[Read the article →](https://docs.voiceb.ai/blog/what-happens-when-lead-capacity-has-no-ceiling)
The thesis: most B2C companies are not capacity-constrained by their market — they are capacity-constrained by their contact center. That invisible ceiling shapes every upstream decision: which leads they buy, which channels they invest in, how they design the top of the funnel.
When the ceiling disappears, five structural shifts compound:
1. **Cheaper leads become economical**, because filtering is free
2. **New lead sources open up** — off-peak campaigns, broader targeting, partner traffic, organic, voice-on-landing-page
3. **Media-mix dependency breaks** — the operator controls the volume dial, not the agency
4. **No human threshold to overflow against** — acquisition capacity is decoupled from headcount
5. **TOFU stops being a filter and becomes a capture layer** — qualification moves from the form to the conversation
The article walks through each shift with production data from live enterprise deployments and closes on the compounding effect: more leads → better data → lower CPA → more budget → more leads. This is a market capture loop, not a cost-reduction story.
This is the strategic narrative that frames every other piece of the product — the widget, the pricing, the integrations, the SIP trunk. It is what the buyer is actually buying.
***
**Final Takeaway**
April was about **closing the gap between the platform and the buyer**.
The Widget makes deployment a one-line operation. The Pricing Guide makes commercial evaluation a self-serve exercise. The new article frames the strategic shift that explains why any of it matters.
Every release in March made VoiceB deeper inside the enterprise. April makes it easier to find, evaluate, deploy, and understand — from the outside in.
---
# Agent Instructions: 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:
```
GET https://docs.voiceb.ai/product-updates/april-2026-voiceb.ai-product-release.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.