How to arrange for members-only performances, or spots in performances?

Hello!

How would we go about setting up performances that are member-only through TNEW? 

We're looking into having member-only events sold through Tessitura. On-site, it wouldn't be an issue, as we could look up the members, and weed out non-potentials. Through the website, however, is it possible to have an event not be available without being a member?

The closest I can come to an answer at this point is to look into creating a MOS that is non-General Public, but it is possible for folks to be a constituent, but not a member.

Has anyone done work on this?

We could half-way do it with performances that aren't linked through our website at all, and instead require explicit linking through TNEW, but that is only a partial solution.

Parents
  • Look into using Rankings. With Rankings, you can make the performance show up on TNEW for only those logged in with specific constituentcies. You create a Rank Type in TR_RANK_TYPE, add that Rank Type to your performance (in the General tab on the performance - Type: section) and a separate MOS for members (if you don't already have one). You assign the Rankings in TR_WEB_RANKING. Have your CRM add the ranking(s) to your member constituent records.

    As always, do this all in TEST first, once you confirm that it works, do it in LIVE.

    We use Rankings for online Member Only events as well as access to special member only pricing.

    We also have used it with the Gift Shop (a separate company) so that they can redeem our Gift Certificates (they use the gift certificate(s) to purchase Zoo Bucks to make the purchase in their store - the Zoo Bucks are good throughout the Zoo and can be used at the Gift Shop, Food Vendors, and IMAX). We created a Zoo Buck performance for selling our Zoo Bucks that has a Vendor Zoo Buck Price Type and an Online Vendor Login MOS associated with it. The Gift Shop logs into our website, click on Admissions and they see a Zoo Buck performance (instead of our regular Admission performance). They then add Zoo Bucks to their cart and use the guest's Tessitura Gift Certificate to pay for the Zoo Bucks. They pretend that they actually have the Zoo Bucks in-hand to pay for the purchase and finish the transaction in their system using the Zoo Bucks as a Payment Method (or whatever it is called in their system). The Gift Shop has a record in our database, with a Vendor Login consituentcy, Vendor Ranking, 4 TNEW logins (so that they could have up to 4 of their staff logged in at the same time - they told us the 4 emails they wanted, we added it to their record and created logins). We set-up a nightly scheduled report that gets emailed to their managers and our Finance department; as well as a monthly report. They settle up monthly. Another reason for more then 1 login for the Vendor is that TNEW will make them wait up to 10 minutes before they make an identical or like purchase within 10 minutes (to help avoid a duplicate purchase by mistake). If they were to make a Zoo Buck purchase on TNEW, and then attempt to do another within 10 minutes - with the same web login - the site will not allow them, indicating that they should wait 10 minutes. The Gift Shop simply uses one of the other logins that they have to redeem the gift certificate for Zoo Bucks (they made their logins consecutively numbered i.e. gift.shop1@gmail.com, gift.shop2@gmail.com, etc..).

Reply
  • Look into using Rankings. With Rankings, you can make the performance show up on TNEW for only those logged in with specific constituentcies. You create a Rank Type in TR_RANK_TYPE, add that Rank Type to your performance (in the General tab on the performance - Type: section) and a separate MOS for members (if you don't already have one). You assign the Rankings in TR_WEB_RANKING. Have your CRM add the ranking(s) to your member constituent records.

    As always, do this all in TEST first, once you confirm that it works, do it in LIVE.

    We use Rankings for online Member Only events as well as access to special member only pricing.

    We also have used it with the Gift Shop (a separate company) so that they can redeem our Gift Certificates (they use the gift certificate(s) to purchase Zoo Bucks to make the purchase in their store - the Zoo Bucks are good throughout the Zoo and can be used at the Gift Shop, Food Vendors, and IMAX). We created a Zoo Buck performance for selling our Zoo Bucks that has a Vendor Zoo Buck Price Type and an Online Vendor Login MOS associated with it. The Gift Shop logs into our website, click on Admissions and they see a Zoo Buck performance (instead of our regular Admission performance). They then add Zoo Bucks to their cart and use the guest's Tessitura Gift Certificate to pay for the Zoo Bucks. They pretend that they actually have the Zoo Bucks in-hand to pay for the purchase and finish the transaction in their system using the Zoo Bucks as a Payment Method (or whatever it is called in their system). The Gift Shop has a record in our database, with a Vendor Login consituentcy, Vendor Ranking, 4 TNEW logins (so that they could have up to 4 of their staff logged in at the same time - they told us the 4 emails they wanted, we added it to their record and created logins). We set-up a nightly scheduled report that gets emailed to their managers and our Finance department; as well as a monthly report. They settle up monthly. Another reason for more then 1 login for the Vendor is that TNEW will make them wait up to 10 minutes before they make an identical or like purchase within 10 minutes (to help avoid a duplicate purchase by mistake). If they were to make a Zoo Buck purchase on TNEW, and then attempt to do another within 10 minutes - with the same web login - the site will not allow them, indicating that they should wait 10 minutes. The Gift Shop simply uses one of the other logins that they have to redeem the gift certificate for Zoo Bucks (they made their logins consecutively numbered i.e. gift.shop1@gmail.com, gift.shop2@gmail.com, etc..).

Children