It is very useful to maintain a quality contact base. Unfortunately, duplicates in your base cannot often be avoided. That is why SecuTix 360º has a batch for identifying potential duplicates. You will only have to check this potential contacts list to merge them and maintain a suitable contact base.

  1. In the “Organization” context, “Tools” module, verify that the duplicates detection batch is correctly scheduled on the ‘Batches programs’ menu.


     If there is no duplicate detection programming, it means that you haven’t used the duplicates detection batch yet. You will have to activate this batch on the "List of batches" screen of the "Tools" module, where you have to simply add a new batch of the "Batch of duplicates detection" type. Once you have saved the batch, you will find a programmation for the duplicates detection that you could plan at your convenience. It is not generally recommended planning this batch more than once every 24 hours.

  2.  When you run the batch, an algorithm will check the contacts of the base in order to identify the contacts that can probably be duplicated. These contacts identified as potential duplicates will change into orange on the contact search screen.

    Indicators taken account by the batch for the identification of duplicates

    (lightbulb) Contacts with a zip code

    Those contacts that have the following identical elements are considered to be duplicates:

      • The role of the contact.
      • The SOUNDEX evaluation (phonetization feature of ORACLE) of the names and surnames of the individual contacts.
      • The first 35 characters of the standardised address (street number + type of road + street name).
      • The zip code with capital letters.
      • The country.
      • The name of the structure if the contact is associated with a structure (this is an optional element for the definition of the identifier for the duplicate).


    (lightbulb) Contacts without a zip code but with a mail address

    Those contacts that have the following identical elements are considered to be duplicates:

      • The role of the contact.
      • The SOUNDEX evaluation (phonetization feature of ORACLE) of the names and surnames of the individual contacts.
      • The main mail address (“Mail 1” field).
      • The name of the structure if the contact is associated with a structure (this is an optional element for the definition of the identificatory for the duplicate).
  3. In the “Contact” module click “Duplicates control” to find the potential duplicates identified by the system.
  4. If you click on a line, you could choose the information that you wish to retrieve after the merge and merge these two contacts or tell the system that that is a false-positive (= false-positive).


  5. After the merge, the contact selected as "head of the duplicate" is the one that will remain active and every entity related to the duplicated contact (including its history) will be attached to the head of the duplicate.

Duplicates not detected by the batch

The batch might not identify some duplicates because the criterion for the detection does not store any data. However, you as a human can notice a duplicates pair. What can you do?

  1. First, enter the contact numbers of the contacts in question and click “Search” on the duplicates management interface. Then, the button “New” will appear.
  2. Click on the button and enter the contact number of the head of the duplicate (the one that you wish to keep).
  3. Do the same with the second contact.
  4. Merge your duplicates choosing which one you wish to keep.


You could detect the duplicates of the structure type in the same way. You can find more information on this website!