new super packages

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

The Milwaukee Repertory Theater currently offers fixed-seat subscription series in each of its three venues, 32 packages in two of the venues and 48 in the third.  For next season, the wish is to create overall, multi-theater Rep packaging, so we are planning  SuperPackages where the formerly singular individual-stage packages would constitute the sub-packages.  For instance a subscriber with a 6 play package to our largest theater would be moved to a package with 5 plays in the main theater and 2 in another theater.  Preliminary Super-Package testing raised a couple of major issues:

 

If a patron refuses one of the sub-packages, how can that sub-package be removed?

 

When a patron needs to change the series assignment for one of the component packages, how can that be processed?

 

Also, one venue is being reconfigured, so current subscribers will need to be rolled into a new facility. Any feedback on the pros and cons of different ways to do this would be greatly appreciated.  And any hazards to avoid especially appreciated.

Parents
  • Matt,

    One question for you - do you actually want patrons to be able to "refuse" one of the sub packages?  If so, then you will have to create a whole other set of  packages for each venue that you would re-seat the patron in. (Return or delete the super package and then re-add the appropriate new package).   This becomes tricky with how you handle your base seating and upgrades, so think this through before implementing.  If you want superpackage folks to have priority, then you might not want to offer the same seat to someone who is not subscribing to the larger package.  Or maybe you don't care, in which case don't worry about it.

    When you say "component packages" - do you mean sub packages?  Superpackage upgrades and seating requests can be handled the same way as they would be for regular packages.

    The only thing I would caution you on is how you set up the superpackages in terms of performance dates and sub packages, because when you have performances that are part of more than one sub package, the base seating issue can be tricky. We use only the composite maps to avoid any issues with this.

    As for your venue reconfiguration, any time you have a facility change, I recommend completing your rollovers in your test system first so you can find out if you have any issues and fix them ahead of time. 

  • Well, we don’t really want them to refuse one of the sub packages, but we anticipate they might – this is a new change for us and some of our subscribers have stuck with the same seats, same venue, for decades.  But I get what you’re saying about having the other packages waiting in the wings.

     

    Thanks Annie.

     

    MH

    matt_hilgers@milwaukeeartspartners.org

    IM:  matt_hilgers

     

     

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Annie Gribbins
    Sent: Tuesday, February 09, 2010 2:48 PM
    To: Matt Hilgers
    Subject: Re: [Tessitura Ticketing Forum] new super packages

     

    Matt,

    One question for you - do you actually want patrons to be able to "refuse" one of the sub packages?  If so, then you will have to create a whole other set of  packages for each venue that you would re-seat the patron in. (Return or delete the super package and then re-add the appropriate new package).   This becomes tricky with how you handle your base seating and upgrades, so think this through before implementing.  If you want superpackage folks to have priority, then you might not want to offer the same seat to someone who is not subscribing to the larger package.  Or maybe you don't care, in which case don't worry about it.

    When you say "component packages" - do you mean sub packages?  Superpackage upgrades and seating requests can be handled the same way as they would be for regular packages.

    The only thing I would caution you on is how you set up the superpackages in terms of performance dates and sub packages, because when you have performances that are part of more than one sub package, the base seating issue can be tricky. We use only the composite maps to avoid any issues with this.

    As for your venue reconfiguration, any time you have a facility change, I recommend completing your rollovers in your test system first so you can find out if you have any issues and fix them ahead of time. 

    From: Matt Hilgers <bounce-matthilgers3174@tessituranetwork.com>
    Sent: 2/9/2010 2:21:47 PM

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    The Milwaukee Repertory Theater currently offers fixed-seat subscription series in each of its three venues, 32 packages in two of the venues and 48 in the third.  For next season, the wish is to create overall, multi-theater Rep packaging, so we are planning  SuperPackages where the formerly singular individual-stage packages would constitute the sub-packages.  For instance a subscriber with a 6 play package to our largest theater would be moved to a package with 5 plays in the main theater and 2 in another theater.  Preliminary Super-Package testing raised a couple of major issues:

     

    If a patron refuses one of the sub-packages, how can that sub-package be removed?

     

    When a patron needs to change the series assignment for one of the component packages, how can that be processed?

     

    Also, one venue is being reconfigured, so current subscribers will need to be rolled into a new facility. Any feedback on the pros and cons of different ways to do this would be greatly appreciated.  And any hazards to avoid especially appreciated.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • Well, we don’t really want them to refuse one of the sub packages, but we anticipate they might – this is a new change for us and some of our subscribers have stuck with the same seats, same venue, for decades.  But I get what you’re saying about having the other packages waiting in the wings.

     

    Thanks Annie.

     

    MH

    matt_hilgers@milwaukeeartspartners.org

    IM:  matt_hilgers

     

     

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Annie Gribbins
    Sent: Tuesday, February 09, 2010 2:48 PM
    To: Matt Hilgers
    Subject: Re: [Tessitura Ticketing Forum] new super packages

     

    Matt,

    One question for you - do you actually want patrons to be able to "refuse" one of the sub packages?  If so, then you will have to create a whole other set of  packages for each venue that you would re-seat the patron in. (Return or delete the super package and then re-add the appropriate new package).   This becomes tricky with how you handle your base seating and upgrades, so think this through before implementing.  If you want superpackage folks to have priority, then you might not want to offer the same seat to someone who is not subscribing to the larger package.  Or maybe you don't care, in which case don't worry about it.

    When you say "component packages" - do you mean sub packages?  Superpackage upgrades and seating requests can be handled the same way as they would be for regular packages.

    The only thing I would caution you on is how you set up the superpackages in terms of performance dates and sub packages, because when you have performances that are part of more than one sub package, the base seating issue can be tricky. We use only the composite maps to avoid any issues with this.

    As for your venue reconfiguration, any time you have a facility change, I recommend completing your rollovers in your test system first so you can find out if you have any issues and fix them ahead of time. 

    From: Matt Hilgers <bounce-matthilgers3174@tessituranetwork.com>
    Sent: 2/9/2010 2:21:47 PM

    Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    The Milwaukee Repertory Theater currently offers fixed-seat subscription series in each of its three venues, 32 packages in two of the venues and 48 in the third.  For next season, the wish is to create overall, multi-theater Rep packaging, so we are planning  SuperPackages where the formerly singular individual-stage packages would constitute the sub-packages.  For instance a subscriber with a 6 play package to our largest theater would be moved to a package with 5 plays in the main theater and 2 in another theater.  Preliminary Super-Package testing raised a couple of major issues:

     

    If a patron refuses one of the sub-packages, how can that sub-package be removed?

     

    When a patron needs to change the series assignment for one of the component packages, how can that be processed?

     

    Also, one venue is being reconfigured, so current subscribers will need to be rolled into a new facility. Any feedback on the pros and cons of different ways to do this would be greatly appreciated.  And any hazards to avoid especially appreciated.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
  • I believe if you just set the minimum number of perfs to zero for the potentially refusable subpackages in question, then you could just delete them (peel-back style). The assumption here being that when you renew them, even though they declined a certain sub-component this year, you'd want to try to get them back into it next year. If that's not the case, then I think smaller packages that are super-package-in-question minus refusable sub-package is the only other way to do it.