Hello!
I am with a historic site that is moving to timed ticket entry for mansion tours, which is GREAT! However, the shift is raising several logistical questions about how we will continue serving our members, donors, and constituents who are more than a traditional guest.
Our members can visit as many times as they like within the membership level they have. Example: Our "Dual" membership includes 2 adults and at any time the 2 adults can tour the mansion, and they can purchase discounted tickets for additional family/friends (with a limit on how many they can purchase in a year). Because we have not used timed tickets, all membership ticket transactions occur onsite at the ticket office rather than having members purchase tickets in advance online. We have soft-opened the site using timed tickets, and are now running into issues of members not being able to tour the site because we are sold out and they could not reserve tickets online in advance.
The first shift for us will be implementing membership availability online for advanced ticket purchase. Does anyone know if we can cap the number of tickets a member can reserve at their comp rate based on their membership level by transaction? We utilize pricing rules for members to purchase discounted special event/program tickets online based on constituency, but can we go further with membership level?
The second shift is giving them the capability to purchase discounted tickets online associated with their membership level. Does anyone know how we may accomplish this?
Lastly, does anyone have policies in place for members who purchase their membership onsite, but the tours are sold out? Do you have a separate entry line to try and accommodate them?
Apologies for the lengthy post, and am grateful for any insight you are able to share. We use TNEW for our online sales component.
Thank you!Ashley
Hi Ashley,
We've been using the Entitlements add-on for situations where we want to limit the number of comp/discounted tickets members can get online. Setup's a little complex but it works great. It's essentially the precursor for the v16 benefits functionality Nathanael mentioned. It's not free, but it might be worth it if you're in a pinch.
If you've got a SQL developer in house, you could also roll your own by customizing lwp_validate_precart. I've had success with introducing ticket limits this way in cases where Entitlements weren't quite what we needed.
We're still on 15.0.4 (soon to be 15.1.11). What functionality were you referring to?
My apologies, it was actually Anne who'd referred to the benefits functionality upcoming in v16.