General Availability Features
Visual Engagement (Video and Screen Share)
Consumers have consistently favored video for interactions where they want a personalized experience or have a complex problem they need resolved. Visual Engagement elevates conversations by enabling an agent, via a single click from within ContactPad, to escalate any interaction to a video call with screen share capabilities. This allows them to communicate visually, making them more effective and efficient, and resulting in a better customer experience.
Whilst engaged with a video call, the agent’s state and capacity will appear as occupied, informing their supervisor and other agents that they are on a call, whilst also updating the contact center routing so that no other interaction is routed through to them.
Visual Engagement is a native channel for Vonage Contact Center (VCC) and is made available to agents using ContactPad when embedded in Salesforce, Microsoft Dynamics or ServiceNow. Supervisors and business analysts will also be able to historically report on video interactions alongside voice and any other channel which the agent supports.
Visual Engagement enables your business to achieve the following:
- Reduce time to resolution
- Make customers happier
- Lower cost to serve
- Increase first call resolution rates
- Engender trust
- Increase win rate
- Increase retention
- Protect revenue
- Communicate more effectively
- Compensate for travel cost and restrictions
- Save on travel expenses
- Reduce impact of travel restrictions
- Increase number of contact center channels
- Remain competitive in the market and keep up with evolving technology trends
- Fastest growing channel for customer service
- Report on visual engagement in real-time and historically
Visual Engagement is available on request. If you are interested, please speak to your Customer Success Manager or Account Manager.
For information about video and screen sharing, see Video and screen sharing (Visual Engagement).
Up until now our Omnichannel capabilities have been a premium feature and required a Salesforce license. However we understand that not all our customers use Salesforce and furthermore not all our customers are looking for the full feature set of our premium license. Therefore we plan to offer an Omnichannel experience for all our customers regardless of which CRM or license they use.
Our aim is to provide multiple communication channels, from messaging channels such as SMS, WhatsApp and Facebook Messenger to digital channels such as web and mobile chat—where customers can interact with agents to solve their queries and be provided the same experience, regardless of device, channel and even channel provider.
The benefits of this for your customers is that they will have choice over which device to use as well as which channel to use as they contact your business. The benefit from an agent's perspective is that they can remain within the CRM whilst interacting with customers over any channel, increasing productivity and ensuring customers are answered by the right agent as quickly as possible.
This approach ensures that regardless of who provides your digital channels, Vonage can route them all harmoniously alongside voice. As we add channels to our offering, you get the choice over whether or not you want to adopt them out-of-the-box.
In Spring ‘21 we released webchat as our first native channel. Webchat requests are routed straight from your website directly to the appropriately skilled agent via the ContactPad. This means an agent can work on various interaction types all in one place, as webchat is accessible directly from your CRM, whether you use Salesforce, Microsoft Dynamics or ServiceNow. All the context of your customer is readily available while your agent deals with their request, saving time and improving your agent’s efficiency.
Our webchat is provided as an alternative to our existing product in Salesforce, not as a replacement. We provide the flexibility for our customers to choose their channel provider and we will continue to offer a suite of off-the-shelf options in Salesforce, MS Dynamics and ServiceNow as well as providing APIs for third party integrations. All options will work in harmony with our own native channels, since the same routing logic is employed by all.
Webchat is available on request, so please contact your Customer Success Manager or Account Manager to learn more.
For information about Webchat, see Webchat.
External Routing for Messaging and Cases
During Winter ‘21 we announced the beta release of Messaging and Cases. In Spring ‘21 these features moved into general availability. This enables VCC to route messages and cases to agents using Salesforce External Routing. Messaging lets your company have conversations with customers in ways that are most convenient for them using messaging apps such as SMS and Facebook Messenger. Cases let your company capture work to be done using, among other methods, web-to-case and email-to-case. Agents have messages and cases routed to them in the Service Console, based on the contact center routing logic, the agents skill, capacity, and availability.
Screen Recording enables supervisors and quality managers to understand what the agents were doing on their desktops during the call and listen to the call. This improves your quality management capabilities so that you can easily identify inefficiencies.
Screen Recording enables your business to achieve the following:
- Identify coaching opportunities to improve call efficiency
- Record one or two screens, not just browsers or applications
- Understand after call work activities
- Synchronize desktop activity with audio recordings
- Playback multiple screens at once
- Zoom into agents screens
- Download audio and video in a single file
- Identify which calls have just audio and transcription and screen recordings easily
- Store screen recordings securely
- Set permissions on who can view screen recordings
- Centrally control whose screens are recorded
- Link screen recordings to Conversation Analyzer
For more information about screen recording, see ContactPad with Screen Recording.
Virtual Assistant delivers conversational artificial intelligence (AI) for business communication within your Vonage solution, making customer experience your competitive advantage. Virtual Assistant uses AI to deliver enhanced self-service interactions that engage every caller with natural language and enable additional capacity within your contact center.
With Virtual Assistant, you can:
- Reduce cost
- Increase self service
- Increase customer satisfaction
- Reduce wait time
- Improve average handle time
- Easily tailor the solution to your business needs
- Get up and running in days
- Improve your operational KPIs, customer experience, and business accessibility
Virtual Assistant interprets what the customer’s question is and, if required, asks clarifying questions to formulate the appropriate response. That response may be referencing content from an FAQ, proposing an action to update or read customer data, or routing the call to the correct queue within the Interaction Architect.
This release provides a more intuitive version of the intent builder by using a visual builder to represent your conversations more clearly.
In this release we took the next step in consolidating all administrative functions into User Admin. Functionality previously available only in Real Time and User Access have been migrated over to User Admin.
Supervisors with the appropriate permissions can now take advantage of the full User Admin Experience. This provides full parity with Real Time and much more.
User Admin now:
- Allows supervisors to edit users, groups and skills in which they have permission
- Respects a supervisor’s group permissions when providing view or edit access to a user
- Respects a supervisor’s managers when providing view or edit access to other supervisors
This new capability comes with some new permissions:
- Access User Admin: Provides general access to User Admin
- Create User: Allows the user to create other users of the same level as them or below
- View Unassigned Users: Allows a supervisor to see agents not assigned to a group they have permission for
- Manage Routing Settings: Allows a supervisor to edit or create skills and groups.
All users that previously had the Edit Agent permission under Real Time have been given the Edit User permission under User Admin.
Previously only available as early access. All customers can now archive all user types at an individual level or via bulk/import. Archiving a user prevents them from logging in, release their license, and remove them from Dashboards. All this whilst providing the ability to historically report on these users.
This has resulted in the following changes within the CSV import/export:
- User Active has been added
- Active changed name to ContactPad enabled
Unlock User Account
The ability to reset login attempts has been migrated from Real Time into User Admin. This is used to unlock and user account when it has become locked because of a high number of incorrect password attempts.
The ability to delete groups has been migrated from Real Time into User Admin. Only administrators are allowed to delete a group.
User Interface Improvements
We have been working to improve the user experience or User Admin by making filtering more effective, providing quick bulk actions, improved layout, and much more.
For more information about user administration, see User Admin.
Dashboards have been extended to provide greater visibility for outbound-focused contact centers. In addition, terminology and calculations have been updated to be channel agnostic (phone, chat, video, and so on). Finally we have added some new in-demand metrics across the Agents and Interaction Details widgets.
Outbound Support for Interaction Details
The Interaction Details widget type has been extended to support Internal and Outbound alongside Inbound. To better support these additional interactions this widget type also has some new metrics:
- Initial Direction: The direction of the interaction when it began. It can be either Inbound (external party initiated), Outbound (agent initiated to external party), or Internal (agent initiated to another agent).
- Hold Time: The time that any party spent on hold (calls), or the interaction was parked (cases). If multiple hold events coincide for multiple parties then elapsed time is reported
- Interrupted Time: The time that an interaction was interrupted so the agent could handle higher priority interactions. Only non-live interactions can be interrupted.
- Talk Time: The time an agent spent connected to another party. For Inbound this is from the moment the agent accepts the interactions, for Outbound and Internal it is from when the second party connects.
- Interaction State: Connected - Interrupted: The interaction has been interrupted (and put aside) while the agent focuses on a higher priority interaction.
- Interaction State: Completed - No Answer: An interaction initiated by an agent where the party being contacted did not answer.
- Interaction State: Completed - Agent No Answer: An outbound or internal interaction where initiating agent did not answer.
Existing widget metrics names and calculations have been updated to support the multiple directions types:
- Customer ID renamed to Source Address: The address of the party that initiated the interaction. For Inbound interactions this is the address of the customer. For Outbound interactions the address is the call-back number. For Internal interactions the address is the agent's name. The source address for a call is the phone number and changes appropriately based upon the media types, for example cases may display an email address.
- Dialed Number renamed to Destination Address: The address of the party being contacted by the interactions. For Inbound this is the address which the customer used when contacting the contact center. For Outbound interactions this is the address of the customer being contacted. For Internal this is the name of the agent being contacted.
- Handle Time calculation update: The time that an agent or agents have spent working with an interaction. If multiple agents have handled the interaction, all agents' handle time in relation to the interaction is included. Handle Time includes the time agents have spent in Alerting, Connected, and Wrap states, for interactions where an agent connected.
- Service Name calculation update: The service name of the interaction plan where the interaction was first processed.
- Time To Answer calculation update: For Inbound interactions this is the time between the interaction entering the queue and when the agent accepted the interaction. For Outbound and Internal this is the time between the interaction beginning (Offered Outbound/Internal) and the second party connecting (Connected Outbound).
As well as this step forward in metrics the addition of outbound to this widget type provides the ability to report on outbound Audio Problems, Post Call Quality Rating, and Call Logging Disposition codes.
Additional Agent Metrics
The Agent Widget has been extended to provide greater insight into the running of a contact center. The following new metrics have been added:
- Offered Internal: The number of interactions offered to the agent from another agent. This can be a direct internal interaction or a consult. These interactions can end up Accepted Internal, Unexpected or Failed.
- Offered Inbound: The number of interactions that were offered to the agent from a queue, these interactions can end up Accepted Inbound, Unexpected or Failed.
- Offered Outbound: The number of interactions initiated by the agent. These can also be system generated outbound interactions. These interactions can end up Accepted Outbound, Unexpected or Failed.
- Accepted Inbound: The number of interactions successfully connected to an agent that were delivered from a queue.
- Accepted Internal: The number of interactions successfully connected to the agent from another agent. This can be a direct internal interaction or a consult. These interactions can end up as Connected Internal or No Answer.
- Accepted Outbound: The number of interactions initiated and accepted by the agent. These can also be system generated outbound interactions. This does not indicate a connection to a second party. These interactions can end up as Connected Outbound or No Answer.
- Connected Outbound: The number of Outbound interactions initiated by the agent and successfully connected to a second external party.
- Connected Internal: The number of Internal interactions initiated by the agent and successfully connected to a second agent party.
- No Answer: An interaction initiated by an agent where the party being contacted did not answer.
- Total Hold Time: The total time that any party spent on hold (live interactions), or the interaction was parked (non-live interactions). If multiple hold events coincide for multiple parties then elapsed time is reported.
- Total Interrupt Time: The total time that an interaction was interrupted so the agent could handle a high priority interaction. Only non-live interactions can be interrupted.
- Total Unique Customers: The number of unique customers the agent has either received Inbound interactions from or initiated Outbound interactions to. Internal interactions are excluded. The Customer is identified by the Source Address for Inbound interactions, and the Destination Address for Outbound interactions.
Existing widget metrics names and calculations have been updated to better support the multiple directions types:
- Not Answered renamed to Agent No Answer: The number of interactions that the agent rejected or missed. Agent No Answer is a subset of Unexpected.
- Number Busy renamed to Agent Number Busy: The number of calls that the agent did not answer because their line was busy. Agent Number Busy is a subset of Unexpected.
- Answered renamed to Accepted: The sum of Accepted Inbound, Accepted Internal or Accepted Outbound
- Avg. Handle Time calculation update: The average time the agent spent handling interactions, which is the average of the sum of Alerting Time, Connected Time and Wrap Time: excluding Parked (non-live Hold) and Interrupted time.
- Avg Ringing Time renamed to Avg Alerting Time: No change.
- Failed renamed to Failed to Connect: The number of interactions that failed to connect to an agent possibly due to configuration or network errors.
- Interaction State - Failed renamed to Interaction State - Failed to Connect: No change.
- Interaction State - No Answer renamed to Interaction State - Agent No Answer: No change.
- Interaction State - Number Busy renamed to Interaction State - Agent Number Busy: No change.
- Interaction State - Ringing renamed to Interaction State - Alerting: No change.
- Offered calculation update - The sum of Offered Internal, Offered Inbound, and Offered Outbound.
- Significant Interactions calculation update: The number of interactions that were connected to more than one party (agent plus another) for longer than the configured threshold. For example, the number of calls where the agent was connected to the customer for at least 1 minute. Significant Interactions can be used to filter out voicemail and short, insignificant conversations.
- Max Handle Time calculation update: The longest time any interaction was handled by an agent, which is the longest of the sum of Alerting Time, Connected Time and Wrap Time: excluding Parked (non-live Hold) and Interrupted time.
- Min Handle Time calculation update: The shortest time any interaction was handled by an agent, which is the shortest of the sums of Alerting Time, Connected Time and Wrap Time: excluding Parked (non-live Hold) and Interrupted time.
- Total Talk Time calculation update: The total time that any party spent on hold (live interactions), or the interaction was parked (non-live interactions). If multiple hold events coincide for multiple parties then elapsed time is reported.
For more information about metrics available in Dashboards, see Dashboard metrics.
We continue to make the VCC platform more open to integration than ever before.
User-Level API Credentials
Until now API Credentials within VCC have been generated at the account level—meaning that API credentials had Admin level privileges. Within this release we have improved the granular permissions you can apply by allowing API Credentials to operate at the user level.
Any new API Credentials generated within API Admin will now be attached to the user generating them. In addition, should that user be marked as inactive or deleted, then those API credentials will cease working.
Account-level API credentials
Many of our APIs still operate at account levels—meaning that even with user-level credentials, the APIs will grant Admin privileges. We are now beginning to migrate all APIs to enforce user permissions.
The first API to be migrated is the Interaction Content API. API requests made to this API can only access the data the same user could through the application. This allows customers to provide programmable access to a subset of their dataset.
Delete Content Using Interaction Content API
A new major version of the Interactions API is now available and provides customers with the ability to:
- Page through interactions more effectively with continuation token paging
- Delete interaction content—including call recordings—for an individual interaction
- Bulk delete interaction content—including call recordings—for up to 1000 interactions at a time
This version works in tandem with the new User-Level API Credentials. Meaning that it can only be used with user credentials and will return data and validate permissions based on the user. The API will not be able to do more than the user can through the portal.
For a migration guide from the existing version, or to review these features in detail visit Interaction Content API Documentation.
Target Time-to-Answer Metrics for Virtual Queues
Within VCC a collection of skills can be grouped into a Virtual Queue. This virtual queue can then be used to optimize route, or for reporting. In this release we have extended the reporting capability into the Insights Stats API as part of the interaction endpoints. This provided the user with a "
targetTimeToAnswer" metric for each virtual queue within a queue event.
"interactionPlanName": "Customer Support Plan", "presentedSkills": [
"virtualQueue": "Billing Queue",
This time can be used in conjunction with the
duration properties to calculate Service Levels in an external system.
Delete Interaction Content in Bulk
As part of this release users are able to delete the Interaction Content—including Call Recording—for up to 1000 interactions in bulk. This functionality is available within the Interaction Search component of the VCC portal.
For information about deleting interaction content in bulk, see Deleting interaction content.
Alternative Content Storage Locations
Within each region we operate, Interaction Content—including Call Recordings—has previously been stored in one core location, as detailed below:
- EMEA - London
- NAM - Virginia
- APAC - Sydney
We can now offer a second storage location in each region. Providing customers even more control of where their data is stored. The updates regional storage locations are:
|Region||Storage Locations Available|
|EMEA||London | Frankfurt|
|NAM||Virginia | California|
|APAC||Sydney | Singapore|
You can see where your data is stored now within the Data Retention area of VCC:
To adjust your storage location, contact the Vonage support team. A change in location is only respected for future Interaction Content.
For information about data retention, see Data Retention.
Report Audio Problems
The Spring ‘20 release included a major update to the button that agents can use to report audio quality problems during a call. This was of particular benefit for inbound calls.
The Spring ‘21 release includes improved support for outbound calls in Dashboards, which means you can now get the same benefits for outbound calls.
VCC users can now:
- Specify the type of problem being experienced, e.g. too loud, too quiet, echo, distortion, background noise, delay, or other (the button can be used multiple times in a single call)
- View reports of audio problems for inbound and outbound calls in Dashboards
- Retrieve the audio problems reports through an API
This feature was enabled on request in Spring ‘20 and will roll out to everyone by default in this release.
For information about reporting audio problems in ContactPad, see Reporting problems.
Post Call Quality Rating
To truly understand your contact center you need to know when things are going well in addition to when they’re going wrong. In Spring ‘20, the Report Audio Problems feature was added to VCC and Post Call Quality Rating was added in Summer ‘20.
Report Audio Problems is an important feature that helps VCC customers self-serve and provides VCC operations and support staff with early visibility of developing problems. However, because this feature only reports problems, it gives a distorted view of VCC call quality.
Post Call Quality Rating acts a complement to the existing Report Audio Problems feature by allowing users to provide a single overall rating (good or bad) at the end of a call. Users provide a rating which maps to an Opinion Score: a whole number between 1 and 5. These Opinion Scores can be averaged into Mean Opinion Scores or MOS: a number between 1.0 and 5.0. The MOS can be calculated for an interaction (as multiple VCC users can be engaged on a call), a location, an entire VCC account and so on.
The Opinion Scores and MOS are available in Dashboards and Statistics alongside the data from Report Audio Problems and together this provides VCC customers and VCC staff with a holistic view of VCC call quality.
This feature was enabled on request in Summer ‘20 and rolled out to everyone by default in this release.
For information about Post Call Quality Rating, see Post Call Quality Rating.
When an agent is in a ready state, the platform will automatically deliver any eligible interactions. If the agent is not ready for an interaction, the agent may click the release button in ContactPad rather than allow the call to ring out. Previously, clicking Release in ContactPad during the ringing phase would always terminate the call—whereas clicking Decline in WebRTC would route the call back to the queue.
Within the Spring '21 release, we aligned the two behaviors. Now during the ringing event for an inbound call, if the agent selects Decline or Release, the call is delivered back to the queue.
For information about rejecting a call in ContactPad, see How do I reject an incoming call? in Working with an inbound call.
Overview - Now Generally Available for Voice
Cadence is now Generally Available. We introduced this in Winter ‘21 as early access. We have improved the resilience of the product to offer seamless disaster recovery in line with our platform standard. Should an incident impact the performance of the platform which requires your account to be moved to
another node, Cadence will now continue to operate without any overhead from administrators of your account.
Cadence for Sales Leaders
Studies show that it’s currently taking over four times as many attempts to connect with prospects compared to the early 2000s—as many as eight attempts on average. The typical sales representative tries only twice before they give up.
The Vonage Cadence solution was designed to specifically navigate this by allowing you to configure your entire outbound communications strategy whilst ensuring the management of that process is completely automated for your sales representatives. This reduces their time spent on administration and removes the thought process required to follow the rules of your outbound campaign. This ultimately frees them up to do what they do best—sell.
Once implemented, Vonage Cadence can help you:
- Remove process overhead
- Reduce representative administration
- Prioritize high-value prospects
- Increase lead qualification
- Speed up onboarding
- Increase dial rates
- Increase connections
- Generate pipeline
- Encourage upsell and cross-sell
- Deliver insights towards success
- Iterate towards repeatable success
Cadence for Service Leaders
Leading analysts have seen that nearly 90 percent of companies compete on customer experience alone. With your existing customer base being your most valuable asset, it’s imperative you have a strategy to effectively communicate with your customers when required. This could be reacting to CSAT scores,
rescheduling appointments, or simply following up when you said you would.
As consumers, our expectations have never been higher. However, 31 percent of service teams feel that their leaders treat customer service as an expense, not an opportunity for growth.
Once implemented, Vonage Cadence can help you:
- Ensure data driven follow ups
- Improve CSAT
- Increase customer loyalty
- Encourage upsell
- Reduce churn
- Deliver on Service Level Agreements
- Optimize agent utilization
For information about Cadence, see Cadence.
Beta/Early Access Program
Our Beta/Early Access Program gives some customers access to VCC enhancements that are still under development. Incorporating feedback from customers during the program allows us to continue improving these features, which ensures that every feature fulfills its purpose in a range of different
environments. All customers using features in the Beta/Early Access Program must agree to participate in the feedback process.
If you are interested in gaining access to a feature in the Beta/Early Access Program, please contact your Customer Success Manager or Account Manager. Participation in this pilot program is at the discretion of Product Management and not guaranteed.
Enabling the Salesforce Service Cloud Voice “Bring Your Own Telephony” Pilot
According to Salesforce, Service Cloud Voice unifies phone, digital channels, and CRM data in real-time in one centralized console. This is the contact center of the future—intelligent, unified, and fast. Now companies can:
- Integrate telephony and route calls on a single platform: Agents can work from a single, powerful console. This eliminates the need to toggle back and forth from multiple screens and find manual workarounds.
- Boost productivity by reducing data entry and call wrap-up time: With automatic transcription capabilities, agents can now focus on what actually matters—addressing the customer’s needs quickly and accurately.
- Leverage AI-powered agent recommendations: With call transcriptions surfacing in real-time directly in the Service Cloud console, Einstein AI can now provide recommended solutions and next best actions for the agent in the background. This reduces average call time and improves both the agent and customer experience.
- Empower supervisors with real-time omnichannel visibility: A new supervisor console lets managers view all calls and digital conversations in real-time. This allows managers to monitor where calls are being routed, evaluate each agent’s skill set, and determine which conversations may require assistance, live coaching, or post-call coaching.
For example, when a customer calls in, the Vonage transcription capabilities turn speech into text that can be viewed alongside customer data in the console. This empowers the agent to deliver a personalized experience based on factors like the customer’s purchase history, warranty information, or past
interactions across channels. With the call converted to text, Einstein AI can go to work by serving up recommended responses, knowledge articles, and next best actions to the agent.
VCC now enables Salesforce to deliver these benefits through the power of our Interaction Architect, Salesforce integration, and audio quality. These are key areas to a successful deployment of Service Cloud Voice.
To use Service Cloud Voice, it is possible to continue with existing call flows, users, and contact numbers—though items like case pops may need to be changed. A review of your VCC implementation is recommended to understand what changes need to be made, if any, to take advantage of Service Cloud Voice.
It is important to understand that the existing integration between Salesforce and VCC does not change and will continue to provide the existing benefits. Service Cloud Voice just provides a possible alternative to how you want Salesforce and VCC to work together
to provide benefit to your contact center.
Note that adding this service may incur professional services time and additional product charges. If you would like to be considered for the Beta/Early Access Program, please discuss it with your Customer Success Manager or Account Executive. Participation in the pilot program is at the discretion of Product Management and not guaranteed.
Analytics Dashboards - North America Only (Beta)
Historic reporting within a contact center is a key pillar of success. The new Analytics offering will bring the power of a Business Intelligent system into the VCC Portal for customers of all types. This offers the ability to:
- Report historically on Interaction and Agent data
- Create custom Analytics Dashboards to meet your needs
- Download reports in a variety of formats
- Build a custom formula calculation to deliver truly bespoke reporting
This feature is open for limited beta access in North America only. Speak with our Account Management team if you want to help us shape the future of VCC reporting.
Post Interaction Processing (Beta)
The interaction plans you are able to configure within VCC can be incredibly powerful. You’re able to integrate with your third-party applications such as backend databases or your CRM which can help route, prioritize, and skill interactions as we learn more about the consumer. This can enable the implementation of a self-serve IVR or simply remove the painful chain of menus for a more personalized experience—and make sure your consumers speak with the right people, in the right order.
The problem today is that once the interaction has finished, all of this processing stops. With the Spring ’21 release, VCC enables you to initiate a fresh interaction plan after the processing of an interaction has finished. The caller doesn’t need to hang around for this, as you will be able to conditionally evaluate the outcome of the previous interaction to determine what, if anything, you decide to do next.
Never miss a call
Abandoned calls are one of many challenges for all contact center leaders. The battle to keep abandonment rates low never stops—whether that’s to meet SLAs, maintain great CSAT/NPS/Customer Loyalty, or make sure you connect with that inbound lead.
With post interaction processing, you can evaluate the profiles of abandoned callers before taking steps to get back in touch—particularly if they are high value to your business. You can add them to a dial list, or initiate a queued callback or even a more robust multi-step outbound campaign through Cadence.
If you have implemented post call surveys to track customer feedback, you can now easily process the results from within the interaction architect and push them into whatever third-party application for analysis, such as an object linked to the contact within your CSM. Depending on the feedback, you could
automatically initiate follow ups to help improve the customer’s experience with your business. But remember, you can first evaluate caller profiles before determining if they offer enough to your business.
To facilitate real processing of interactions, it’s important to understand the context of what happened before. Using Data Source Mappings, you can see the outcomes of interactions from within Dashboards or pull information directly from the insights stats API. This allows you to see if the call was delivered or abandoned, initiated a callback, broke out of the queue, or ended because the caller hung up before reaching a queue. It will also allow you to customize what’s presented within Dashboards, so you can see other key checkpoints within your Interaction Plan, such as whether the customer self-served (and how).
System Status Changes
We are aligning the naming convention across both VCC System Status pages. This will affect the name shown in incident alerts, but existing notification subscriptions will continue.
With this release, the VCC Status Page names have been updated as detailed below:
|Current Name||New Name|
|Cloud 11 - UK & Europe||EMEA - London|
|Cloud 8 - UK & Europe||EMEA - Frankfurt|
|Cloud 17 - US||NAM - Virginia (Cloud 17)|
|Cloud 16 - US||NAM - California (Cloud 16)|
|Cloud 12 - APAC Sydney||APAC - Sydney (Cloud 12)|
|Cloud 14 - APAC Singapore||APAC - Singapore (Cloud 14)|
|N/A||EMEA - London (Cloud 8)*|
|N/A||EMEA - London (Cloud 11)*|
*Added in the last 4 months as part of the EMEA Infrastructure Refresh
In addition the VCC Uptime Page, names have been updated as detailed below:
|Current Name||New Name|
|EMEA - Cloud 11||EMEA - London|
|EMEA - Cloud 8||EMEA - Frankfurt|
|NAM - Cloud 17||NAM - Virginia (Cloud 17)|
|NAM - Cloud 16||NAM - California (Cloud 16)|
|APAC - Cloud 12||APAC - Sydney (Cloud 12)|
|APAC - Cloud 14||APAC - Singapore (Cloud 14)|
|N/A||EMEA - London (Cloud 8)*|
|N/A||EMEA - London (Cloud 11)*|
*Added in the last 4 months as part of the EMEA Infrastructure Refresh
Along with the exciting new functionality added to the product with every release, we are also working to retire older parts of the product. The removal of functionality within our product is completed in up to these stages:
Intent to deprecate
This is an optional stage that gives users early warning of our intent to deprecate functionality. It is most commonly used when an alternative is announced, and gives users the ability to migrate ahead of the functionality becoming deprecated. At this stage we encourage customers to stop using the mentioned product functionality, and migrate to an alternative.
This indicates that a piece of functionality is no longer supported. The functionality will continue to work, but no new enhancements or bug fixes will be made (with the exception of security vulnerabilities) and new functionality may not be compatible. We commonly announced the target End of Life date when deprecating. At this stage customers must stop using the mentioned product functionality, and migrate to an alternative.
End of life
The date in which we will remove functionality is referred to as the End of Life. After this date the functionality will either cease working entirely,
Salesforce Managed Packages—deprecated and end of life
The following packages and earlier versions have been deprecated:
|End of Life|
Vonage Contact Center for Salesforce
18.251 or higher
18.250 or lower
|18.231 or lower|
Vonage Contact Center Connect
19.100 or higher
18.259 or lower
|16.118.1 or lower|
Vonage Contact Center Advanced Reporting
2.57 or higher
2.56 or lower
|2.44 or lower|
End of life for deprecated versions: Summer '21 release.
Call Recordings (SFTP Download) - Deprecated
This feature has now been replaced by the Interaction Content API. Customers may no longer request Secure FTP access to their Call Recordings for periodic download of data. This can now be achieved through the Interaction Content API.
Secure FTP may still be provided upon Termination or Expiry of the Agreement, as described in the Data Retention Service Description.
Projected End of Life: First half of 2022
Real Time Admin Functions - Deprecated
With the introduction of Supervisor Access to User Admin, we have full parity with Real Time administration functions. As of the Spring ‘21 release, administration functionality within Real Time is deprecated.
All other functions, such as changing agents states and call monitoring, will remain supported within
Projected End of Life: Summer ‘21 Release
Skill Management—end of life (update)
We announced the deprecation of Skill Management in Summer ‘20. This will now enter End of Life alongside the Real Time Admin Functions.
Projected end of life: Summer '21 release.
Call Recordings (Search Page)—end of life (update)
We announced the deprecation of the Call Recordings page in Summer ‘20. The End of Life of this function is now moved to Summer ‘21. However, from this release users will see a deprecation banner within the Call Recording search page.
Projected end of life: Summer '21 release.