Chat and phone contacts can describe the same unresolved issue. Link them through an explicit matching process so staff keep one coherent case without accidentally merging distinct customer problems.
Duplicate tickets are a business relationship
Cross-channel ticket deduplication determines whether interactions belong to one issue. Shared contact details or similar wording can help, but neither proves identity or issue equivalence on its own.
For a proposed model, keep interaction records separate from the canonical ticket. Record customer verification context, affected resource, issue category, relevant timing, and matching evidence. Preserve uncertain matches for authorised review.
Do not discard the newer interaction after linking. It may contain a correction, additional impact, or a changed contact preference. The ticket should retain source references and current actionable facts.
Test a fictional repeated outage report
A customer opens chat about a login failure, then phones when no response arrives. Both contacts concern the same account and unresolved incident. The system can link the call to the existing ticket rather than create another team assignment.
Another call from the same number concerns a separate billing dispute. A broad “same phone within a day” rule would merge unrelated work. The fixture should prove that the distinct issue remains separate.
| Matching case | Expected result |
|---|---|
| Same verified customer and same unresolved issue | Link through the approved rule |
| Same customer, different problem | Separate ticket or explicit related-case structure |
| Shared telephone number | No identity assumption |
| Caller supplies ticket reference | Verify permitted relationship |
| Ambiguous similarity | Review without destructive merge |
Inspect assignments, notifications, and source history after linking. A merge that prevents duplicate records but loses the caller’s updated urgency is still defective.
Keep concurrency in the design
Chat and phone intake can create tickets simultaneously. Use a supported atomic or reconciliation strategy for the intended uniqueness boundary. Event-ID deduplication within each channel cannot solve a cross-channel issue relationship by itself.
Strict deduplication can undercount legitimate issues; permissive creation can split ownership and duplicate replies. Track false merges, duplicate cases, and staff correction effort. Prefer reversible linking when the evidence is uncertain rather than destructive automatic deletion.
This ticket design is proposed. The voice integration case study describes related support and telephony work without claiming this deduplication system. Pair it with cross-provider event identities.
Cross-channel ticket FAQ
Can a phone number uniquely identify the issue?
No. Numbers can be shared, changed, or reused across several requests.
Should linking delete the original contact?
Preserve the relevant interaction history and evidence under the approved data policy.
What should happen when two tickets already exist?
Use the authorised merge or relationship process, preserving ownership, current facts, and an auditable disposition.