We're trying to figure out the best way to track benefit comps in Tessitura. Any suggestions on using Premiums, Issues, ticklers, CSIs, etc?
We offer complimentary tickets to donors at certain levels and we'd like to have a system in place to track if this benefit has been used.
Thanks for any information!
We want to track this on the constituent level? This way we can report if anyone has unused comps, call them up and have them go see a show. We can then also see when they used this particular benefit.
We also have a good system in place when they "cash in comps." We also use diff. comp reasons.
Do you ever track who to issue comps out to? and How?
Thanks,
HC
From: Brenda Fehlberg <bounce-brendafehlberg2154@tessituranetwork.com>Sent: 2/9/2010 8:40:33 PM
We use Attributes to track staff comps within Tessitura. It's a bit of a manual process, but has worked well for us. At the museum each staff member gets 20 free Omnitheater tickets each year. We have an Attribute called Number of Staff Tickets that uses a drop-down. Whenever a staff member comes in or calls to use their tickets the tickets are sold to the desired movie using a Comp price-type with the correct reason code. The staff member then also decrements the correct number of tickets from the Attribute. By trial and error we found that using a drop down to track numbers is crucial because if you manually enter in a zero Tessitura drops the attribute completely.
At the beginning of the fiscal year we use the Manage Attributes utility to update all staff records to 20 (we have a staff constituency so we can easily run a list of all staff accounts). For further tracking we have the Attribute set up to pull into List Builder so we can run lists of who has used all their tickets, who has tickets left, etc...
Hi Kjersten
Would you still recommend this method for tracking staff comps or is there a new system that can work? We are looking to implement and track comps for out staff and volunteers.
Thanks
Liz
If the benefits are of the nature of X number per year, for out of the box functionality, I still think using an attribute is a great solution. As I said, it does necessitate some manual work, but is very simple to set up and get running. It's also not too tricky to get into the header if you want quick access to view the data. If the benefits are more constant you might consider looking at setting up a pricing rule (perhaps based on a staff constituency) to change the price accordingly.
Another option to consider, and this may not apply in your case, but wanted to throw it out in case it does - if you've got any structure set up to track and allocate benefits for members consider giving your employees and volunteers 'memberships' and using that same structure to track their benefits. I've worked with many museums that have done something similar and it's worked well.
I hope this helps!