• Replies 2 replies
  • Subscribers 414 subscribers
  • Views 279 views
  • Users 0 members are here
Related

Socially distanced pod seating (help!)

Olivia Anderson
$organization
Hi everyone!
I have a question about everyone's favorite topic--socially distanced seating.  We have come up with a plan on how we would like to sell tickets, but I am having trouble getting Tessitura/TNEW to cooperate to achieve our desired outcome.  What we would like to happen is the following:
Pod seating consisting of single, double, and quadruple seats.  When a SINGLE customer tries to select a single seat within a quad pod, it forces them to purchase all four seats, so single ticket buyers cannot buy one seat out of a double/quad pod.
I have split the single, double, and quadruple pods into their own zones.  I feel like there should be some way to achieve what I want using pricing rules, but I have not been able to get results.
We would like to avoid the "subscription" model of having a customer purchase a ticket and then hand-seating them.  While I like this idea, it would not work for the Festival since we can have upwards of 10 performances a day for seventeen days, and my staff just cannot make that happen.
Does anyone have any suggestions on how to make this work?  Or, is this something you originally tried and have come up with a better solution?  Any help or advice you can provide is MUCH appreciated!
Cheers,
Olivia A.
Spoleto Festival USA
oanderson@spoletousa.org 
Parents
  • $organization

    Hi Olivia, 

    We did something similar to what Heather mentioned where we only sold groups of 2 or 4 and used hold codes to create these available groups of seats on a SYOS map. I would also recommend naming your Price Types and Zones to say "Group 4 (must purchase 4 seats)" to reinforce the message.  Then build a zone map where you can only select the Price Type "Group 2" in those seats you've marked as Zone 2 - Group 2.

    Setting TNEW to not allow orphan seats will avoid the single seats as Heather Mentioned. We then set up a Pricing Rule to fire when a patron tried to purchase 1 - 3 tickets at the Group 4 Price Type. The Price Type would switch to our "Test" Price type which was valued at some outrageous amount and display a message indicating that they must select 4 seats in that area.  This worked really well and didn't require us to watch the seat maps. Happy to chat more if you have any other questions! Best of luck to you all!

Reply
  • $organization

    Hi Olivia, 

    We did something similar to what Heather mentioned where we only sold groups of 2 or 4 and used hold codes to create these available groups of seats on a SYOS map. I would also recommend naming your Price Types and Zones to say "Group 4 (must purchase 4 seats)" to reinforce the message.  Then build a zone map where you can only select the Price Type "Group 2" in those seats you've marked as Zone 2 - Group 2.

    Setting TNEW to not allow orphan seats will avoid the single seats as Heather Mentioned. We then set up a Pricing Rule to fire when a patron tried to purchase 1 - 3 tickets at the Group 4 Price Type. The Price Type would switch to our "Test" Price type which was valued at some outrageous amount and display a message indicating that they must select 4 seats in that area.  This worked really well and didn't require us to watch the seat maps. Happy to chat more if you have any other questions! Best of luck to you all!

Children
No Data