# March 2026 β VoiceB.ai Product Release
***
March focused on **enterprise connectivity and CRM depth**.
This release brings VoiceB deeper into enterprise telephony infrastructure and revenue systems. \
\
SIP Trunk moves VoiceB inside carrier-grade contact centers without disrupting existing infrastructure. The Salesforce integration replaces a simple webhook with a full CRM orchestration layer. \
\
And Trigger Conditions β now covering both HubSpot and Salesforce β give operators precise control over what flows into their CRM and when. \
\
The objective: **closer to the revenue system, further from the generic voice bot**.
***
**π Key Highlights**
* **SIP Trunk** β private call routing with pre-call, in-call, and post-call data injection
* **Salesforce Integration** β CRM-native orchestration across any object, with deduplication and field mapping
* **Trigger Conditions for HubSpot and Salesforce** β outcome-based firing logic for both integrations
***
**π‘ SIP Trunk β Private Call Routing for Enterprise Voice AI**
VoiceB can now connect directly to any enterprise PBX or Session Border Controller (SBC) via a dedicated, fully managed SIP trunk.
This is the architecture that Vodafone EspaΓ±a runs in production. Instead of porting numbers or routing through shared telephony infrastructure, organizations keep full ownership of their carrier contracts and phone numbers β and connect them to VoiceB AI agents at the SIP layer.
[SIP Trunk documentation β](https://docs.voiceb.ai/sip-trunk-private-call-routing-for-enterprise-voice-ai)
**What this enables:**
* **Pre-call data injection** β Before the AI agent picks up, VoiceB fires a webhook to your CRM or backend. The response is injected into the agent's prompt, so every conversation starts with full caller context: account status, lead tier, prior interactions. The caller hears "hello" and the agent already knows who they are.
* **In-call SIP header routing** β Custom SIP headers attached by your PBX are captured and used to route calls to the right agent in real time. One trunk, multiple agents, zero PBX reconfiguration.
* **Post-call transfer with context** β When the agent hands off to a human, VoiceB fires a pre-transfer webhook with the full conversation data β transcript, intent, extracted fields β before the call arrives at the human agent's desk.
**Configuration is fully no-code from the Agent Studio dashboard:**
* IP Access Control β whitelist your SBC IP addresses
* SIP header capture table β define which headers to capture, their direction, and where to forward them
* Routing rules engine β evaluate headers and webhook fields to select the right agent (first-match-wins)
* Call Tester β dry-run validation mode and live test call mode, both from the dashboard
**Competitive position:** No other AI voice platform offers pre-call webhook templating with `{{placeholder}}` SIP header tokens, a routing rules engine native to the AI layer, or a pre-transfer webhook with HMAC-SHA256 signing. This is carrier-grade infrastructure, not a telephony workaround.
***
**π΅ Salesforce Integration β CRM-Native Orchestration Layer**
The previous Salesforce connector created a Lead record and stopped there. The new integration makes VoiceB a full CRM automation layer for Salesforce.
[Salesforce integration documentation β](https://docs.voiceb.ai/how-to-connect-your-voiceb.ai-agent-with-salesforce)
**What changed:**
The integration is no longer limited to fixed Lead creation or simple webhook behavior. VoiceB now acts as a CRM-native orchestration layer.
You control:
* **Which Salesforce objects receive data** β Leads, Contacts, Opportunities, Cases, or any custom object. Not every call should create a Lead. A closed sale should create an Opportunity. A customer care interaction should update a Case.
* **How objects relate** β Define relationships between objects. An Opportunity can be linked to an existing Contact without creating a duplicate.
* **Which values are constant** β Fixed field values (pipeline owner, campaign source, agent ID) are injected at sync time regardless of call data. No extra middleware required.
* **How duplicates are handled** β Matching rules prevent duplicate Contact or Lead records when the same caller interacts more than once.
This allows enterprise-grade Salesforce automation driven entirely by call outcomes β without additional ETL tools, Zapier layers, or custom development.
**Why this matters at enterprise scale:** an energy client's architecture writes autonomous sales directly as *ventas brutas* to Salesforce, bypassing the human review step entirely. That flow requires an integration layer that can address any Salesforce object with structured data, not just create a Lead.
***
**π Trigger Conditions for HubSpot and Salesforce**
First introduced for HubSpot in the February release, Trigger Conditions now apply to both HubSpot and Salesforce integrations.
[HubSpot integration documentation β](https://docs.voiceb.ai/how-to-connect-your-voiceb.ai-agent-with-hubspot)
Operators choose exactly which outcomes fire a CRM sync. The full outcome set available:
| Sales | Scheduling | Routing | Negative | System |
| ------------- | ---------- | ------------- | -------------- | ----------- |
| Sold | Reschedule | Talk to Agent | Not Interested | Pending |
| Customer Care | | | Dropped | Busy |
| Voicemail | | | Failed | Unreachable |
| Not Found | | | No Answered | |
**What this prevents:**
* Polluting CRM pipelines with failed calls, voicemails, or customer care interactions
* Unwanted Contact creation on low-intent or invalid calls
* Attribution noise across sales and marketing reporting
* Duplicate pipeline entries from non-sales outcomes
**Example configuration:** A client running Salesforce for closed-deal tracking and HubSpot for lead nurturing can configure VoiceB to sync *Sold* outcomes to Salesforce only, and *Reschedule* and *Talk to Agent* outcomes to HubSpot only β from a single integration panel, with no code.
The **Valid only** shortcut selects all sales-positive outcomes in one click. **All outcomes** resets to full sync for clients who want a complete call record in their CRM.
***
**Final Takeaway**
March was about **closing the gap between AI agent and revenue system**.
SIP Trunk puts VoiceB inside enterprise telephony infrastructure without disrupting it. The Salesforce integration makes VoiceB a CRM orchestration layer, not a webhook sender. Trigger Conditions ensure only the right outcomes reach the right systems.
Every feature in this release is about one thing: making the autonomous close β end-to-end, from call to CRM β something an enterprise can run in production and trust in their reporting.
