Beyond screen pop: using Salesforce data to drive smarter routing
Connecting Microsoft Teams and Salesforce is only the first step. The real value starts when Salesforce data can influence what happens to the interaction
A traditional CRM integration may open the right customer record when a call comes in.
Useful
But limited
With CC4Teams, Salesforce data can become part of the routing decision itself.
Salesforce knows the customer, and CC4Teams knows what to do next.
Salesforce can hold valuable information about a customer, Case, Asset, contract, service entitlement, priority, or service relationship.
CC4Teams can use that information together with its own routing logic, including:
Agent skills
Match the interaction with people who have the right knowledge or expertise
Availability and capacity
Take current availability, workload and agent capacity into account
Priority and SLA
Differentiate interactions based on urgency, customer priority or service level
Language and queue status
Apply language requirements and current queue conditions to the routing decision
That makes routing much more informed.
A high priority case can be treated differently. A technical Asset issue can be routed to the right specialist. A customer with a specific service entitlement can receive the handling that matches their agreement.
The CRM does not just sit next to the conversation. It helps shape the conversation.
Move beyond the screen pop
The traditional model is simple:
- A customer calls
- The system recognizes the number
- The Salesforce record opens
That is helpful, but it only tells the agent what to look at.
CC4Teams can go further by using Salesforce data before the interaction reaches the agent.
The question is no longer only:
Which record should we open?It becomes:
Where should this interaction go, and who is best placed to handle it?Use business context to make better routing decisions
Imagine a customer contacts your organization about an existing technical issue.
Salesforce already knows:
- which Account is involved
- which Asset is affected
- whether there is an open Case
- what priority applies
- what service entitlement the customer has
CC4Teams can use that context, along with skills, availability, queue rules, and capacity, to determine the best route.
The interaction can reach the right person with relevant context already available.
Routing is where Salesforce context becomes operational
Synchronizing data is useful.
Using that data to make a better decision is where the integration becomes powerful.
Identify
Find the relevant customer and business context
Orchestrate
Combine Salesforce data with skills, priority, SLA, availability and capacity
Route
Send the interaction to the most appropriate available agent or workflow
Handle
Give the agent the interaction with the right context
Automate
Capture the outcome and send relevant information back to Salesforce
This turns Salesforce from a passive CRM record into an active part of the Customer Contact process.
Better routing creates a better conversation
Smarter routing is not just about moving an interaction faster from one queue to another.
It is about starting the conversation with a better chance of success.
The right person
Route the interaction based on the expertise needed to handle it
The right priority
Use customer, Case and service information to determine how it should be handled
The right customer context
Give the agent relevant Salesforce information from the start
A stronger starting point
Reduce the need to transfer, search or ask the customer to repeat information
That is the experience the technology should create.
Your CRM already knows a lot. Put it to work.
Organizations invest heavily in building customer and business context inside Salesforce.
That information should not sit in the background while the Customer Contact solution makes decisions without it.
With CC4Teams, Salesforce data can be integrated into how customer interactions are prioritized, routed, and handled.
Salesforce knows the customer, and CC4Teams knows what to do next.
See smarter Salesforce routing in action
Discover how CC4Teams uses Salesforce context throughout the Customer Contact flow, from identification and routing to handling and automated write back.
Request a Salesforce demoPart of our CC4Teams + Salesforce series: practical ways to bring Customer Contact and customer context together inside Microsoft Teams.
Read the Salesforce series
Explore how CC4Teams brings Salesforce customer context directly into Customer Contact in Microsoft Teams.
01
Salesforce Open CTI is retiring. What does that mean for Customer Contact?
What the change means and why it is a good moment to rethink how Salesforce and Customer Contact work together.
02
You already have Microsoft Teams and Salesforce. Why add another desktop?
Bring customer conversations and Salesforce context together without forcing agents to constantly switch between applications.
03
Beyond screen pop: using Salesforce data to drive smarter routing
See how Salesforce data can influence priority, routing and who is best placed to handle each interaction.
