General Feature Requests

It would be great to be able to mark an Address/Email/Phone as Primary in Almabase. In RENXT - this is possible. If a user registers for the first time on the Almabase platform, and they provide three phone numbers (cell/home/office) - we do not know which of these three phone numbers is primary. We can make the assumption that the Cell is primary - but we don't know. This is an issue when importing the data to RENXT. It's also an issue with using the data. We do a lot of calling via "Phoneathon," and we will need to know which number users prefer. Finally, if we are using the Almabase platform, and see that a person has three phone numbers, it's not clear which is their primary. We would need to go back into RENXT and see the datapoint of "primary" there.

Constituent records should be able to be approved in multiples instead of individually. Also, all other aspects of the record (ie. address, email, and phone number) should be approved once the constituent record is approved instead of having to approved in a different tab.

It would be helpful to include the External Database ID in the gift exports, so we can merge the Blackbaud Merchant Services Transaction ID to transactions initiated through Almabase. The Transaction ID is included as a custom field on all transactions from Blackbaud Giving Forms, and having this information assists our accountants in credit card reconciliation. Currently, the process to reconcile online credit card transactions from Almabase is manual, which is especially difficult during Days of Giving when we receive hundreds of gifts.