we are getting ready for our single ticket campaign to launch for the first time on Tessitura and are wondering what other organizations are using as a single ticket source code. Is it as simple as creating a source code named "single ticket" or do you break it down further or add in the year etc
any advice is welcomed with open arms :-)
We have a Single Ticket Appeal and under that, generic source codes such as website, newspaper, word of mouth, email news, billboard, radio, etc. These are set up not to expire. That way the ticket sellers are familiar with the basic source codes when they ask “Where did you hear of this performance?”
When we do a more targeted appeal that we need to track, for instance a special offer to a partner’s mailing list, that will have a dedicated source code usually with an expiration date.
I always find that the trick with Tessitura is to determine how specific you need to be to so the data collection has value to the organization and yet not go overboard and create excessive labor for information no one will ever use. It takes some time to find that magic line (and it changes as everyone gets to know the software better). That’s the value and the challenge of the software. It can do so much, you need to know how much to do.
Good luck,
Susan
Susan Crockett
Chief Information Officer
Ruth Eckerd Hall
From: Julie Gregorchuk [mailto:bounce-juliegregorchuk3305@tessituranetwork.com] Sent: Tuesday, July 24, 2012 2:59 PM To: Susan Crockett Subject: [Tessitura Ticketing Forum] Single Ticket Source Code
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Thank you all for the suggestions! Much appreciated!