I also want to have this feature reinstated. (BTW, If i'm voting for this as requested above, am I voting to reinstate the feature of the OP, or to approve the moderator's solutions/choices? Because I do not want the latter.) Regarding more than one email address per contact, consider this: You are a customer receiving a newsletter. You are receiving it at your home and work emails by choice. CC provides the ability for the customer to update their own contact record and you have in the past had multiple emails in your record. Up until this change, you would be able to see both of your email addresses in your contact profile. Now what happens, you have to manage two profiles? This just doesn't make sense. What if you had an old old email address you're finally getting rid of but now want to receive mail at two new addresses? Would the customer have to create a new record for the extra email address? That's a good way to piss off a customer. Then, from our point of view, wouldn't only one record keep the engagement history and then the other new address would have to have a totally fresh/no engagement history record? That makes no sense and kinda defeats the purpose of being able to analyze data. It also makes it more difficult for US to manage our contacts efficiently. If you're looking to help US better manage our customers' emails, perhaps provide a detailed import guide that includes instructions on how CC matches data so that we can help avoid accidently making duplicate records when importing. (for example, which field is used to match records? I've heard two different answers to this: email address, and more recently first name/last name.) Or, why not work on developing a tool we can use to easily identify duplicate emails in unique contacts across a select number of lists (or all lists) which then offers options on how to reconcile/fix/ignore the issue.
... View more
