Handling general corporate emails

Hi everyone,

Our company operates in the B2B sector and has only recently started using HubSpot, so some things are still a bit unclear to us. I would be very grateful if someone from the community could help me out :slightly_smiling_face:

We are currently building our HubSpot CRM with a company-centric approach, and we are facing an issue with generic corporate email addresses such as:

Our Setup:

  • Companies are our primary object
  • Contacts must always be associated with a company
  • Automatic company creation in HubSpot is disabled to avoid duplicates
  • Companies are managed manually or via import
  • Contacts are linked under their respective companies

Additionally, we have a workflow:

  • Trigger: new contact is created
  • After a 2-minute delay:
    • if no company is associated → create an internal task
    • if a company exists → workflow ends

The delay is necessary because HubSpot sometimes processes the company association internally just after the contact is created.

This works well in principle.

Problem:
When someone from our team sends an email to a generic corporate address (e.g., info@firma.de), HubSpot automatically creates a new contact. Since automatic company creation is disabled, this contact initially has no company associated with it. As a result, our workflow is triggered and creates unnecessary tasks.

However, from a business perspective, we want to keep these generic addresses because they are important in a B2B context:

  • Initial contact
  • General communication
  • Quote requests
  • Sending information

Our ideal scenario would therefore be:

  • Generic corporate emails should remain as contacts
  • They should be automatically associated with the existing company
  • The “contact without company” workflow should NOT trigger for these cases
  • Automatic company creation should remain disabled

We are currently considering:

  • A contact property like “Generic Corporate Address”
  • A workflow to detect info@ / kontakt@ / office@
  • Automatic company association based on the email domain
  • But no automatic company creation

My questions:

  1. Is this the cleanest approach from your perspective, or do you have better ideas?
  2. How do you handle generic corporate emails in a company-centric B2B setup?
  3. Do you use automatic company association despite having automatic company creation disabled?
  4. Are there best practices for cleanly separating generic corporate emails from actual contacts?

Thank you in advance for your help. I look forward to any responses!

Hi @danhighmountain,


@danhighmountain wrote:

Additionally, we have a workflow:

  • Trigger: new contact is created
  • After a 2-minute delay:
    • if no company is assigned → create internal task
    • if company exists → workflow ends

You can simply add the “Create association” action here, before the delay. The association can be based on matching property field values (between contact and company), using the email domain on the contact and the company domain on the company. Then, the association will occur, if the company exists, before the check, and a task will only be created if the association is not successful.

Best regards

Vielen Dank, mit deiner vorgeschlagenen Anpassung funktioniert der Workflow jetz wie gewollt.
Liebe GrĂĽĂźe