Should be able to link dupes by Household!
J
John Taggart
If a fella submits a lead to my CRM and his wife submits a separate lead with the same phone number, same shared email address, same address, same last name, but different first name, we should be able to join those leads together without fully merging them!
A merge removes either the husband or wife's name while leaving them separate leaves out valuable information about the customer you are speaking to or attempting to call!
It's a no-brainer!
Shelby Parker
Thank you for posting, John Taggart! I have a few more questions for you:
- How should the system handle cases where there are multiple shared attributes but some differences, like different phone numbers?
- Would you like the option to manually review and confirm potential household links before they are finalized?
- Are there any specific attributes or criteria that should be prioritized when identifying potential household links?
J
John Taggart
Shelby Parker I think it could be handled in the dupe merging screen and that it would key off of similar attributes. Prioritizing addresses, phone numbers, then email address in that order. There could also be a "last name" key that the system could pick-up on that would suggest a "household merge" rather than the merge we have now.
There could also be a separate box under the customer card (where things like Details, Garage, and Customer Notes live) that keeps track of households and allows properly permissioned users to manually merge households for instances that do not trigger the suggestion.