It would be nice if to create an internal marketing email subscription for internal communication that doesn't let contacts unsubscribe from that email subscription.
"Hi all I am the product manager on the subscriptions team at HubSpot, I certainly see where this will be useful as folks run all their communications on HubSpot (external and internal) and the need to keep those completely separate. Right now we do not have a space for this in our roadmap, however I will keep this one on our radar."
As far as workarounds go, all of them come at an additional cost (business units or transactional email for example).
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
"Hi all I am the product manager on the subscriptions team at HubSpot, I certainly see where this will be useful as folks run all their communications on HubSpot (external and internal) and the need to keep those completely separate. Right now we do not have a space for this in our roadmap, however I will keep this one on our radar."
As far as workarounds go, all of them come at an additional cost (business units or transactional email for example).
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Would love to know if Hubspot has made any updates on this front since this chat. Also, if a company was to use Hubspot for internal communications, I was wondering if there is a 'best practices' list. What would be the important considerations? Here are a few issues/questions that I can think of right off the bat:
Obviously, internal commmunications requires importing all employees. Is there a subscription type that allows contacts that recieve communications that don't need to be payed for like regular marketing contacts?
How to ensure that there is a clear distinction in the CRM between employee contacts and marketring contacts (are there custom or existing contact properties that should be used?)
email analytics must be seperated from marketing performance.
It looks like this feature request is still currently not planned by the Product Team. I would recommend following feature request so you can get any updates made it by the product team.
In regards to your best practices questions, would you mind adding them to a new post, please? Creating a new post will ensure it gets visibility among all of the community members who can brainstorm ideas with you and offer insight.