Credit card processors charge more for transactions without CVV.

We have at least one event every year that contains a slate of child events, some of which overlap or occur at the exact same time. At present, the onus is on the user to ensure that he or she doesn't register for events that conflict with each ot...

Some events are made for Team participation. We would like to be able to restrict registration to joining or forming a team, without using custom code to hide the "Register as an individual" options.

Gifts/Registrations are processed in Gift/Registration Date order, and this would present a sequential list by "pure" date. Gifts/Registrations within this sort order would be in Date/Pending order.

Currently when RELO finds a match (that is really not a match to an existing record), when you Create New and Process, it only creates the new constituent, but does not open the record for editing as it does for non-matched Create New and Process ...

Improves efficiency of the gift/registration processing personnel.

Would love to see the features of this product (emails based on interactions and if/then areas in an email) for admissions. This would be wonderful!

Change the interface from LO to BBMS to include the LO User Confirmation Code in every transaction on BBMS reports in the comments. Currently, on the BBMS reports, recurring payments indicate "payment X of X" in the comments, which is not helpful ...

sometimes a single campaign becomes too big to easily find the right document and if there are emails that are similar, it would be easy to give them subgroups to avoid accidental confusion (ie create a folder for major donors, a folder for member...

Thermometers should have numbers, not percentages.