Multiple seat maps attached to one performance?

Hi Kari,

I'm a little confused. Are you designating specific seats in the house as subscriber seats and certain seats single tickets? Are these general admission performances? Usually if you have 2 seat maps for one performance, you just have a double booked performance. Is the reason for this clarity in reporting?

Hi Joshua,

These are regular seated performances, but essentially a seat could be one price zone for a subscriber, but a different price zone for a single ticket buyer. After doing a bit more research and talking with JCA, it's looking like the best way to accomplish this is through microzoning, but I was hoping that there might be a less time consuming way!

Hmm...At a previous organization I did something that could be modified to work for your situation, but it is probably more complex than it is worth and wouldn't really save time...though would give you a more pure form of sales than microzoning would. I am not necessarily recommending it, but just in case it is useful to you I will share, You would need to build 3 performances in the system for each single performance...one for subscriptions, one for singles, and one which is a placeholder or dummy house that will be used to communicate between the two. Then you would build a subscriber and a single ticket fixed seat super package for each one. The subscriber subpackage would have the subscriber house and the dummy house, and the single sub package would have the single house and the dummy house. Because they share the dummy house, any seats sold in one, will be unavailable in the other. Overall reporting could theoretically use the dummy house since that would hold all attendees while you would have the singles and the subscriber houses for more specific reporting. As I said, it would be a lot of work on the front end and make your system much more complex but it is the only way I can think of to have two separate house maps for one performance and not end up double-booking, so do with that as you will.

Hmm...At a previous organization I did something that could be modified to work for your situation, but it is probably more complex than it is worth and wouldn't really save time...though would give you a more pure form of sales than microzoning would. I am not necessarily recommending it, but just in case it is useful to you I will share, You would need to build 3 performances in the system for each single performance...one for subscriptions, one for singles, and one which is a placeholder or dummy house that will be used to communicate between the two. Then you would build a subscriber and a single ticket fixed seat super package for each one. The subscriber subpackage would have the subscriber house and the dummy house, and the single sub package would have the single house and the dummy house. Because they share the dummy house, any seats sold in one, will be unavailable in the other. Overall reporting could theoretically use the dummy house since that would hold all attendees while you would have the singles and the subscriber houses for more specific reporting. As I said, it would be a lot of work on the front end and make your system much more complex but it is the only way I can think of to have two separate house maps for one performance and not end up double-booking, so do with that as you will.

Thanks so much for sharing, that's helpful. We're going to be working on this over the course of the next year for implementation in our 2021/21 season launch, so as we start looking at things more in depth in the system I may reach out again if that's okay.

Of course! Happy to help however I can.

Thanks, appreciate it!