Release Notes for version 18.220 of Connect (Enhancement and Bug Fix Release)
Date of release
Summary
Next Contact Time is respected when activating dial entries (Bug Fix)
Enabled when you enable Next Contact Time in custom settings
Availability
Vonage Contact Center for Sales Premium
Agent changes
It was possible for dial entries to be created for salesforce records that matched dial list filters and exist as pending dial entries even after Next Contact Time was set by an agent.
This allowed records which should be excluded from dial lists due to their Next Contact Time to be activated and potentially dialled more than once.
Now, once an agent has completed or skipped a dial entry it is no longer possible for another agent to work on a dial entry related to that record until their Next Contact Time is updated to make them elligible for a dial list.
Support custom Next Contact Time field for Dial Lists based on Accounts or custom objects (Bug Fix)
Custom NextContactTime__c field is working fine on all possible objects.
Error Logging (Enhancement)
Enabled by default
Availability
Vonage Contact Center for Sales/Service Express/Essentials/Select/Premium
Agent changes
Detailed red error messages have been replaced with a simplified error message that contains a reference that can be passed to Vonage Contact Center support for investigation.
Salesforce administrator changes
Records for VCCContactWorld__Log__c object will be created when errors occur, these records contain the error detail, user that inserted the record and a value to help group common errors.
Each error is logged asynchronously as an Apex Job. This job will also delete records created over 1 month ago to limit impact on storage usage.
For general assistance, please contact Customer Support.
For help using this documentation, please send an email to docs_feedback@vonage.com. We're happy to hear from you. Your contribution helps everyone at Vonage! Please include the name of the page in your email.