| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
| Info | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Interactions in Salesforce and VCCInteraction types
VCC makes different routing decisions based on the interaction type. Agents can perform different tasks on an interaction based on its type. Salesforce objects, work items, and interactionsSalesforce uses different terminology for the items known in VCC as interactions:
The Salesforce record may be a web chat or a case that arrive in Salesforce through Live Agent or email respectively. Defining a service channel in Salesforce for a Salesforce object enables Salesforce to route records of that type and makes such records into work items. |
...
- When the agent changes their state in ContactPad, their presence status updates in the Salesforce Omni-Channel widget
- When the agent changes their presence status in their Omni-Channel widget, their state updates in ContactPad
- When the agent logs in to ContactPad, the agent goes into an online presence status in the Salesforce Omni-Channel widget
- When the agent logs out of ContactPad, the agent goes offline in the Salesforce Omni-Channel widget
- When the agent goes offline in Salesforce Omni-Channel, the agent logs out of ContactPad
| Note |
|---|
When Salesforce assigns a chat to an agent, and auto-acceptance is enabled, the agent's state in ContactPad automatically changes to Busy Inbound. If auto-acceptance is not enabled, the chat shows as Alerting in ContactPad until the agent accepts it in the Omni-Channel widget. You can optionally configure changing the agent's state in ContactPad to Busy Inbound whenever the agent's presence status in the Omni-Channel widget is updated to a busy status. For more information, see Integrating with Salesforce Omni-Channel presence. |
...
With external routing, VCC can route all types of interactions—live (such as phone and video calls), semi-live (such as web chats) and non-live (such as emails). For more information about interaction types, see Interaction types. External routing can also route custom objects. Custom objects are routed in the same way as cases and are treated as non-live interactions.
...
ContactPad with multi-interaction routing
When multi-interaction routing is available in your account, agents will notice some changes in ContactPad. For information about ContactPad, see Overview of ContactPad. With multi-interaction routing, agents can work on multiple interactions—of different interaction types—at the same time.
| Section | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Queue information panel
|
...
If enabled, you can configure optimum load settings for your account. For information about configuring optimum load for your account, see Configuring multi-interaction routing.
| Note |
|---|
The optimum load feature does not work if either of the two interrupt toggles have been enabled: |
...
If cross-media consult is enabled for your account, an agent can consult with a third party while they are handling a semi- or non-live interaction. The third party could be another agent or someone on another phone number. The agent always performs the consult using a phone call.
For information about using cross-media consult, see Using multi-interaction routing.
Transferring interactions
...