Everyone loves shiny new features (us, too!). But exciting and novel functionalities work best in tandem with regular maintenance and updates of already-existing features.
The Monthly Product Roundup is your chance to take a closer look at what’s happening behind the scenes at Rhythm. While we’re still building new functionalities, we’re constantly improving and optimizing our existing capabilities based on feedback from customers.
Your experience matters. Keep reading to see what kinds of product enhancements we added in May.
Now, you can prevent portal users from adding new organizations to your database in a contact form. Your team can control the creation of organizations in the console, proactively maintaining your database quality.
When this option is turned off, contacts can still create new organization records in the portal, but they can only link themselves to existing organizations.
We’ve introduced a new membership concept called Lapse Date. This is the date that the membership last lapsed. This is different from the Termination Date in that it doesn’t get erased when a constituent reinstates their membership. This feature is especially helpful for determining whether a constituent has maintained a continuous membership or not.
Let Rhythm do the recordkeeping for you with easy-to-access audit logs and database relationships on all system configurations. Using 360 screens, you can view the history of a configuration, what changes have been made, and by whom.
Use database relationships to view a list of all records associated with a contact including financial transactions, membership applications, and event registrations.
Now, you can use an individual’s organization membership in advanced rules and logic throughout the system.
For associations that have organization memberships, you have the ability to add rules for pricing, purchase eligibility, and security policies based on the membership standing of a contact’s organization.
Let your scheduled queries run on autopilot now that Rhythm’s Query Engine allows the use of relative dates instead of specific dates. For example, you can run a query for memberships expiring “this month,” instead of going in and manually changing them. It only needs to be set up one time, and the system will automatically substitute the dates based on the execution time of the query.
Relative dates are essential for queries that rely on pulling data over a period of time, as opposed to pulling data based on specific dates.
Let’s say you’ve got an offer for 10% off the price of an annual conference for anyone who registers in the month of June. You may have a few June registrants who didn’t know about the offer or take advantage of it.
Instead of having them cancel their registration and re-register, or offering some other kind of “equal” credit, it’s now possible to retroactively apply coupons to past orders in both the console & portal.
Reduce staff hassle, improve the member experience, and enhance your database tracking quality all in one swoop.