- [New] We now send the phone number as the caller ID name. This mostly only affects calls to Canada, as most carriers in other countries do not use the caller ID name that is sent with the call. Instead, they look up the caller name in a central database. Before this change, a call to Canada appeared as from “Unknown”plus the telephone number. Now it will just appear as from the telephone number. (315947,366660,381569)
Bug fixes
- [Fix] If a lead hangs up their inbound call while we are establishing the agent’s call leg, DialSource will think the agent is still in a call, but won’t let the agent disconnect, leaving the agent stuck and unable to receive more calls. (333780,373931,388645)
- [Fix] In some situations, Hangup on Disposition does not hang up the call. The call is dispositioned, but the agent must manually hangup. (274129,386601)
- [Fix] Answering a call can result in the caller name and object type to get reset to unknown, so the agent must manually find and link the record. (388256,390295,394021)
[Fix] After clicking Disposition Without Dial, if the page is reloaded before the Disposition is selected, selecting a disposition after the refresh will fail. (296358,296366,296277,323553,323602)- [New] Better error handling when refreshing reports in campaigns. The CRM APIs often return errors that we can recover from. This change makes Denali handle more of those error types.
- This was rolled back because an unrelated code change that altered the size of the Notes box was accidentally included. We will remove the unrelated change and push this back out again shortly.
[Change] When a call is blocked by the Do Not Call API, the UI presented to the user will be less confusing. Previously, the call that was being blocked said “Next Call” and let the user override and call the number anyway. Because the title is Next Call, users would mistakenly override the blocked call, thinking it was instead the next call in their campaign. - This was rolled back because an unrelated code change that altered the size of the Notes box was accidentally included. We will remove the unrelated change and push this back out again shortly.
[Fix] After clicking Disposition Without Dial, if the page is reloaded before the Disposition is selected, selecting a disposition after the refresh will fail. The note for fix was mistakenly included in the December 2 Release Notes. The fix was not released on December 2, and is being released today instead. (296358,296366,296277,323553,323602) - [Change] When a call is blocked by the Do Not Call API, the UI presented to the user will be less confusing. Previously, the call that was being blocked said “Next Call” and let the user override and call the number anyway. Because the title is Next Call, users would mistakenly override the blocked call, thinking it was instead the next call in their campaign. This fix was rolled back from December 11 release and is being released today.
- [Fix] The Pre-Dial webhook fires on incoming calls and DLD offers. It is only supposed to be triggered on outgoing calls. This means that customers using the pre-dial webhook could easily block incoming calls inadvertently.
- [Fix] After clicking Disposition Without Dial, if the page is reloaded before the Disposition is selected, selecting a disposition after the refresh will fail. This fix was rolled back from December 11 release and is being released today. (296358,296366,296277,323553,323602)
- [Fix] New calls are not logged in the history tab. This behavior started after the December 11 release. (412282)
Comments
0 comments
Please sign in to leave a comment.