It is often an issue if two different contacts use the same browser, where their activity feed would be combined. To be able to check off which entries you are moving to a new contact, then create that new contact and have those chosen activity fields populate the contact properties would be AMAZING.
Right now this is a huge inconvenience and manual process to create the new contact, and their activity still shows up on the original contact's page. This messes up analytics.
Hi everyone! My name is Hallie, and I'm an Associate Program Manager on our CXM Team. I touched base with our product team regarding this feature request for unmerging records, and while they confirmed it's on their future roadmap, they do not yet have a timeline for this work. We understand the need for this feature, so thank you for your continued patience. As any more updates on timelines arise, we'll be sure to update this post to keep you informed! 🙂
Alternatively it would great if we could have a global setting so Hubspot simply made a new contact for each unique email address instead of trying to determine if two emails should be on the same contact.
Al menos el rol administrador debería poder retroceder la combinación de contactos.
El sistema de asociación de contactos desde la bandeja de entrada de conversaciones, desde que hemos integrado la API de Whatsapp, da lugar a errores de asociación/combinación con frecuencia.
Me acaban de confirmar desde soporte que, además, no existe opción de crear un informe, alerta ni lista de contactos con distintos teléfonos en distintas conversaciones, por lo que estos errores están sucediendo y pasan desapercibidos, con la posterior confusión que supone el tratamiento posterior del contacto.
It is dissapointing that this feature is not in place. Human error occurs and it creates ALOT of pain and issues when mass merge is completed. Identifying the records is hard and there is no way to fully recover the history and details. THis has been 4 years with over 200 votes and must be prioritised. Some in flight items have far less demand and are far less important.
Voting this up. This feature would be very beneficial as a safeguard. Our particular use case was in relation to the built in AI auto merge feature, where merges were occuring behind the scenes.
