A customer emails about a billing issue. They receive no response, so they call. The service rep speaking with them on the phone opens a new case. Later that evening, the customer submits a form through a portal, opening a third case. It’s the same problem for the same person, split across three records.
Duplicate cases are created when the same customer issue is logged multiple times in Salesforce Service Cloud. Often, customers won't wait for a resolution on one channel before trying another. Other times, they're answer shopping, hitting multiple channels and hoping one rep gives them a more favorable outcome. As a kid, when one parent said no, you'd ask the other, hoping they'd say yes. Except this time, each ask opens a case.
The obvious cost of duplicate cases in Salesforce is the time it takes to find and merge them. The costs nobody budgets for are metric pollution and customers getting conflicting answers from different reps.
Four Ways Duplicate Cases Waste Time in Salesforce
1. Unknowingly working the same customer issue.
A service rep starts working on a case. This typically involves reviewing the history, pulling up knowledge articles, and drafting a response. In a best-case scenario, they immediately notice another rep has already responded on another case before responding to a customer. But chances are, several minutes are spent on an issue another rep is handling.
In a worst case, they send the response. Now the customer has two answers from two reps, and nobody inside the org knows it happened. The duplicate wasted time and created a new customer experience problem. And unless someone catches it, neither rep ever knows.
2. Checking every new case for duplicates.
In some orgs, every new case gets a manual duplicate check. Reps check recent cases on the account, search by email address, scan for similar subjects. If that check takes even one minute, that minute happens every time.
When queues are backed up, it's the part of the job that feels the most pointless.
3. Hunting for information scattered across duplicate cases.
When the same issue is logged more than once, prior conversations, attachments, and details end up spread across multiple pages in Salesforce. If the rep knows about the other cases, they're clicking between records trying to piece together what's already happened. If they don't, they find out from the customer, who has to repeat themselves or reference a conversation they can't see.
Either way, the rep is spending time gathering context instead of resolving the issue.
4. Manually merging cases in Salesforce.
Even when duplicates are identified, merging them takes time. If there are four records, you have to perform the merge process twice, because Salesforce's case merge feature limits you to three cases at a time.
Sometimes, admins restrict merge access because basic Salesforce case merges can't be undone. So the duplicate is identified, passed along, and someone else performs the merge when they can get to it. That's another handoff and another case sitting in someone's queue.
How to Calculate the Cost of Duplicate Cases
Now that we know how duplicates waste time, we can translate that into hard costs. The formula below accounts for two ways duplicate cases waste time: the routine check every new case requires, and the extra time spent working and merging the ones that slip through.
((Annual Cases × Duplicate Rate × (Time Working Duplicates + Time Merging)) / 60)
+ ((Annual Cases × Search Time per Case / 60)
× Hourly Rate
Imagine a mid-sized team running omni-channel support: email, phone, chat, web portal. Customers don’t always wait for one channel to respond before trying another. Some submit the same issue twice. During volume spikes like seasonal peaks, product recalls, service outages, or billing cycles, it gets worse.
Here's what the numbers look like for that team:
- 50,000 cases per year
- 100 service reps
- 10% duplicate rate
- 8 minutes working on a duplicate
- 2 minutes searching per case
- 5 minutes merging
- $25/hour rep cost
That's nearly $70,000 a year.
Vicasso has a calculator for this — plug in your own numbers and see where you land.
How Duplicate Cases Skew Your Service Metrics
The time and labor costs are straightforward to measure. The harder costs to quantify are the ones that compound quietly in your reporting. When one customer issue gets counted as three cases, your case volume is unreliable. A few metrics that suffer:
- Average Handle Time artificially drops when agents close duplicates without doing real resolution work.
- Time to resolution loses meaning when high-touch cases are averaged with instant-close duplicates.
- Cases closed per agent gets inflated by closures that don't represent actual work.
Decisions that rely on those numbers are where it hurts. Take SLA tracking. A duplicate sits in the queue unworked because in a quick search, a service rep can see it is a duplicate. They don’t merge it and move on to their next case. The clock keeps ticking and triggers a breach for an issue being resolved on another case record. If you're reporting on first response violations, the duplicate shows up with legitimate misses. There's nothing that tells your org, "this one was a duplicate, ignore it." You'll have to accept that some percentage of your SLA numbers are wrong and try to guess by how much.
When a backlog is 10 or 15% larger than the actual volume, it feeds into capacity planning and headcount conversations. Any justification for more headcount is based partly on phantom demand.
The data that would tell you how bad things are is the same data that is polluted. People feel the numbers are off, but "our counts include some duplicates" doesn't get you very far in a hiring conversation. Or worse, leadership sees that reps aren't keeping pace with volume and draws the wrong conclusion about productivity.
Filtering duplicates out of your reporting assumes they've already been identified. If they had been, you'd merge them. Catching duplicates before they accumulate gives each case a single owner, one resolution path, and a clean data trail. The metrics that come out of that are based on actual work, not duplicate records.
How Duplicate Cases Hurt Reps and Customers
For service reps, duplicate cases erode trust in their workflows. When queues are padded with issues that are already being handled elsewhere, the work feels less purposeful. Every duplicate they encounter is a reminder that the tools aren't keeping up.
For customers, the experience is inconsistent if two reps respond to the same issue. It makes the company look disorganized. And when responses conflict, customers tend to pick their preferred resolution and ignore other cases. The dropoffs aren't flagged as duplicates and show up as unresolved cases with no customer response. They get counted alongside real open cases in your numbers.
The customer who picked one answer and ignored the other case isn't filling out a positive survey. That kind of experience shows up in satisfaction scores and reviews, and the team may never connect it back to a duplicate. In some orgs, the conflict isn't caught unless the case escalates and someone reviews the full account history.
Why Duplicate Cases Get Worse Over Time
Every new channel and automation rule creates more opportunities for duplicates, and in combinations that are harder to spot. Especially when different teams work different types of cases. As metrics inflate, they become the baseline for year-over-year comparisons, capacity planning, and budgeting. Next year’s targets get set against phantom demand.
If volume spikes, an existing duplicate case problem is amplified. The worst data quality hits you during the moments customers need you the most and leadership is watching closest.
The goal isn’t to limit how customers reach you, but to make it easy to catch and merge duplicates before they accumulate in your metrics. Case Merge Premium is what we built to address it.
