Hi all,
I am doing some testing before implementing Allocations and Rankings but I am struggling to figure out a few things.....
1. In rankings under the research tab of a constituent, the Rank Description refers to those set up in TR_RANK_TYPE. However you can only apply one Rank Type per performance. I'm confused as to how you can have several different rankings per performance/per person when you can only link one of them.
E.g. I have created one called 'Ticketing' and another called 'Development'. However under ticketing there would be several categories (student rush online, staff comps, subscribers etc). Do I have totally the wrong idea here? Should this be set up differently?
2. How does the numerical value of the rank in the constituent account link to the rankings you apply when in season manager? Eg: The rank type is 'Ticketing' but then the allocation maps have the same category names as above (staff comps, etc). when I place a value against these in Season manager, I can’t see how they are linked. How do I say who belongs in what category?
I think I must be missing some fundamental pieces of information here! Any help would be so great!
Tash
Hi Natasha,
I think you are blending allocation codes and rank types a bit, and that could be part of the confusion.
Rank types allow you do assign different rank values to the same constituent. For example, you could have a Seating rank type and a Development rank type. The rank values you give to a constituent would be different for each rank type. The Seating rank type would be used with allocations. The Development rank type would not be used with ticketing, it would be used by the development staff for building lists for their solicitations.
Now that you have two different rank values on a constituent, Tessitura needs to know which one to reference when evaluating whether or not a constituent has a high enough rank value to access an allocation code. And that’s why you select a rank type on performances.
The different categories you refer to in your examples (student rush online, staff comps, subscribers) would correspond to different allocation codes. When you apply those codes to performance you would set a minimum rank value that constituent must have to access a seat with the code. For example, you would set the rank value on the Subscribers allocation code to 100, the rank type on a performance to Seating, and then a constituent must have a Seating rank value of 100 or more in order to access the Subscriber allocation code. Does that make sense?
Based on your allocation code examples, I’m not sure that the rank portion of allocations is going to allow you to accomplish your goal. Because the rank value you set on an allocation code is a minimum, the highest ranked constituent would have access to all the lower ranked codes. For example, if subscribers had the highest rank value, they would also have access to staff comp and student rush seats. Mode of sale is probably going to be the way to accomplish your goal. You would create special modes of sale for student rush, staff comps, and subscribers and then set shifts into those modes of sale on the web based on either the entry of a source code or rank value. Then you would associate the different allocation codes with their corresponding special modes of sale, so that the only way you can access those seats is if you are in the special mode of sale.
If you haven’t read it already, see the Allocations document for details on how all of this works.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Hi Kevin,
Thanks for such a detailed response, that all makes perfect sense! I did read through all the documentation but I had clearly missed a few things.
Thanks again,
Natasha