The v11.29.0 release brings smarter AVA-to-HubSpot data extraction, more accurate sequence response tracking, and clearer Branded Caller ID status. These updates give admins better visibility into platform activity and reduce manual work in CRM workflows.
AloAi Voice Analytics Custom Entity Mapping & HubSpot Deal Sync
AloAi Voice Analytics (AVA) entity mapping for HubSpot has been significantly expanded. Beyond the existing 40+ standard entities AVA already extracts from call transcripts, admins can now define up to 25 fully custom fields, each with their own name, type (Text, Selection, or Multi-Selection), and accepted values. AVA's LLM extracts these custom values automatically from call transcriptions and syncs them into HubSpot.
Both standard and custom entities are managed within the same AVA Entity Mapping tab, now organized into two clear sections: Standard Entities and Custom Entities.
Entity mapping also now supports HubSpot Deals in addition to Contacts. Using the HubSpot object selector at the top of the tab, admins can configure mappings independently for each object. Both Standard and Custom Entities reflect whichever object is selected. When Deal is selected, AVA syncs extracted values to up to 10 HubSpot Deals associated with the contact from the call.
This eliminates the need for agents to manually update CRM fields after every conversation, while ensuring the data captured is exactly the data your team cares about, whether that's a contact-level attribute or a deal-level update.
Voicemail Exclusion from Sequence Response Counting
Sequence response tracking is now significantly more accurate. Aloware now uses Answering Machine Detection (AMD) on outbound sequence calls to distinguish human-answered calls from voicemails and answering machine pickups.
Previously, voicemail pickups were sometimes counted as contact responses, which caused contacts enrolled in sequences with the "Remove lead if they respond" setting enabled to be prematurely disenrolled. With this update, only calls classified as human-answered are counted as sequence responses. Calls identified as voicemail, machine, fax, or unknown outcomes are excluded from response metrics and disenrollment logic.
What to expect after release:
- Sequence response metrics reflect real human engagement only
- Contacts are no longer removed from sequences due to voicemail or machine pickups
- Enabling this feature incurs an additional per-call fee
- Disabled by default; admins can opt in per account
Branded Caller ID Status Visibility
The Branded Caller ID (BCID) label in the Lines view now accurately reflects both the registration tier (Standard or Enhanced) and the current registration status (Pending, Approved, or Rejected).
Previously, BCID labels always displayed carrier associations (e.g., "Branded for Verizon and T-Mobile") even when registration was still pending or had been rejected, leading to a misleading in-app experience. With this update, the label updates dynamically:
- Approved: Displays the registration tier and associated carriers
- Pending: Displays the registration tier with a clear Pending indicator
- Rejected: Displays a Rejected status and the failed branding for carriers
- Lines without an active BCID registration display no BCID label or an unregistered state
- BCID filtering in the Lines view works correctly across all registration states
Admins and internal team members now get clear, real-time registration visibility without leaving the Lines page.
Bug Fixes & Performance Improvements
This release includes a range of stability, reliability, and performance improvements across AloAi, integrations (HubSpot, Salesforce), telephony, and platform infrastructure.