Re: Associated Primary Company Issue with Corporates Having Multiple Branches Globally

Hey all! Having an issue on similar lines with a client. They work in the tourism industry and will have many companies with the same domain, but often these companies operate differently and they do not want them to be associated automatically. (I appreciate this undermines a lot of the point of the CRM but it is what it is). An example of this are local councils in the UK. There are many departments of which all have the same domain (@eastsussexcountycouncil) for example. But within that, you could have a leisure centre, a library, a sports centre, all different buildings in different parts of the county, with the only thing connecting them being an email domain. Then whoever is last into the CRM overwrites the name and creates an issue.

The mechanism for bringing the companies into the CRM is all form-based, with Contact and Company Object Properties on the form. So even though the auto association is turned off, the fact both Contact and Company level properties are in the form will always create the association.

I have turned off the auto associate settings in the account and HS insights. It is not possible to add them all to the never associate list as they have too many, nor could they mitigate who would be coming in the future.

HS have suggested either using separate forms or create custom properties under contact to save Company information instead of using properties from the Company. Ideally I would like to find a different solution to these due to the vast number of forms and other potential issues that come off the back of this.

I hope that makes sense! :smiling_face_with_sunglasses:

Hi @JJeffery,
It sounds like you’re dealing with a complex scenario, but the current setup is causing issues due to automatic associations between contacts and companies.

1. Use custom fields (like department or location) to differentiate companies with the same domain.

2. Assign unique identifiers combining company names with specific attributes (e.g., location or department).

3. Adjust forms to map inputs to these custom fields, avoiding domain-based auto-association.

4. Set up workflows to review and correct associations before saving records.

5. Schedule periodic data audits to fix any incorrect associations.

These steps will help manage the CRM without relying solely on the domain for associations.

I hope it helps, let me know if you need to talk!

Khushboo Pokhriyal

Growth & Operations

GroRapid Labs

LinkedIn | 9315044754 | Email | Website