I know it's seen as bad practice and I know why HubSpot doesn't currently allow it.
But really guys, sometimes we actually do need to delete an email address from a contact record.
I have historical contacts with important notes and history that have never had a valid email address in the email property. Or, someone in our organization entered a bad email address years ago and now it's permanently enshrined on the contact record, causing confusion and bounced marketing emails.
Perhaps when a HubSpot user attempts to clear an email address you can present us with a dire warning and then let the user make that decision themselves. Or, make it an advanced permission that only administrators can enable for themselves.
Either way, deleting the contact record or creating custom properties (as suggested here) are not viable solutions.
Hello HubSpot community! As @Apocalyps already noticed, this functionality is officially live in all HubSpot accounts as of a few days ago. I had been holding off on posting until we had ironed out some of the potentially misleading messaging that @BB1 noticed, but looks like you all beat me to the punch in noticing 😉
We'll be cleaning up that messaging this week, but, in the meantime the functionality is available for all to use. Thank you as always for your continued input here on the community forum. We're always listening and it helps us build a better product!
Hello HubSpot community,
I'm excited to let you all know that this is something we are planning to work on in the coming months. At this time I don't have a specific timeline for delivery but will update this post once we do.
Hello HubSpot Community,
Thank you as always for your continued feedback, it helps us build a great product.
We are constantly evaluating and re-evaluating our priorities and roadmap to deliver as much value to our customers as possible. The request to remove the last email address from a contact is an interesting one. Based on the comments and use cases you all have listed, we are reviewing this request and its feasibility among other priorities on our roadmap. At this time I don’t have any details around timing or delivery, but thanks to the comments and votes on this post we’re actively looking into what it would take to solve this problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.