• Replies 1 reply
  • Subscribers 204 subscribers
  • Views 106 views
  • Users 0 members are here
Related

v16 Membership Benefits and Performance Access

Gawain Lavers
$organization

I've read through the v16 Benefits documentation and just watched the TNEW Benefits webinar, but I wanted to try and confirm something (calling ).  In TNEW we use ranked MOS shifts very extensively, and it's complex, since we are juggling online benefits for members of our email promotions newsletter, subscribers for either of two seasons (current and upcoming) and up to five different membership levels.

These ranked MOS for donors to provide the following benefits:

Presales: donors are given first dibs on buying tickets to most events, sometimes by several weeks or even months for certain levels.

Access to premium parking locations: we use a combination of MOS shift and Entitlements for this.  Some donors have access to purchase, and higher levels have access to comps.  We use MOS to make purchase unavailable to people without the right donor level, and also hide the comp price type option for donors not high enough to access it, then control quantity with Entitlements.

Fees: at higher levels handling fees on orders are waived.

The documentation is quite vociferous about the fact that we should be transitioning away from MOS shifts to Benefits for member benefit fulfillment, and of course this would be a dream for us (we have 13 different modes of sale to cover various combinations of web benefits), but I'm not sure it's going to be that easy.  I only see one example in the cookbook that appears relevant:

Member-Only Events

https://www.tessituranetwork.com/Help_System_v160/Recipe-Books/Benefits/Events.htm

As I understand this, you basically have a performance with one price type on it, and the price type is controlled by "Enforce Limit".  Anyone can go to the page and select tickets at the special price type, but only Members will be able to complete the transaction.  Is this basically the Mode of Sale shift replacement?

My concerns are:

  • This seems like an awkward way to manage a limited presale: you'd potentially multiple special price types if you have multiple presales.  We have a long presale for high level donors and new season subscribers, a second for all other donors, and finally a brief presale for our "Email Club" members, which is currently just a mailing list (Interest/Constituency) but would presumably need a new membership organization and some complex tooling to apply, update and remove the membership.
  • It would work fine for our parking entitlement, but we'd have to add a lot more text to pages to explain who and why a customer might or might not be able to purchase, versus being able to take advantage of generic "not on sale" text.
  • I don't see that this can do anything with fees.

Am I correct that Enforce Limit is basically what is meant by a MOS shift replacement?

  • $organization

    Hey Gawain, I'm in the process of building our benefits for Memberships in V16  as we speak (we are going live end of May) and in testing (in application only so far, we are still waiting on our test TNEW for v16) the enforce limits are behaving as you would expect them to (within the application, again cant speak to TNEW yet). I have one set up for our Major exhibition where a member has their first visit free, then pay for subsequent visits. We have the frequency set to once per membership, and then l have it pointing to attendance category which allows you to set the limit of adults and children.  In terms of utilising this for presales, you would set up the price type with defined on sale and off sale dates and then build your benefit to point to that price type. I'll be able to speak to this more once we have TNEW up and running and can see how this behaves online, but so far in the client its working pretty well. Happy to answer any questions where I can.