Tracking Seat Naming Opportunities via Future Performance?

Hi Grayson

I have seen this managed using out-of-the-box functionality. It would depend upon your business needs, of course, as to whether or not this will work for you

1. A performance is setup to represent your Seat Naming program - it would have the appropriate Season and other details assigned. Use blackout Hold Codes for any seats that would not be offered up for Naming 
2. When the seat has been 'named' it is sold in a Ticket Order as a complimentary - no need to print any tickets of course. 
3. Processing the contribution component through Contribution Entry or Ticket Orders
4. To capture the name of the Seat - there are 2 ways, adding a Program Name with a type called Seat Naming (contribution processed in Ticket Orders) , OR add simple custom field to Contribution Entry to capture the information (using the system table T_KEYWORD) - there's details in Tessitura's Help docs on how to do that (contribution processed in Contribution Entry)

To report, you can visually see the seats that have been Named and those available on the seat map for the 'performance'. The Performance Seating Book outputs the constituents who have named seats and their seats. If you used Program Names to store the recognition name for the Named Seat (as it could be different to the Constituent name), you would use the Program Listing report to output the name. If you used Contribution Entry to process the contribution and the custom field, the details in the field output in the Print Acknowledgement Utility. 

Thought I'd mention it as it might be a good option to use as a place to start.

Cheers

Sandra

Hi Grayson

I have seen this managed using out-of-the-box functionality. It would depend upon your business needs, of course, as to whether or not this will work for you

1. A performance is setup to represent your Seat Naming program - it would have the appropriate Season and other details assigned. Use blackout Hold Codes for any seats that would not be offered up for Naming 
2. When the seat has been 'named' it is sold in a Ticket Order as a complimentary - no need to print any tickets of course. 
3. Processing the contribution component through Contribution Entry or Ticket Orders
4. To capture the name of the Seat - there are 2 ways, adding a Program Name with a type called Seat Naming (contribution processed in Ticket Orders) , OR add simple custom field to Contribution Entry to capture the information (using the system table T_KEYWORD) - there's details in Tessitura's Help docs on how to do that (contribution processed in Contribution Entry)

To report, you can visually see the seats that have been Named and those available on the seat map for the 'performance'. The Performance Seating Book outputs the constituents who have named seats and their seats. If you used Program Names to store the recognition name for the Named Seat (as it could be different to the Constituent name), you would use the Program Listing report to output the name. If you used Contribution Entry to process the contribution and the custom field, the details in the field output in the Print Acknowledgement Utility. 

Thought I'd mention it as it might be a good option to use as a place to start.

Cheers

Sandra

Thanks, Sandra--this is what I had in mind. I'm not as concerned about tracking the text on the plaques, etc. I'm more worried about knowing how much stock we have to sell, so to speak, and who's already bought seats.

Then setting up a performance so you have a seat map and all the associated reports is a good option. Might be worth trying it out in your Test environment to make sure this option gives you everything you need.