# January 2026 — VoiceB.ai Product Release

January focused on **outcome governance and data integrity**.

This release strengthens how VoiceB classifies calls, enforces outcomes, and guarantees consistent labeling across inbound sources. The objective is simple: **cleaner data, stricter validity rules, and enterprise-grade outcome control**.

***

### 🚀 Key Highlights

* New **INVALID – CUSTOMER CARE** categorization
* Fixed **PENDING call logic** and display rules
* Guaranteed **FROM / TO consistency** for DDI and VoIP calls
* Introduction of **Outcome Governance**
* Custom, configurable **Outcome Tags** per AI agent or campaign

***

### 🛑 New INVALID Category: CUSTOMER CARE

VoiceB now automatically classifies **existing customer requests** as invalid demand.

If the AI detects:

* Invoice or billing questions
* Service or technical issues
* Incident reports
* Any customer-care related intent

The call is now closed as:

**`INVALID – CUSTOMER CARE`**

This prevents non-commercial demand from polluting sales metrics and ensures that VoiceB remains focused strictly on **revenue-driven conversations**.

***

### ❌ PENDING Call Logic Fix → INVALID – FAILED

We fixed the logic and display rules for calls stuck in **PENDING**.

What changed:

* PENDING is no longer a terminal state
* Failed or incomplete calls are now consistently classified as\
  \&#xNAN;**`INVALID – FAILED`**
* UI and reporting now reflect the real outcome

This eliminates ambiguity and removes artificial inflation of valid demand.

***

### ☎️ FROM / TO Consistency for DDI and VoIP

Inbound call labeling is now **fully consistent** across all sources.

Improvements include:

* FROM / TO fields always populated correctly
* Direct DDI inbound numbers displayed accurately
* VoIP calls no longer shown as “–”, now explicitly labeled as **VOIP**

This ensures:

* Reliable attribution
* Cleaner analytics
* Fewer reconciliation issues with telco teams

***

### 🧭 Outcome Governance

January introduces **Outcome Governance** as a first-class platform concept.

Key principles:

* Outcomes are no longer free-text or loosely enforced
* Each outcome follows explicit rules
* Required fields are enforced before an outcome can be applied

This is foundational for operating VoiceB in **regulated, high-volume enterprise environments**.

***

### 🏷️ Outcomes Are Now “Tags” 

#### 🧩 Custom Outcome Tags per AI Agent or Campaign

Outcomes are now implemented as **Tags**, enabling structured and extensible classification.

What this unlocks:

* Clear mapping between Tags and the **Valid / Invalid backbone**
* Multiple sub-tags under the same validity category
* A shared language between AI, reporting, and business teams

This makes outcome data both **machine-reliable** and **business-readable**

VoiceB now allows **custom outcome tags** configured per:

* AI agent
* Campaign
* Use case

Each custom tag:

* Is still mapped to Valid or Invalid
* Follows the same governance rules
* Can be tailored to vertical or client-specific logic

Documentation:\
<https://docs.voiceb.ai/tags-custom-ai-classification-for-calls-and-leads>

***

### Final Takeaway

January was not about new channels or shiny AI features.

It was about **making VoiceB’s data trustworthy**:

* Cleaner invalidation
* Stricter outcomes
* Configurable but governed classification

This is the groundwork required to scale autonomous sales **without breaking reporting, attribution, or enterprise trust**.


---

# 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/january-2026-voiceb.ai-product-release.md?ask=<question>
```

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.