Membership Levels in a Consortium

Former Member
Former Member $organization

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

We at the AT&T Performing Arts Center operate within a consortium, but also manage a centralized box office utilized by many of our resident companies and consortium partners.  We opened in October, and only recently launched our first membership/annual campaign and are working through issues as they arise.

 

IT recently reconfigured our Tess headers to include our Membership Levels and Next Perf (see below) so our box office employees can easily identify our high level members and offer them the appropriate membership perks (ex: discounted self-park at CC3, CC4 and CC5; discounted valet at CC4 and CC5). 

 

We realized this morning, however, that the membership levels populated in the header seem to be tied to the organization presenting the Next Perf (so, while I see one of AT&T PAC's shows as the Next Perf and CC5 as the membership level, Box Office employees (and others with wider control group access) see a resident company show as the Next Perf and a resident company membership level).

 

Has anyone else run across this issue?

 

How can we easily and consistently communicate to our BO employees who our high level members are so that they can extend the highest levels of customer service?  Attributes are not easily seen and an additional Constituency will only confuse the header further, since our box office folks see constituencies for all Consortium users. 

 

I can try and include a screen-shot, if that would help.

 

Thank you!

Rhealyn Carter, AT&T Performing Arts Center

 

 

 

Parents
  • We simplified our header by removing the actual membership level and replacing groups of levels with clip art icons that represent the various benefit levels. 

    Our top membership levels all have a $ in their header.  We have another group of membership levels that allow for special discounts that shows up as % and yet another group that results in a privileged buying period that has a little first place trophy. 

    Using this method you could set the header to look only at the membership levels for your organization and ignore the resident company levels.

    On a separate note, we also limited the constituencies that the ticket sellers see to only the ones that the need to inform their work processes.  It gave us more real estate on the header to play with and cut down on the clutter they had to sort through.

Reply
  • We simplified our header by removing the actual membership level and replacing groups of levels with clip art icons that represent the various benefit levels. 

    Our top membership levels all have a $ in their header.  We have another group of membership levels that allow for special discounts that shows up as % and yet another group that results in a privileged buying period that has a little first place trophy. 

    Using this method you could set the header to look only at the membership levels for your organization and ignore the resident company levels.

    On a separate note, we also limited the constituencies that the ticket sellers see to only the ones that the need to inform their work processes.  It gave us more real estate on the header to play with and cut down on the clutter they had to sort through.

Children
  • Former Member
    Former Member $organization in reply to Kay Burnham (Past Member)

    Hi Rhealyn

    If you're seeing the membership levels associated with the company of the Next Perf, that's presumably the logic programmed in by your IT folk. It's not native Tess.

    If you only want to see your own membership level, that should be a fairly simple change to your header code, as Kay suggests.

    On the other hand, if you want to see the level appropriate for the presenter whose ticket the constituent is about to buy, that's a serious logical  challenge, possibly involving a little precognitive ability, (if you start sales flow from the constituent, rather than from the performance) which is not part of the Tess functionality, clever though Tess is... :-)

    I don't think you need to look at using additional attributes or constituencies. You already have the information you need in the system. It's just a question of how to present it, and the logic of what to present when.  You might have to get a bit creative there, and try to develop some graphic display coding that generates a picture to convey a lot of information at once.  

    Ken

  • Former Member
    Former Member $organization in reply to Former Member

    Ken and Kay - thank you both for your tips!