La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
As many of you we also did encounter the problem of not being able to use the same email more than once. We used the workaround that has been mentioned in this community quite a bit.
By adding '+1', '+2', etc, before the @ in het email. Example:
So you if you are using the IBAN, you could use a trigger that IBAN is updated in an events trigger (You would need to manaully enroll everyone at first though with being an events trigger but it would allow you have the workflow allow re-enrollements). But the issue is setting which one would be the main contact and also having spot the 'similar' fields.
If you add the Koalify 3rd party app, you could use the IBAN field as the search field and then set the rules for which one you would like be the 'primary' and then use the koalify field to trigger off the workflow to set the associations.
We started with Hubspot just before I started here. So I don't know the exact reason why they choose to work with the '+1's'.
Fact of the matter is, we have it now haha.. and I need to find a way to work with it.
The association labels sound interesting. Does the associaton labels make it possible to crosscheck fields between multiple contacts?
My first reaction is to do this:
Through a workflow add the association label 'probably the same person' to contacts that have the same input in the property fields that should be unique (for example IBAN and another unique value), to link contacts with eachother.
When emailing a list of ex-participants: Check if contact in list does have the label 'probably the same person' and check if one of those contacts has the propertie status 'active' (custom field that we use), if so, remove from email list.
So that should work, belongs the fields are normally the same and are not a 'required' field on a form. For example, I do not give my own number on forms if I am not 100% sure on the company, I would add 07123456789, and I know a few people who do the same. So you would need 100% certainty that this would not happen, other you might send an email to wrong person.
You could also look at a 3rd party app, such as Koalify who provide a service to find duplicates. You could use their app to find the duplicates, but not the merging tool so that you could set rules to look for, such as same name and address. You can also set a rule as to who your primary would be such as 'First created' then you would have an duplicate ID number and also one set a 'primary' You could then use this to filter out in email lists.
Let me know if this sounds like something of interest and if you need more information.
So I had looked into this in past as well actually. So there are a number of older email providers that do not support this email address input and the recipent will not recieve the email.
Unfortunately, there is no way around the duplicate emails in HubSpot even via a custom coded workflow. It would either error or just overwrite what is there.
Could I ask what the need of the different users with the same email would be? I have found that one way around this could be using custom fields and association labels to ensure that people only recieve emails related to their role, relationship etc. And with the assocation labels you can add this via a workflow.
