Disable automatic contact creation for Conversations
HubSpot auto creates a contact for anyone that emails in - or is cc'd into a reply in conversations. For some customers who manage through support, this will mean a large number of contacts can enter the database. The only way to prevent this at the moment is by setting filtering rules, as all filtered emails do not create contacts. There is a use case from a customer in this post..
This is a request to build a "Create contact" rule giving us the option to disable automtically creating contacts for people we communicate with in Conversations.
Thank you all so much for this feedback and direction! I will be reviewing this with the team and will post an update. We have a few upcoming features that should address some of this pain so I will share in the next couple weeks as we have a more details. Thank you!
Hi everyone, my name is Cambria - I'm a Product Manager on the Conversations team. Thank you to everyone who has upvoted this discussion, shared your use cases, and added your thoughts and opinions over the past several months.
Before we dive into things, I just want to say that this feature was absolutely not designed to push any of our customers above their contact tier limit.
Contacts are the beating heart of HubSpot, and we want to empower teams using the Inbox to have remarkable 1:1 conversations, largely leveraging the power of contacts so they can have a 360 degree view of who they're talking to and previous interactions they might've had with their team.
That said, we know there's a few problems with our current system.
1) Contact tier limits - we know this is a problem and we're exploring solutions internally on how we can address this. 2) Filtering - we need to improve our system for filtering spam/undesirable emails so they never get to the point where they're being added as contacts anyway. We're planning on tackling later this year after some core email infrastructure work we're doing in the first half of the year.
I know this may not be the response you hoped for, but thank you again for all your feedback and patience with this issue. We'll keep this post updated when we have further announcements to share on progress here