| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Your existing integration between Salesforce and VCC shouldn't change much, if at all, and continues to provide the existing benefits. Service Cloud Voice just provides a possible alternative to how Salesforce and VCC work together to provide benefit to your contact center.
You can use Service Cloud Voice with existing interaction plans, users, and contact numbers. We recommend that you review your VCC implementation to understand what changes need to be made, if any, to take advantage of Service Cloud Voice. For example, you may want to associate the objects that currently pop with the new voice call object.
...
| Table of Contents |
|---|
Pure and hybrid modes of using Vonage for Service Cloud Voice
When you have configured your VCC account for Service Cloud Voice, you can choose for all of your agents to use SCV, or for some to still use ContactPad with the VCC and Salesforce integration. The different modes are:
- Pure. All of your VCC agents are using Service Cloud Voice.
- Hybrid. Some your VCC agents are using Service Cloud Voice and some are using ContactPad with the VCC and Salesforce integration.
The following features are available in the different modes:
...
Presence mapping doesn't work in both modes at the same time. For more information see the Presence mapping from SCV to VCC section later in this page.
Features
If SCV is enabled and you have configured your VCC account, agents can use many SCV features including the following:
Making and receiving calls
Using SCV, agents can make and receive calls.
To make an outbound call using SCV, an agent can click a phone number in a Salesforce record, or they can enter the phone number in the Omni-Channel utility. When the agent makes the call, VCC initiates the call to the target number.
When someone, for example a customer, makes an inbound call into VCC, VCC routes that call through the applicable interaction plan to a VCC agent. The call appears in the agent's corresponding Salesforce user's Omni-Channel utility in Salesforce.
While connected to an inbound or outbound call, an agent can work with that call in the Omni-Channel utility. The agent can mute the call, put the call on hold, record the call, and so on. For information about making and receiving calls in SCV, see Answer and Make Calls (Salesforce help).
Consulting, transferring, and conferencing (or merging) calls
When using SCV with VCC, agents can consult, transfer, and merge calls.
While on call, an agent can add another agent to consult with them about the call. To do so, the agent clicks Add Caller and selects an agent from the presented list of agents and interaction plans. (The agents in the presented list are Salesforce users, all of whom are linked to agents in VCC.) This puts the original call on hold while the original agent is connected to the agent chosen from the list. The original agent can then perform one of the following actions:
- Swap between original call and consult.
- End the consult.
- Perform a warm transfer to the other agent (by leaving the call themselves).
- Combine the original call with the consult. Combining the calls is known as merging in SCV—merging is called conferencing in VCC.
Alternatively, the agent can do a cold transfer of the call to a VCC interaction plan. To do so, the agent clicks Add Caller and selects an interaction plan from the presented list of agents and interaction plans. The call is immediately transferred to the interaction plan.
For information about consulting, transferring, and merging calls, see Add Callers or Transfer Calls (Salesforce help).
Transcription
If SCV is enabled for your account and if transcription is enabled for an individual agent, Vonage transcribes that agent's calls. Transcription turns the customer's and the agent's speech into text in real time. During a call, the transcript appears in the call's voice call record so the agent can view transcription text alongside customer data.
Vonage uses the Google Cloud Speech-to-Text API to transcribe the calls. Vonage can therefore transcribe calls in all the languages that the API supports. For a list of supported languages, see Language support (Google help). Vonage transcribes calls in your account's default language, unless the default language is overridden for an individual call. For information about overriding the default language for calls, see the Overriding the transcription language for individual calls section in Configuring Vonage for Service Cloud Voice.
| Note | ||
|---|---|---|
| ||
Using SCV an agent can take a payment using VCC's payment solution. Depending on the implementation, payments may involve transferring a customer to an interaction plan in VCC. In this case, after the payment is made, the agent and customer can be reconnected if required. When reconnected, if the agent later clicks to consult with another agent or interaction plan, transcription of the call will stop. The call itself will continue and the agent can continue to consult with—and optionally transfer the call to—a third party, or return to the customer. For information about VCC's payment solutions, see Vonage for Service Cloud Voice. |
External Routing
If you have integrated VCC with Salesforce external routing, when interactions arrive in Salesforce, Salesforce delegates routing decisions to mapped interaction plans in VCC. Where configured, Salesforce uses VCC to route chats, cases, and messages (for example, WhatsApp messages) alongside phone calls.
When using Salesforce with external routing and SCV, in addition to phone calls, agents can transfer the following interaction types:
...
A user
| Note |
|---|
Agents can transfer chats to any Salesforce user in the presented list, some of whom may be linked to agents in VCC. |
A chat button
| Note |
|---|
| The selected chat button transfers the chat to a Salesforce queue. |
...
A Salesforce queue
...
Cases. Agents can transfer cases by changing the case owner to one of the following:
A user
| Note |
|---|
Agents can transfer chats to any Salesforce user in the presented list, some of whom may be linked to agents in VCC. |
| Note |
|---|
Due to a Salesforce limitation, when a case is transferred to another agent, the new agent will not receive an item in the Omni-Channel utility. However, the case's owner will be changed to the agent and, if configured in Salesforce, the agent will receive a notification email. |
...
A Salesforce queue
| Note | ||
|---|---|---|
| ||
Agents can transfer a chat or a case to a Salesforce queue, either by selecting the queue directly or by selecting a chat button. If the queue uses external routing, Salesforce will route the chat to the mapped interaction plan in VCC. The interaction plan can tag the transferred case with required skills and deliver it to the most appropriate agent. |
For information about integrating VCC with Salesforce external routing, see Configuring Salesforce external routing for Vonage Contact Center.
Presence mapping from SCV to VCC
...
Limitations
| Note |
|---|
Vonage for Service Cloud Voice has the following limitations:
|
In this section | |
|---|---|
|
...