New in this release
Refer to the latest documentation changelog for additional information.
CRM integration
Bitrix24 call logging and screen pops
Calls made using the Bitrix24 integration are now logged in the Bitrix24 call history. Call outcome logging and call details are automatically transmitted to the Bitrix24 database after a call and are available from the Call Details table.
When an agent handles a call in Voiso,
the contact record is automatically displayed in Bitrix24.
Do Not Call Registry
Support for Zen DNCR services
For contact centers operating in the UAE, Voiso supports an API integration with the Zen service to verify outbound UAE numbers against the Do Not Call Registry in real time. This integration applies only to UAE numbers (+971). All outbound call types are supported, including agent dialed calls, click-to-call calls, and Dialer campaigns.
DNCR End reasons
The following End reasons are now included in Call Detail Records to support calls that ended when their numbers were on the Do Not Call Registry:
- DNCR failure — Voiso cannot complete the DNCR verification due to an API accessibility issue or error, so Voiso blocks the call under the fail closed behavior (Disposition: Failed).
- DNCR rejected — When a Do Not Call Registry check completes successfully and returns that the outbound number is on the restricted list, Voiso blocks the call (Disposition: Failed).
Numbers
Minimum service terms numbers
Minimum service term tracking is now available for certain numbers on the Buy Numbers page. When access to these numbers is enabled for your contact center, numbers with a minimum service term are clearly labeled during browsing, checkout, and on the Numbers page, including remaining months. If a number is returned before the term ends, Voiso calculates and charges the early return fee immediately, and the charge appears in your billing transaction history with a clear description.
Improvements
UX and UI improvements
Improved Flow creation
A new indicator is added to the Flows page to help you identify which flows have not yet been fully configured. If Flow Builder has not been used to create and save an interaction routing, the status of the flow will be Not configured. After you create an interaction flow using Flow Builder, the status of the flow will be changed to Configured and the flow can accept and route interactions.
There is currently no automated logic testing of your interaction flows. Voiso recommends that you test all of your interaction flows manually before putting them into production.