We are getting started with tracking volunteer service activities in Tessitura. I have some great examples from other organizations of the custom screens used for tracking volunteer service hours.
Our program allows volunteers to redeem their service credits for tickets to shows. We need to track the credits used as well as the credit balance remaining. I expect that other organizations have similar programs.
My question is, how do you track the credit redemptions and the credit balance? If anyone has something set up in Tessitura for this, I would love to hear about it. Thanks!
I set up something similar in my previous job relating to staff comps. If you're storing their credits against a staff account, the LP_CUSTOMER_RANK could trigger the credit update based on the volunteers service activities, and as part of (or separate) to the nightly ticket history update, you could update their redeemed value based on ticket history for their account (assuming you'd only query a show booked that was somehow categorised as being used against their credit). Would something like that work for you?
Annie
Thanks Annie!
Using a rank as you described could work. We'll take a look at that option.
Hi Susan,
We do something similar for other comps which I will probably integrate into our volunteer tracking as well.Here is what I plan on doing (assuming it all works out).Create a nightly job to calculate total comps available based upon hours worked, and store this as an attribute. (if you need this in real time you could look into the pros and cons of using lp_customer_rank)Create a comp code reason for volunteer comps.Add to our existing custom header code to take total comps available and subtract them from comps used based upon comp code reason. This is displayed as total acquired, total available and total used in the header.
Since we already have a place in our header for comps I might as well take advantage of that, however you could just do all this in a nightly job and save it as an attribute.
Shoot me an email if you want more info.
Cheers!
Thank you Ryan!
Using the comp code reason to track tickets used is a great suggestion. And I had been thinking about an attribute, so we might go that route.