Support composite duplicate matching (e.g., Full Name + Phone/Email) instead of relying only on Email or Phone
D
Dinesh Thakur
Currently, duplicate contact prevention relies primarily on matching a single unique identifier like Email or Phone. While this works well for standard cases, it creates friction in scenarios such as medical or dental clinics where multiple family members (e.g., parents and children or spouses) share the same phone number or email address.
When two patients share the same phone number, relying solely on phone matching can either block creating a valid second patient record or cause existing contact data to be overwritten/merged unintentionally.
Proposed Enhancement:
Allow configurable duplicate-matching rules/combinations (such as Full Name + Phone or Full Name + Email) in addition to Email or Phone alone.
Let users/admins choose 2–3 fields (e.g., Full Name, Phone, Email, or Date of Birth) to evaluate whether an incoming record is a true duplicate vs. a distinct person sharing contact info.
Provide clear handling options when a match is found (create new contact, update existing contact, or prompt/flag for review).
This would make contact deduplication much more accurate for multi-person households, clinics, and shared-contact businesses while still preventing actual duplicate entries.
Log In