Hi all,
as pretty recent alumens of the Tessitura Network, we're currently working on moving our sponsor-handling from an external, separate CRM-system into Tessitura, specifically the Plans module.
One issue that's come up is how to best handle the pool of complementary tickets we promise sponsors as part of their deal with us.
The way it works is, we promise the sponsor 100 tickets (for instance) that they can use at their leisure throughout the season. Typically, the coordinator in charge at the sponsor calls a few days in advance and asks for 4 tickets to a specific performance.
Would appreciate any suggestions as to how we can record this pool of 100 tickets to start with, and then write them down as they're spent throughout the season.
They aren't held or allocated in any specific performance in advance.
I've been thinking about using a ranking and value or attribute and value, or maybe there's a smart way to use CSI's or Plans?
Thanks in advance, and all the best from Denmark :-)
Martin
Hi Martin,
I am about to start planning ways to do this too, so will follow this thread with interest
My thinking at the moment is to have the ticket number display in the constituent header, maybe from an attribute (I haven't really tested, and this might be to flexible/editable) and have it count down (or up) based on the number of tickets (with a specific price type, so they could buy tickets in the same account and not have them count towards their allocation) they had used, so there was a visual display of what they had used. e.g. 14/100
My thinking was that this should work as a simple view only way if the tickets were only allowed to be requested via phone and via the Sponsorship department. If we wanted to do this on line, then I think it would have to become a bit more sophisticated. so people didn't go over their limit.
Looking forward to hearing what others are doing as I am sure there are some more sophisticated ways to do this.
Caryl
Hello Caryl,
Thank you for joining the discussion - happy to hear your working on this issue too.
I like the idea of showing the ticket count in the header, making it quite fast and easy to find it .As you say, it should be linked to something like a specific price type, to be able to separate it from other types of sponsor tickets or regular tickets. Maybe a price rule could work.
Not sure how I feel about using "merely" an attribute to store allocation value, it sounds too simple :-) But if I understand you correctly, the attribute value is only to show the maximum number of tickets, right? So no one would have to adjust it throughout the season, except if the allocation changes, like due to a new agreement?
Cheers
Yes, that's what I was thinking, an attribute just to indicate the max tickets.
Maybe it's a local system table with a row for each Sponsor, that shows their designated allowance each year (but can be updated if the agreement changes). That way there's an audit trail of changes etc.
We put the ticket count in the header
Flags: CORP38
38 means the Constituent, who originally had 90 tickets at the beginning of the season, now has 38 remaining tickets for the season because they've used 52 tickets. It's under the attributes tab