Amazon Connect Cases: When to Merge and When to Link
AWS announced merge and link options for Amazon Connect Cases on Nov. 12, 2026. Merge when two tickets describe the same issue for the same customer and your team needs one case to work from. Link when the tickets share a cause but each still needs its own follow-up.
The simple rule: merge for one customer, one issue; link for related but distinct cases
Use merge when two cases really represent the same support issue for the same customer and the conditions for merge are met. Use link when cases should stay separate but be coordinated together, such as when multiple customers are affected by the same outage. In both situations, the goal is to reduce confusion without losing the operational details that agents need.
When merge makes sense
A practical staging example is two fictional contacts from the same customer about the same billing error. If the cases are eligible under Amazon Connect Cases merge rules, a merge can help reduce duplicate work and create one clearer record for the team. Before merging, review the primary case carefully, confirm the key fields, and check related items so you know which case should remain the anchor record.
AWS documentation notes that a merge is final and cannot be undone. After completion, the secondary case is closed, while the cases are automatically linked. The secondary case is not deleted, which matters for traceability and history. A merge also requires the Cases - Merge permission.
Quick merge versus manual merge
With Quick merge, the primary case keeps its filled fields and takes values from the secondary case for empty fields. With Manual merge, agents can choose which value to keep when the two cases disagree. If you choose to keep all related items, supported items such as comments and contacts can move to the primary case. Files and service-level agreements (SLAs) stay on the secondary case.
That is why staging matters. Use dummy records first to confirm how your team wants to choose the primary case, how often fields differ, and which related items should be reviewed before someone completes a merge.
When link makes more sense
Link is better when the cases are connected but should remain distinct. A common fictional staging example is two different customers reporting service disruption during the same outage. These cases share a common cause, but each customer’s impact, contact history, and follow-up may still need to stay separate. Linking lets agents coordinate the response without collapsing the records into one.
AWS documentation states that linking is done with Cases - Edit. That makes linking a lighter-weight option for coordination, especially when you want to preserve each case’s independent workflow while still making the relationship visible to the support team.
A practical decision framework
- Merge when the cases describe the same customer and the same issue, and merge eligibility is satisfied.
- Choose the primary case first and verify fields and related items before combining records.
- Use quick merge when you want the primary record to stay dominant and fill in blanks from the secondary.
- Use manual merge when values differ and you need agents to reconcile the final outcome.
- Link when the cases are related operationally but must remain separate, such as different customers affected by one outage.
- Use staging data and dummy records before any real operational rollout so your team can validate process choices safely.
Why this distinction matters for support operations
Merging can simplify case volume, but it also changes the shape of the record and ends the secondary case. Linking keeps cases separate, which is often better for multi-customer incidents, escalations, or situations where each customer needs an independent path while still sharing context. The best choice is the one that preserves accuracy, reduces duplicated effort, and matches how your support operation actually works.
Sources
AWS What’s New: Amazon Connect Cases merge and link announcement
AWS Documentation: Merge cases in Amazon Connect Cases
AWS Documentation: Linked cases in Amazon Connect Cases
