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,
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.