Key takeaways
- Track a balanced set: speed (service level, wait time), quality (first contact resolution, CSAT) and efficiency (handle time, occupancy).
- Optimizing one metric alone, such as handle time, can damage customer experience.
- Telephony data and Salesforce case data are most useful together, linked by call records on the case or contact.
- Dashboards should show trends by queue and team, not just today’s numbers.
Contact centers generate a flood of numbers. The best teams focus on a small set that reflects what customers experience and what drives cost, and they connect telephony data to the CRM so every call has context.
The metrics that matter
| Metric | What it tells you |
|---|---|
| Service level | Share of calls answered within a target time, for example 80% within 20 seconds |
| Average speed of answer | How long callers wait before reaching someone |
| Abandonment rate | Share of callers who hang up before being answered |
| First contact resolution | Share of issues solved on the first contact, without follow-ups |
| Average handle time | Talk time plus hold time plus after-call work |
| Customer satisfaction (CSAT) | How customers rate the interaction, usually from a short survey |
| Occupancy | Share of logged-in time agents spend handling contacts |
Balance speed, quality and efficiency
A team pushed only to cut handle time will rush calls, which lowers first contact resolution and increases repeat calls. A team measured only on satisfaction may spend too long on simple requests. Review metrics together, and use first contact resolution and CSAT as the guardrails.
Connecting telephony and Salesforce
Most cloud contact center platforms, including Service Cloud Voice, Five9, Amazon Connect and Twilio-based solutions, integrate with Salesforce through a softphone, call logging and screen pops. When each call creates or updates a task or voice call record linked to the contact and case, you can report on outcomes, not just call volumes.
Building the dashboards
- Operations view: calls waiting, service level today, abandonment and agents available, by queue.
- Quality view: first contact resolution, repeat contacts within seven days, CSAT trends by team.
- Leadership view: volume trends, cost per contact, top contact reasons and backlog.
Use case reason codes consistently. They reveal why customers call, which is where the biggest savings usually lie: fix the cause, publish a self-service answer, or automate the request.
Turning metrics into improvements
- Coach individuals with their own trends, not team averages.
- Review the top contact reasons monthly and remove avoidable ones.
- Use call recordings and transcripts, where permitted, to understand low CSAT.
- Forecast staffing from historical volume by hour and day.
How to calculate the key metrics
| Metric | Calculation |
|---|---|
| Service level | Calls answered within the target time ÷ total calls offered |
| Abandonment rate | Calls abandoned before answer ÷ calls offered |
| Average handle time | (Talk time + hold time + after-call work) ÷ calls handled |
| First contact resolution | Issues resolved without a repeat contact within a set window ÷ total issues |
| Occupancy | Time handling contacts ÷ time logged in and available |
Agree definitions before reporting. For example, decide whether very short abandoned calls, where the caller hung up within a few seconds, count toward abandonment, and how many days define a repeat contact for first contact resolution.
Data you need in Salesforce
- A record for every call, linked to the contact, account and case where relevant.
- Call direction, queue, wait time, talk time and disposition from the telephony system.
- Consistent case reasons and resolution codes.
- A survey result linked to the case or call for CSAT.
Common reporting mistakes
- Averages that hide problems: a fine daily service level can mask a terrible Monday morning.
- Counting cases instead of customers, so one customer’s repeated calls look like many issues.
- Comparing agents who handle very different call types.
- Reporting volumes without reasons, which hides the fixes that would reduce volume.
Frequently asked questions
What is a good first contact resolution rate?
It varies widely by industry and complexity. Track your own baseline and improve it steadily rather than chasing an external number.
Can Salesforce report on phone metrics?
Yes, when call data is captured in Salesforce through a telephony integration. Some detailed real-time metrics remain in the telephony platform’s own reports.
Should we measure agents on handle time?
Use it carefully and alongside quality metrics. On its own it encourages rushing.
