Users of Referral Trak are supposed to ensure that before a new Referral is created for a new person or business (a Referred Party or RP) that the database is first checked to ensure that the RP does not already exist. This prevents duplicate instances of the same RP from entering the database which can cause a lot of confusion and make searches run slower and return duplicates. Its also not possible to measure referral activity per household or cross selling properly if your system has duplicate RPs.

Referral Trak customers that purchase integration will have duplicates when a new customer walks in off the street and is referred for one or more products or services. A customer is defined as new when there is NOT a CIF in the database for this customer yet. Thus the referrals are created BEFORE they can be linked to a CIF. Once the person becomes a CIF in the Core Processing System that CIF will be sent to referral trak which results in a duplicate.

In either case, the Merge Referred Parties Wizard helps by suggesting candidates for merging based on exact and loose matches on Last Name and Business Name. When you use this tool to merge the candidate into the suggested Referred Party (or CIF if integration is enabled) then all of the referred products and services are kept intact, and the duplicate personal or business information is simply logged and deleted.