How to model functional email addresses?

Is there a recommended way/best practice for modelling functional email addresses (e.g., sales@, info@, billing@, …)? By default HubSpot creates contacts for those (which is fine by me), but these email addresses don’t typically correspond to people and, therefore, don’t have a lifecycle stage and I would like to exclude them from how we treat other contacts.

We currently use the Persona property with an “Artificial Person” persona to filter those out, but I’m wondering whether there’s a “better” way to do this, maybe, where I don’t have to remember filtering these contacts everywhere? :thinking:

Hi @svamann,

Using a custom property to label these ‘contact’ records is the right way to go in my opinion. The naming and specifics are a matter of taste. I typically work with a contact type property and create a dropdown value ‘Shared inbox’ in that field. The result is the same: you can exclude or include these records based on the property value in reports, lists, workflows etc.

Additionally, you could set the lifecycle stage of these records to ‘Other’ to document that these live outside any buyer’s journey.

Best regards!