Hello Hive mind,
I am hoping that one of you may have some insight or advise for me.
We have a program where we offer 6 tickets for $100 with the caveat that the patron must be 16-40 years of age. With that, they purchase the card and identify which performances they would like to attend. We assign best available seating the week of the performance and they pick up the tickets at will call the night of show. They must be the one to pick up the tickets and must show ID to verify DOB.
The program is set up with its own mode of sale, with the card being built as a production in order to collect the funds. Then once a performance is reserved we have a single price type which allows us to seat the reserved number of seats without any additional charge. The Card nor the PT is available in any other MOS, and I would like to keep it that way if at all possible.
We have been very successful with the program and it is starting to grow. In the past the only way a card could be purchased was over the phone, that way we could collect and verify the DOB. I am now being asked to make the program available online to sell, with the hopes that we can attract more people.
So my question are:
Would I need to create a MOS specifically for online sales of the card as I have for internal sales?
Is there a way to have an age verification indicator online through the purchase pathway?
Any insight would be greatly appreciated.
Hi Rhea!
I do something for our 18-29 discount. When they purchase the card or express interest in the discount, we have them show us their ID to verify they are in the correct age range. We then set up a constituency for that discount and create a price rule to make the change online. That way as long as they log in to their account, it should work.
Does that seem like it would work for you?
So the ballet has a customization for the school which validates if a child is eligible for a class either by an age (birthdate) validation or by an attribute validation (depending on the program). It is a custom concept that works with keywords and forms. You can even add a new student for classes validated by age (birthdate). This might be more time investigating and creating a custom plug in than you might want to invest but something to consider. I am happy to hop on a GoTo Meeting and show you what ours looks like.
Cheers,
Michaela
We doe something similar to what Michaela wrote. We have age requirements with a small 3 month grace period time which are all in keywords linked to the age attribute in their records. If camps are purchased online outside the age and the birthday not within the grace period to bring them of age they cannot add the camp to cart and there is a pop up that mentions the do not qualify for this camp. Similar to Michaela,it is a customization.
We do something similar to Jordan for our Young Professionals program (though no one truly verifies the birth date). Patrons may purchase a membership online either as a $10 per month perpetual pledge or a $120 per year contribution. It is managed via a Membership that adds a Constituency. I've then got a pricing rule that looks at the constituency and lets the member purchase their allotted two tickets to each show.
Happy to hop on a call if it would help!
Sara
Hi Rhea,
We have a separate TNEW instance for our 15-35 years old program (https://tsoundcheck.tso.ca/), where we have a pre-cart customization that asks for a birth date. That birth date gets added to the constituency record as an Attribute. and we have a stored procedure that checks for the Attribute dates and adds a constituency. Next time that patron logs in to buy tickets on TNEW, their constituency is recognized, so they don't have to enter a birth date again, and are able to proceed with the purchase.
Hi Jordan,
I think it is an interesting thought, but I'm not sure how it would work with our set up. We are currently using constituencies for those who are card holders. However, because we do not offer this product online, there are a majority of the cardholders that do not actually have an online account to flag.
Because it is a constituency, all you have to do, is make the pricing rule constituency based. You can also send them a temporary login if they request it, so that they can make those purchases online once they update the password. Let me know if you want to talk through this on phone or in person, and I'm happy to help.