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
Wow, some great suggestions, thank you all for chiming in. As often with Tessitura, there really are a lot of different ways to a useful solution. I'll do some more experimentation, as we need to find a way that's convenient enough to use, and also allows for some aggregate reporting.
Eventually, we'll want to develop a self-service solutions that'll allow sponsors to get their tickets online, so there's something to keep in mind too.
Beth, even though the custom table solution has not been flawless, do you find it's been worth you trouble?
Thanks