Vonage for Service Cloud Voice integrates Vonage Contact Center (VCC) with Salesforce's Service Cloud Voice. For information about Service Cloud Voice and its benefits, see Service Cloud Voice (Salesforce help). Vonage for Service Cloud Voice enables Salesforce to deliver these benefits using VCC.
Your existing integration between Salesforce and VCC shouldn't change much, 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 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.
| In this page |
|---|
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:
| Feature | Pure | Hybrid |
|---|---|---|
| SCV Voice Call object creation for voice calls |  | |
| Task creation for voice calls |  | |
| Presence mapping from SCV to VCC | |
Presence mapping doesn't work in both modes at the same time. For more information see the Presence mapping between SCV and 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, or consult, transfer, or add a third party to the call for a conference. 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. (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.
Agents can also consult with an external number. To do so, the agent clicks Add Caller, then—instead of selecting an agent—clicks Keypad and enters a number to consult with. This puts the original call on hold while the original agent is connected to the external number. The agent can then perform the same actions as if they were consulting with an agent.
Alternatively, the agent can consult with a VCC interaction plan—or, more specifically, a VCC agent servicing the interaction plan—or transfer (warm or cold) to an interaction plan. To do so, the agent clicks Add Caller and selects an interaction plan from the presented list. This puts the original call on hold while the original agent is connected to the interaction plan. The agent can either hang up to perform a cold transfer to the interaction plan, or wait to be connected to an agent to consult. If the agent waits to be connected, on connection, the original agent can perform the same tasks as described for a consult to agent earlier in this section.
For information about consulting, transferring, and merging calls, see Add Callers or Transfer Calls (Salesforce help).
Transcription
If SCV is enabled for your account, Vonage transcribes an agent's calls if transcription is enabled for that agent and if their calls are recorded. 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.
Transcription with taking payments in SCV
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 Payments in Vonage Contact Center.
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:
- Chats. Agents use the transfer button in the chat interface to transfer chats to any of the following:
A user
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
The selected chat button transfers the chat to a Salesforce queue.A Salesforce queue
- A Salesforce skill
Cases. Agents can transfer cases by changing the case owner to one of the following:
A user
Agents can transfer chats to any Salesforce user in the presented list, some of whom may be linked to agents in VCC.
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
Transferring to a Salesforce queue
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.
Omni-Channel flow routing
When using SCV with VCC, you can delegate routing decisions for inbound calls into VCC to Salesforce's Omni-Channel flows. When configured, VCC notifies Salesforce about applicable inbound calls. Salesforce then uses an Omni-Channel flow to determine which interaction plans VCC should route the calls to next.
For information about configuring VCC to use Salesforce Omni-Channel flows to make routing decisions, see Configuring Vonage Contact Center to use Salesforce Omni-Channel flows.
Presence mapping between SCV and VCC
Salesforce user presences and VCC agent states are synchronized in Salesforce and VCC.
This means that when a Salesforce user's presence changes in the Omni-Channel widget or utility within Salesforce, VCC updates the state of the corresponding agent in VCC. Conversely, when a VCC agent's state changes within VCC, the presence of the corresponding Salesforce user is updated. (This applies to both automatic and manual Salesforce presence and VCC state changes.) The presences and states change based on the mappings configured in VCC.
This ensures that VCC and Salesforce don't assign interactions to Salesforce users and VCC agents who aren't available. It also means that VCC is able to report on the agent's activity within Dashboards and other reporting features. For information about mapping Salesforce presence statuses to and from VCC agent states, see the Mapping Salesforce user presences and VCC agent states section in Configuring Vonage for Service Cloud Voice. Presence updates when using Vonage for Service Cloud Voice in hybrid mode When presence updates are enabled for SCV, updates will only happen for agents using SCV. Presence updates will not work for agents who use ContactPad with the VCC and Salesforce integration.
High Velocity Sales
If you use High Velocity Sales (HVS) (soon to be renamed Sales Engagement) in your Salesforce organization, you can use HVS features with Vonage for Service Cloud Voice. Agents can use SCV to progress prospects through existing HVS cadences.
For information about High Velocity Sales, see High Velocity Sales (Salesforce help).
After conversation work
Using Vonage for Service Cloud Voice, you can benefit from a pilot feature in Salesforce, After Conversation Work. Most calls require work after the call ends—for example, sending an email, writing some notes, or updating a case. The After Conversation Work feature enables supervisors to set and manage the amount of time agents spend on work after a conversation. This tells agents roughly how much time to spend on tasks.
For information about After Conversation Work, see Give Agents Time for After-Conversation Work (Pilot) (Salesforce help) and Wrap Up After a Call (Beta) (Salesforce help).
Desk phone support
Desk phone support in Salesforce enables SCV users to alternate the type of phones they can receive calls on. In SCV, phones are categorized as:
- 'Softphones', such as WebRTC
- 'Desk Phones'. Desk phones include:
- Desk phones
- Mobile phones
- Any other phones that use a direct inward dialing (DID), or direct dial-in (DDI), number such as Vonage Business Communications (VBC).
Users can set the phone number to use with their 'Desk phone'. Phone numbers must be in E.164 format, which includes the country code. For information about telephone numbers in E.164 format, see Telephone number formats in Vonage Contact Center in Salesforce.
The user doesn't need to rely on an administrator to make these changes for them.
Known Salesforce limitation
For information about desk phone support in Service Cloud Voice, see Use Desk Phones with Service Cloud Voice (Generally Available) (Salesforce help).
Limitation
Vonage for Service Cloud Voice has the following limitations:
- Call controls: Mute and DTMF digits are only supported for agents using WebRTC.
- Only agents can be added as participants to calls.
- Agents cannot use DTMF to warm transfer interactions to an interaction plan. You must clear the Allow DTMF Transfer check box in interaction plans that agents can transfer interactions to.
In this section |
|---|