Duplicate accounts are the bane of any CRM system and one of the most important aspects of maintaining data integrity. How you deal with this depends on where and how your accounts are added. Duplicate accounts will progress to confused reporting, login errors, and poor compliance and control.
Eventchain only allows 1 instance of an email address per Tennant(venue or team). It's still possible, however, to add contacts to different accounts that might be part of the same client. Coca-Cola is a good example where many account names appear overtime. We have seen many names used, for example;
Coke
Coca Cola
Coca Pty Ltd
Coca Cola Pty
Coke NSW
Coke Euro
Using text to consolidate accounts is not a recommended or a best practice approach.
Where you are using text names only, you may need to review your accounts - sorted by name - to remove the duplicates
In this case, it should be easier to control. Accounts can be linked by Account number or account ID.
It is far easier to control accounts using numbers or IDs over text names.
Load files or the manual addition of an account should synchronise your own system's account number. If your existing CRM has duplicate (numbers) they will be replicated in eventchain.
Data integrity issues create log-on issues which are often passed onto eventchain.
To help minimize the issues, eventchain will be adding an account "duplicate manager" for accounts (like seen in the contacts system of our VIP app) around mid-Q2 2024.
