Pallavi Kothari the DND should take the setting based on the most recent version of the contact. And ignore dnd that was set automatically based on the one of the contacts numbers not being a mobile number. And if the DND is too close to tell based on the different variations of the contact, set to DnD and then create a task for the staff to manually asses.

Pallavi Kothari, manual select for each available contact method.

Please and thank you.

It would be hugely beneficial if the "Purchase Activity" could be merged for all of the duplicate contacts as well. This a pain point we about hear from our users.

I think there should be a Merge action as part of a workflow, and this would allow for all kinds of customizability based on various criteria. Email, phone, custom fields, AND/OR logic, etc. Right now, I am trying to manually solve for the issue of 5 different contacts created because of different systems being used and an improper handling of contacts. Many people have multiple emails and phone numbers, and the auto 'prevent duplicates' function in the settings is not a viable solution: it will either prevent information from being written altogether, or it will overwrite information that should have been added instead.

Merge function on contact level to search who we want to merge with.

Could we get a merge option on the individual contact page to select who we want to merge with? Would be amazing!

Update on Merge modal. Pallavi Kothari

Use Case:

Contact register with personal email and book a call with business email.

Solution

In merge modal, we should be able to select to keep both email and just select which one is the default. So in the future we can avoid to duplicate that contact again.

Question.

If a contact has a default email and an additional, a new contact comes in from a form or CSV upload, then will the system check for additional email match as well before creating a new contact?

Pallavi Kothari The only correct way to handle mixed DNS statuses is to set the non-DND email as the default email for the contact (regardless of master record), then have the option to manually turn on DND.

It's too often that clients will DND their work email but not their personal or vice versa based on where they prefer to recieve our emails. Only if they've DND'd both emails should the contact be set to DND by default.

Actually i think the lowest level of DND would be preferred, ie: if one contact is dnd and the other is not then make the contact not DND. only for DND when both are DND should it actually be DND.

Automatically merge and set DND if either record has DND... then provide a list where we can check manually.

Manually checking records isnt feasible with even a few thousand records...

Err on the side of caution and report which records were set to DND after the merge.

thanks Batch

In my experience with merging contacts in general, and any fields in the contact profile, I prefer it to be a manual choice... The software we used previously had an option to check for duplicate contacts - once the list came up with who they thought could be a duplicate, I was given the option to merge (and which info from each profile I wanted to keep in the new merged profile) and which duplicate suggestions to reject.

While manual can be tedious, we have a lot of customers with multiple accounts that depend on separate contact profiles that don't always follow the rules of logic that would most likely be used for auto-merging of contacts.