Allow Duplicate Contacts in Team Database
For larger teams, we run into a lot of cases where a member of the team adds someone to their contacts, only to see the contact already exists in the team database. Our current workaround is telling the second agent to add the contact to their personal database, but then they can not leverage the team's SmartPlans, create team opportunities, the contact is not visible to the team, etc. We would love to have our agents operate solely out of their team account, but this snag makes it nearly impossible.
It would be nice if you could toggle a setting in the team account to allow duplicates or not, maybe have it throw a flag if a duplicate is assigned to the same person. Even though Command treats the entirety of the team-owned database as one database where the phone & email fields must be unique, there should be logic built in on the backend to allow duplicates when the assignee field is different on these duplicated contacts.
Chandler Catron
shared this idea
-
Jen Pyatt
commented
Another reason this becomes problematic is because of how leads are received on paid ads through Command Campaigns. As agents in a group we can run ads on our personal side but the lead stays there because of the duplicate entries that we come across on the team side. Thank you in advance for considering a solution to this.
-
Kelly Bennett
commented
This is an ongoing issue on our team!! Hopefully a solution can be implemented