The new ticket system appears to have eliminated THE feature we need to run events. We’re a museum. Let’s say we’re hosting an event with 40 max registrants. In the previous system, we could set any number of registration levels and not set a limit for each registration level. We could have a mix of 30 members and 10 nonmembers, or any other combination of levels. When the total number of registrations hit 40, the registration would be shut down. Now – I learned from talking with a customer service rep – we can’t do that. We have to set a total number for each registration level. We could set each registration level to the max, or set each level to unlimited, but then we have no control over when to shut off registration based on the total number of registrations sold. That doesn’t work for us. It used to work so well. I understand the interest in having a traditional ticket system for an auditorium or theater where there are only so many front row or balcony seats available. Why eliminate the flexibility to do anything other than that? It’s hard to believe we’re the only ones impacted by this. The customer service rep let me know that CC is getting a lot of calls from customers who want old features back, and that changes might be made. The question is when – and can we afford to wait an unknown amount of time to get back the feature we need. Or do we find another vendor and go through the hassle of migrating data somewhere else? Maybe this isn't the right place to ask, or maybe I'm just venting. I’d rather stay with CC, but this is a real problem that I’d like to talk about with someone who can give me an answer.
... View more
