Feb 2, 2020 2:19 PM - last edited on Mar 3, 2020 5:19 PM by lalexander
We operate in more than 10 countries and we all use the same HubSpot instance.
Feb 3, 2020 12:55 PM
As an option for the short term, you could always create a supression list for each team... So if the France team sends an email, and then use their supression list for that email or workflow that includes all contacts not in France... that is a way to ensure those contacts that arent getting included no matter what. Obviously its work for that team to remember to always use that, but for a complicated workflow or big send, it can always be used as an option.
Feb 3, 2020 2:08 PM
Hi there @khorne and thanks for your suggestion - This is a great point and for sure would decrease the probabilities of mistakes! However, I would still be worried about possible mistakes as you are mentioning!
Tnx a lot for your answer,
Feb 5, 2020 12:09 PM
Richard, thank you so much for this post! We hear you loud and clear. In fact, we are in the process of talking to customers with similar setup like you and understanding better your team structure and where partitioning may fall short today. Would you be interested in spending 30-45min chatting with us?
Regarding the contact partitioning, the way we've approached this so far is to have a team and partition the list by team. So if you are on team A and build a list, in it you will only see contacts that have been assigned to any of the sales reps in team A. That means team B won't be able to use that same list for an email. This is one way to help with the separation issue, but I'd love to have a more extensive discussion with you, if you are open to it.
Users & Teams
Feb 12, 2020 10:00 AM
@RiccardoPisani, we have a similar issue, but across brands instead of countries. Content property partitioning is a great feature we're making use of, however, as you have stated, this doesn't stop a contact from falling into a workflow or list by mistake! The idea of excluding lists from workflows may help with this - we use a lot of exclusions to minimise errors in workflow enrolment and email sends.
We have a bit of a more complex layer too, in that sometimes we want the contacts to receive completely separate messaging from the brands, but some of our contacts overlap across brands (use more than one of them), so this proves difficult to manage and a straight contact division wouldn't suit.
Would be great to have a greater degree of flexibility when deciding whether a contact, or their properties/activities, are visible to one or more teams, or can be enrolled in workflows/lists that are assigned/linked to each team.
Feb 12, 2020 10:24 AM
Hi there @SPhillips I totally see the point - I was thinkign that the best way would be partition contacts based on 2 or 3 properties and assign then teams based on that - e.g:
What do you think?