February 2026 — VoiceB.ai Product Release

By Alex Bisbe. March 5th, 2026.

---

February focused on agent configurability and operational control.

This release gives operators deeper tools to build, manage, and govern AI agents — from how scripts are structured and versioned, to how outcomes are classified, to how data flows into CRMs. The objective: faster iteration, cleaner data, and enterprise-grade agent management.

---

🚀 Key Highlights

• New Campaign Dashboard with search, filters, and outcome visualization

• Script Blocks — structured, block-based agent prompt editor

• Script History — full version control with diff and restore

• CRM Trigger Conditions — outcome-based integration firing logic

• CRM Constants — fixed field values injected at sync time

• Tags Editor — natural language tag logic with Valid/SOLD override

---

📊 New Campaign Dashboard

The Campaign Dashboard has been redesigned for operational clarity.

What's new:

• Search and filter bar — filter calls by phone number, outcome, agent, tag, and more

• Switchable bar chart — visualize call distribution by Status, Outcome, or Tags, all normalized to 100%

• Cleaner call list with consistent column display across all inbound sources

This makes it significantly faster to identify patterns, isolate segments, and report on campaign performance without leaving the dashboard.

---

🧱 Script Blocks

Agent prompts are now built using a structured block system inside Agent Studio.

Each script is composed of typed blocks — Goal, Role, Objective, Objections, and more — each independently editable with rich text formatting, headers, lists, and inline variable support {x}.

What this unlocks:

• Clearer separation of prompt concerns

• Faster editing without touching unrelated sections

• Consistent structure across all agents and campaigns

• Foundation for future prompt automation and auto-generation

Documentation: VoiceB Prompt & Script Guide →

---

🕓 Script History

Every change to an agent's script is now automatically versioned.

The Script History panel shows a full timeline of edits, including:

• Full snapshots

• Block reorders

• Individual script edits

Each entry supports Preview, See Diff, and Restore — allowing operators to review exactly what changed and roll back instantly if needed.

This is the first step toward treating agent prompts with the same rigor as production code.

---

🔗 CRM Integration: Trigger Conditions

CRM integrations can now be configured to fire only on specific outcomes.

Operators choose which outcomes trigger a sync — Sold, Reschedule, Talk to Agent, Pending, or any combination — and exclude everything else (Customer Care, Voicemail, Failed, Dropped, etc.).

What this prevents:

• Polluting CRM pipelines with invalid or low-intent calls

• Unwanted contact creation on failed or care-related interactions

• Attribution noise in marketing and sales reporting

This pairs directly with the Outcome Governance framework introduced in January.

---

📌 CRM Integration: Constants

Alongside field mapping, integrations now support Constants — fixed HubSpot field values that are injected at sync time regardless of call data.

Use cases include:

• Tagging all contacts from a specific campaign or DDI

• Assigning a fixed owner or pipeline stage on creation

• Injecting source or channel metadata automatically

---

🏷️ Tags Editor: Natural Language Logic + Valid/SOLD Override

The Tags configuration interface has been redesigned around natural language logic.

Each tag is defined by:

• True if — a plain-language description of when the tag applies (e.g. "The user is interested in mobile plans")

• False if — the inverse condition

• Color — for visual identification in the dashboard

• Valid / SOLD status checkbox — forces the tag to count as a completed sale in reporting

The SOLD override is particularly significant: it decouples business-defined conversions from AI outcome labels. A checkout completion tag can be marked as SOLD independently of what the voice outcome was — ensuring revenue reporting reflects commercial reality.

---

Final Takeaway

February was about giving operators control.

Control over how agents are built and versioned. Control over what gets sent to the CRM and when. Control over how outcomes are defined and measured.

This release makes VoiceB meaningfully easier to configure, iterate on, and trust — across every layer of the agent stack.