> 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/may-2026-voiceb.ai-product-release.md).
# May 2026 — VoiceB.ai Product Release
***
May moved VoiceB **from reaching the buyer to reaching the lead**.
Where April brought the product to the surface — deployable, priceable, understandable from the outside in — May closes the gap that sits one step further down the funnel: the lead who was acquired, paid for, and submitted, but didn't pick up the first time.
A single dial attempt reaches only a fraction of submitted leads. The new **Click-to-Call Retry Policy** turns that single attempt into a disciplined, compliant retry sequence — controlled by the operator, bounded by local calling rules, and fully visible in the dashboard.
The objective: **maximize contact rate without violating local outbound calling rules.**
***
**🚀 Key Highlights**
* **Click-to-Call Retry Policy** — automatic re-dialing of submitted leads under operator-defined conditions: how many attempts, how long between them, which failure outcomes trigger a retry, and which hours and days are allowed
* **Exponential and custom backoff** — fast retries while intent is warm, spacing out as the lead cools, or a precise manual cadence
* **Business-hours enforcement** — retries snap forward to the next valid window so calls never land outside allowed times
* **Per-retry dashboard visibility** — every attempt logged as its own call with its retry index, filterable per lead and per outcome
***
**🔁 Click-to-Call Retry Policy — Every Lead Contacted, Inside the Rules**
Click-to-Call places an outbound callback the moment a lead is submitted — a form fill, a widget request, a CRM trigger. The first attempt connects most leads, but a meaningful share won't pick up the first time: they're driving, in a meeting, or away from their phone. Every one of those is paid-for demand that, until now, could go uncontacted.
[Click-to-Call Retry Policy →](https://docs.voiceb.ai/click-to-call-retry-policy)
The numbers make the case. A single dial attempt typically reaches 30–50% of leads, while three to four well-spaced attempts lift contact rates above 70%. That difference flows directly into conversion rate and CPA — it is one of the highest-leverage changes available on a live lead source, because the demand is already bought and paid for.
**Operator-controlled, by agent**
The Retry Policy is configured per agent on the agent settings page. A single toggle activates it; when disabled, Click-to-Call makes exactly one attempt per lead and stops. Operators control four things:
* **Max attempts** — total dial attempts per lead, including the original call. Recommended 3–5 for most B2C use cases.
* **Retry on** — which failure outcomes trigger a retry: `no answered`, `busy`, `voicemail`, `failed`, `dropped`, `unreachable`. A typical setup retries on `no answered`, `busy`, and `voicemail`, and skips the number-level failures more attempts won't solve.
* **Backoff strategy** — how long to wait between attempts.
* **Business hours** — the window inside which retries are allowed to land.
**Two backoff strategies**
* **Exponential** — the wait grows after each attempt by a fixed factor, up to a maximum. Defaults of 15 min initial / factor 2 / 1440 min max give hot leads a fast retry while intent is warm, then space attempts out as the lead cools. The right default for most lead-gen flows.
* **Custom sequence** — define each delay manually as a comma-separated list of minutes (e.g. `15, 60, 240, 1440`). The system uses each value in order and reuses the last once the list is exhausted. Built for a precise cadence — retry quickly within the first hour, then once that evening, then once the next morning.
**Compliance by default**
Outbound calling outside business hours is illegal or restricted in most markets. The Business Hours block ensures every retry lands inside an allowed window:
* **Respect business hours** — any retry scheduled outside the window is moved forward to the next valid slot.
* **Start / end hour** — the daily window, in the local timezone of the campaign, not the browser.
* **Weekdays only** — retries scheduled for Saturday or Sunday are pushed to the following Monday.
A Spain campaign set to 9:00–20:00, weekdays only, will never place a retry on a Saturday morning or a Tuesday at 8:30 — even when the backoff math says it should. The controls let operators be aggressive on contact rate while staying inside the rules.
**Visible per attempt**
Every retry is recorded as its own call in the Campaign Dashboard with its retry index alongside the outcome — `retry 1/2`, `retry 2/2`, `retry 1/3`. Filter by phone number to view the full retry chain for any single lead, or by outcome to spot patterns: leads that consistently hit voicemail across all attempts point to a bad data source, not an agent problem. The same diagnose-before-you-blame discipline VoiceB applies everywhere, now extended to contact attempts.
**Recommended starting points**
| Use case | Max attempts | Retry on | Backoff | Business hours |
| -------------------------------------------------------- | ------------ | ---------------------------- | ---------------------------------- | --------------------- |
| Standard B2C lead-gen (ES, UK, EU) | 4 | no answered, busy, voicemail | Exponential — 15 / ×2 / 1440 | 9:00–20:00, weekdays |
| High-intent / hot leads (cart abandon, recent form fill) | 3 | no answered, busy | Custom — `5, 30, 180` | 9:00–21:00, weekdays |
| Low-volume / high-value (insurance, financial) | 5 | no answered, busy, voicemail | Custom — `15, 60, 240, 1440, 2880` | 10:00–19:00, weekdays |
***
**Final Takeaway**
May was about **recovering the demand that was already paid for**.
The Retry Policy doesn't acquire a single new lead. It makes sure the leads already submitted actually get reached — turning a 30–50% single-attempt contact rate into 70%+ across a disciplined, compliant sequence the operator controls and can audit per attempt.
March put VoiceB deeper inside the enterprise. April made it easier to find, evaluate, and deploy. May makes sure that once a lead raises its hand, it gets answered — every time the rules allow.
---
# 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:
```
GET https://docs.voiceb.ai/product-updates/may-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.