Help Isolating Patrons by Base Seat

Hi -
 
We are creating our rollover sets for next season and have run into an issue.  We are rezoning our house and there is a group of patrons who are impacted by the price increase AND the rezone.  There patrons are getting double whammied in terms of their price increase and I need to figure out a way to isolate them by their base seat.  The other complication is that not every patron in the existing zone is moving into the new zone (some are moving into a still different one).  I'd like to try and identify these patrons in some way and then add an attribute to their individual accounts so that I can treat them as their own renewal segment.
 
Has anyone encountered this problem?  Is there a sequel script that exists that could be shared?  Or is the next step reaching out to Consulting Services.
 
Thank you for your help.
 
Meredith

  • Former Member
    Former Member $organization

    Hi Meredith,

    Your situation is sounding somewhat familiar to issues that we are facing this year.  We are re-zoning our theatre and changing prices, but giving our renewing subscribers the opportunity to be "grandfathered" at this past year's rates.  You may want to refer to my posting here, as there are great suggestions and advice from Kevin Sheehan:

    http://www.tessituranetwork.com/COMMUNITY/forums/p/1839/6510.aspx#6510

    It took me a bit of time to work through the logistics, but so far testing of package purchasing is going very well and prices are lining up the way they should for both new and renewing sub packages.  I plan to do a test rollover tomorrow or Friday and our renewal season starts late next week.

    Feel free to email or call me to discuss the process I have gone through to make this work.  This is essentially a one year temporary plan, with next season's subs rolling over into the new prices for all subscribers.

    Duane

  • Thanks so much for your speedy response Duane!

    I talked over option A and B with our in house Tessitura expert and unfortunately I don't think either are going to work for us.

    Option A - We have already started our season build and are too far along to build new maps or make changes to our current zone maps.  If only I had sent this e-mail out a month or so ago!

    Option B - I don't feel comfortable sending out the 2010-2011 prices to our renewing subscriers and dealing with the adjustments when the renewal order is processed.  I don't want these patrons to ever see their actual FY11 prices (for fear of sticker shock) and this would mean that these patrons could not use our online renewal form.

    What we really need to a way to pull together a list of patrons who are impacted by the zone change so they can be their own rollover segment and are looking for advice on how to add an attribute/constituency to their records in advance of the rollover.  If we need to get a consultant involved I am prepared to do that, I just wasn't sure if there was an easier way.

    Thanks again for your help!

    Meredith

  • Hi Meredith -

    We built a number of lists last year when we rezoned. Here's an example of some sql you could put into list builder to identify accounts with 'B' priced seats from one year who have 'A' priced seats in the new season. This would work if you have already rolled over.

    In this example season 60 is the previous season, and 70 is the new season. You can get your season id's from tr_season. 'A' and 'B' are the zones as they are listed in the seat map legend.

    select distinct o.customer_no
    from t_order o
    join t_sub_lineitem sla on o.order_no=sla.order_no and sla.seat_no>0
    join t_sub_lineitem slb on sla.seat_no=slb.seat_no and slb.seat_no>0
    join t_zone za on sla.zone_no=za.zone_no
    join t_zone zb on slb.zone_no=zb.zone_no
    join t_pkg pa on sla.pkg_no=pa.pkg_no
    join t_pkg pb on slb.pkg_no=pb.pkg_no
    where pa.season=70
    and sla.perf_no=0
    and slb.perf_no=0
    and pb.season=60
    and za.zone_legend='A'
    and zb.zone_legend='B'



    [edited by: Brian Graham at 1:49 PM (GMT -6) on 11 Mar 2010]