Reasons we need to filter by Registrations more than we are currently able:

1. To analyze member activity and who's pulling their share of our load, we want to know (for example) what Members have attended more than one registration event in the past three years, and which events they are. Currently we can only filter for the number of registration events, then have to look at each one to determine when and what. People who registered for events 5 years ago are irrelevant, and people who are registered for our annual dinner are also irrelevant. We need to know who has recently registered for our more routine events.

2. In culling our list so as not to go over our limit, we need to do a similar search. Except this time we need to know who has NOT attended a registration event recently, including how often and which events. A non-member who was active 5 years ago but not recently is a candidate for Archives. But to determine this, we'd have to place checks in hundreds of events, and even if we laboriously do that -- it's not repeatable. Change the search, and you have to do that chore all over again. So we don't.

I get a direct increase in the number of attendees (my objective for each of my weekly events) when I can send a specific announcement email for that event. My members are regulars and don't want to and don't have to have to register for the events they want to come to, it wastes their time. The events are specific that week and don't follow a sequence but because of the way you have things set up, to be able to send an announcement ahead of time, for each event that week, I have to input 13 events a week or 52 a month (see attached) and then set up an announcement for each one.

Setting them up as four sessions for the month (using the session function) rather than as individual events, saves me a huge amount of input time each month. To me if you have coding in place now to send a reminder email ahead of each session to any member who registers for the event as a whole, why not simply code that option for announcement emails so every member who could attend that event/session (their membership level allows) gets that same reminder email for each session, regardless of whether they register or not. At the moment assuming your clients and your clients members are using the system a certain way.

Many thanks

Ali

We have a bunch of different membership levels, and we occasionally have to change members from one level to another. Why on earth would someone in WA design think it was a good idea to automatically change the renewal due date if this happens?

I'm flattered to think the designers believed us users are so perfect that we could never enter the wrong level by mistake and then have to change it after the fact, but that happens. And when we make the correction, a year is added from current date.

We also have members who were in bundles until the administrator decides to have them removed; if we want to keep in touch with these people, we have to change their membership level to individual, and hey presto, they are automatically extended for a year from current date even though they aren't renewing. This is especially vexing if the membership is being renewed after lapsing.

Fix this, please!

There needs to be a way for users to find out their username if they forget it.

A simple "Search by last name name, first name, and zip" and, if it returns 1 and only 1 result, notify them of their contact email, set the password to a temporary password, and email them a link to reset their password.

We have people who are re-joining on accident because they cannot remember their login information.

This widget should not assume that the member is active. In many cases, it is the lapsed members who need to urgently recover their username.

We are getting around this by asking the members to email an administrator who can look them up manually.