2 April 2026
Summary
Release window: Thursday 2nd, April 2026, 05:00 UTC.
Service impact: None expected; backend changes only
Customer action: New Call Centre XML required for the Disclaimer (Login Notice) improvement. Download the file below:
Support
If something isn’t working as expected after this update, contact: [email protected]
Improvements
Name change from 'Unaric Unify' to 'Unaric Voice for Teams'
Unaric Voice for Teams is the new name for Unify going forward. This change will be reflected in our softphone, and across all documentation.
Softphone Layout
By default, Unaric Voice for Teams automatically opens the matching Salesforce contact record for inbound calls. Previously, this included popping a single record even when the incoming phone number was associated with multiple contacts.
We have now removed this behaviour, allowing Salesforce’s native softphone configuration to take full effect. As a result, when a conflicting phone number is detected, Salesforce can follow its standard logic (such as displaying the search results page instead of opening an individual record).
Sales Engagement
Unaric Voice for Teams now supports click to dial from Sales Engagement.
Default Call Result
Improved call result functionality by allowing a default call result for call wrap-up.
Outbound Pop Up
Removed the functionality for auto-popping the contact record on outbound calls.
Disclaimer (Login Notice)
You now have the ability to customise the Unaric Voice for Teams disclaimer / login notification.
Customer action: New Call Centre XML required for the Disclaimer (Login Notice) improvement. Download the file below:
Fixed issues
Wrap-up values overwritten with multiple ongoing calls
In some cases, wrap-up notes on one call could be overwritten by notes on a second call when two calls are live simultaneously.
Status: Resolved in April 2nd Update
Immediate hang up causes disconnect
If you answer a call and immediately hang up, this may cause Unaric Voice for Teams to hang in a Disconnected state.
Status: Resolved in April 2nd Update
Known issues
No ring back tone (RBT) heard in Unaric Voice for Teams (outbound calling)
Some instances have reported no ring back tone when making an outbound call. So far, this issue has only been raised by customers using Teams Direct Routing.
Status: Under investigation. This issue is caused by the upstream carrier not providing a ring back tone, so the call is silent until it is either answered, or hits voicemail. When making the call via the Teams Desktop or web client, you will hear the default Teams outbound calling melody played while the call connects (this is Microsoft's way of providing feedback to the caller if no RT is provided by the upstream carrier).
Solution: The Summer release will include a fix to this issue. We will insert our own melody for outbound calls if the ring back tone is not provided by the upstream carrier (in the same way that Microsoft Teams does today).
Temporary fix: An alternative fix is to add a ring back tone to your SBC if using Direct Routing or by raising a request with your Direct Routing provider, asking for them to insert the ring back tone. If you see Ringing in Unaric Voice for Teams, then the ring back tone is not being provided, so the call will be silent until answered or voicemail. If you see EarlyMedia, the Ring back tone is being provided, and you will hear the ringing:
