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
  • We have done this by having a non-public Web MOS as the only web MOS in the event. We then have source codes linked through offers, and provide a URL that deeplinks with the source code embedded in our electronic invite. It worked well for us for an event last month. We also had two types of people being invited, so we had different source codes based on who got the invite - and those people got different offers based on what we loaded into the MOS' offers. By putting it in offers you can also limit the number of reservations you get from each member.

    We wanted to make sure this event wasn't visible to the public because it was a donor only event, but if you want it to be public on your site, you can accomplish the same thing with a public facing MOS tied to source codes in offers. I would recommend that you put some text in your TNEW content build to instruct the patron to input their promo code to gain access. We usually utilize purchase instructions for that. 

Reply
  • We have done this by having a non-public Web MOS as the only web MOS in the event. We then have source codes linked through offers, and provide a URL that deeplinks with the source code embedded in our electronic invite. It worked well for us for an event last month. We also had two types of people being invited, so we had different source codes based on who got the invite - and those people got different offers based on what we loaded into the MOS' offers. By putting it in offers you can also limit the number of reservations you get from each member.

    We wanted to make sure this event wasn't visible to the public because it was a donor only event, but if you want it to be public on your site, you can accomplish the same thing with a public facing MOS tied to source codes in offers. I would recommend that you put some text in your TNEW content build to instruct the patron to input their promo code to gain access. We usually utilize purchase instructions for that. 

Children