Adding another reply to this idea as having the ability to have a workflow that removes contacts based on specific criteria would be incredibly useful for so many reasons. I understand the hesitance as automation for removing a contact can seem like a big step but trust your users to decide for themselves if this is something they want to implement, don’t hinder the system because you’re afraid that your users aren’t cogent enough to use the feature.
Use case Example - We are a Community Management (HOA) provider, our contracts (and therefore our only clients) are specifically the boards of these associations but we often have residents or homeowners who use our website to submit service requests via a specific form we have created. There is ABSOLUTELY no potential for them to ever be clients and legally we cannot keep their contact data without consent but they still need the ability to submit the forms. These forms go through a workflow already to send them to the appropriate department in our organization and to mark them as non-potential or inactive but I can’t use that same workflow to delete them? I have to put them all into a list and manually delete them all once a week and what if someone puts in two requests, instead of a whole new email being generated they become “reconversions” which is a narrow way to define multiple form submissions.
This is an underlying issue that I think greatly affects the HubSpot platform, in an effort to make the system foolproof you water it down for power-users who are used to more flexible environments and honestly is the biggest issue I have using HubSpot. While I appreciate the cosmetic updates I think a focus on some of these more user-requested changes would be really impactful.