SUPER PACKAGES. HELP!

Greetings! 

So here is my problem and I hope someone out there in the Tessitura world can assist me. 

We perform at different venues each year. We have our 4 mainstage productions every year that we are able to roll our subscribers into. We also perform a couple of productions at different smaller venues each year. 

What my leadership team wants is to build our season with all 6 productions into a super package and invoice our subscribers for all. 

My issue runs into the variety of venues. I'm building new facilities every season.. new houses. So I don't have anything to roll from. 

Example:

Next season we are going to be performing once again at a brand new venue. I don't currently have the specifics to build the new facility and probably won't have them until mid October. 

We will be announcing our new season in January so that is a very short time period for me to complete this. 

Is there anyone out there who might be able to put me in the right direction with a plan and a how to?

Thank you in advance!

~Renee Smiley

Atlanta Opera

Parents
  • Hi Renee,

    I'm currently assisting one of our consortia members on this right now. There are a few options that depend on your org's business practices and at what point in the process you want your subs to determine their seating. 

    You can: 
    1) Complete an order import in advance of your rollover seating the patrons into a "dummy" performance that you then use as the source for your rollover. The order import process is pretty straightforward, so it reduces the friction of having to load each order and seat. 

    2) Roll the patrons into dummy performances. As they renew, you confirm their date/time/seats for the real performance and exchange them out of the dummy and into the real. 

    3) Roll the superpackages and let them fail. In the application, it will load the additional SLIs needed and you can seat from there. Note, this means the renewal will be incomplete and I have no idea what this will do on the web. But it works in the application

    I think there might be some other creative solutions, but I'd recommend either 1 or 2. Happy to help answer any additional questions! 

    Best, 

    Katina

Reply
  • Hi Renee,

    I'm currently assisting one of our consortia members on this right now. There are a few options that depend on your org's business practices and at what point in the process you want your subs to determine their seating. 

    You can: 
    1) Complete an order import in advance of your rollover seating the patrons into a "dummy" performance that you then use as the source for your rollover. The order import process is pretty straightforward, so it reduces the friction of having to load each order and seat. 

    2) Roll the patrons into dummy performances. As they renew, you confirm their date/time/seats for the real performance and exchange them out of the dummy and into the real. 

    3) Roll the superpackages and let them fail. In the application, it will load the additional SLIs needed and you can seat from there. Note, this means the renewal will be incomplete and I have no idea what this will do on the web. But it works in the application

    I think there might be some other creative solutions, but I'd recommend either 1 or 2. Happy to help answer any additional questions! 

    Best, 

    Katina

Children