Request for Advanced Constituent Matching Features for Online Gifts

We've encountered challenges with duplicate constituent records created from online gifts in RE NXT. The process seems to lack a direct way to influence constituent matching based on unique identifiers, such as email addresses, which leads to an increased administrative burden to manually identify and merge these duplicates. This is also an annoyance to affected donors, as they are not being credited for pledge payments made through BBMS because their pledge is on one record while their payments are being recorded on another (dupe) record.


Suggestions:

  • Introduce advanced constituent matching features within RE NXT for online gifts that allow organizations to set rules or preferences based on available data points (like email addresses, spouse name, etc).

  • Enhance duplicate detection and management tools to more efficiently identify potential duplicates before they are created, and provide more intuitive options for merging.


Improving this aspect of RE NXT could significantly reduce administrative overhead and enhance data integrity for all users.

Thank you for considering this improvement.


  • Suzanne Hopkins
  • Apr 11 2024
  • Reviewed: Voting Open
  • Attach files
      Drop here to upload
    • Nicki Downer commented
      09 Jan 20:56

      There's also an issue when someone makes a donation on behalf of a company (which is an option you can tick on the online forms). I just had one come through where I had to upgrade an administrative assistant to a constituent because she wasn't showing up in the "relationships" search for the company I had just matched! If I matched the gift to the company, I shouldn't also have to create a new constituent record for that company's admin. We use non-constituent relationships for this!

    • Kyle Reierson commented
      June 17, 2024 21:13

      Similarly, I have noticed many duplicates are created based on popular nicknames/short names. It would be great if RE could search for these common alternatives. As mentioned by OP, this would greatly reduce administrative overhead and enhance data integrity for all users.