A phone number is not a person, and a person is not a matter. A household may share contact details; one person may raise two different issues; one inquiry may arrive through several channels. If the CRM merges these situations indiscriminately, the firm can lose work, expose information, or misstate acquisition performance. Define the objects before automating duplicate decisions.
Keep Three Kinds Of Record Separate
A person record identifies an individual and approved contact details. A matter record describes a distinct potential or accepted legal issue under the firm's definitions. An inquiry event records a particular contact or supplier delivery. Connect these records when appropriate, but do not force every new event to create a new person or every familiar person to reuse an old matter.
Preserve source events even when staff identify a duplicate delivery. Those events may explain a callback, an invoice, or a later attribution question. A reporting view can exclude duplicate units without deleting the history. The firm needs to know what happened, not merely display a smaller count.
Use Matching To Suggest Review
Build matching rules around the risks of a wrong merge. An identical email address can be a useful signal, but shared or mistyped contact details still require care. A name alone is weak evidence. Decide which combinations can suggest a match and which require staff review before any information is combined.
Keep sensitive identifiers out of broad marketing tools simply to improve matching convenience. The firm's professional and privacy owners should determine what identification is needed and who may access it. A duplicate queue can use limited internal identifiers and a controlled review path rather than exposing full case details to every vendor.
Test The Cases That Break Simple Rules
Illustrative scenario: a parent and an adult child use the same phone number, but each has a separate inquiry. Merging on phone alone could combine two people's communications. In another scenario, one person contacts the firm about a workplace issue and later a credit-report problem. A person match does not establish that the matters are duplicates.
A third scenario involves the same person submitting the same issue twice through different suppliers. The firm may choose one active intake path while retaining both delivery events for contract review. These examples show why person identity, matter identity, and a billable duplicate need separate decisions.
Make A Merge Reversible And Accountable
Before a merge, show the reviewer the limited evidence needed to compare records, the fields that differ, and the affected assignments. Preserve an audit entry with the reason and original identifiers. Where the system supports it, verify that an incorrect merge can be undone without losing messages or documents.
Protect communication preferences during reconciliation. An old record's contact setting should not automatically overwrite a newer, explicit instruction without review. Check open tasks and owners after the merge so two staff members do not continue parallel follow-up or, conversely, both assume the other is responsible.
Report Counts At The Right Level
Show delivered events, distinct potential matters, and distinct people as separate measures. Use the purchased unit for supplier billing reconciliation and the firm's matter definition for acquisition outcomes. Explain exclusions and revisions when a duplicate is identified after a report was issued.
Audit a small sample of both merged and unmerged records periodically, especially after adding a new supplier or practice category. The useful target is fewer incorrect decisions and clearer ownership, not the largest possible reduction in record count. A record that remains separate with a documented relationship can be safer and more informative than a confident but mistaken merge.
Common Questions
Should Duplicate Inquiries Be Deleted?
Usually the firm needs an appropriate record of the original delivery and the disposition, even if the active workflow is consolidated. Apply the firm’s retention and access decisions. Removing a duplicate from a metric does not require erasing the event that explains a charge or prior communication.