Corporate ticket allocation & member renewals

Hi all

Here at Live Theatre we provide corporate partners with benefits such as free tickets. We can see on their ticket allocation on their record how many tickets have been used, but in terms of keeping an updated running total of how many free tickets/benefits they have left I simply record info in an excel spreadsheet. Does anyone do anything to integrate running totals of usage of benefits on Tessitura?

 

I also have a query about membership renewals. Currently we offer only paper standing orders for regular payment. Often these are made out 'until further notice' so on our system there is no end date to these memberships. We would like to start stewarding these donors with a yearly thank you, but I am unsure how we would utilise acknowledgment reports without a specified end date for memberships. Does anyone do anything similar or have any advice on this issue?

 

Lizzy

 

 

 

Parents
  • We aren't currently doing any tracking in Tessitura for these situations but I have a thought. If you used an attribute to say how many comps they are entitled to for the year and then another one for how many they have booked then maybe you can pull the difference into the constituent header? So it would show how many they have remaining when your staff member pulls up the account.

    I imagine the one showing how many have been booked would need a custom procedure to update it automatically for you.

    Not sure if that works in reality as I definitely haven't tried it.

    Whatever you decide to do - good luck!

  • Hi Beth

    That sounds an interesting idea. Is it quite straightforward to create a new constituent header/attribute? I can't seem to work out how to do that - do you require specific administrative access rights?

    Thanks in advance

Reply Children
  • Hi Lizzy,

    Attributes are setup in the T_KEYWORD and TX_KEYWORD_CUST_TYPE system tables. Adding items to your header will depend on how your header is built. We use Tessitura's Flex Header solution which is setup in TR_FLEX_HEADER and TR_FLEX_HEADER_ELEMENT. But you may be using a completely custom one that is setup in InfoMaker.

    If you have a database administrator in house they should be able to tell you if they think this option is feasible.