I am one of several members in a consortium group using/sharing Tessitura data. I want to flag a patron who has ticket history with another arts organization as wanting to receive information from mine. For instance: a patron buys a ticket to the Ballet but also wants to be added to the Orchestra's mailing list (they have no Orchestra ticket history). I also want to flag new patrons accordingly from name capture by event or requested series information. How/where would that patron be flagged for me to pull and mail to? We do not want to use Constiuent as that would add too much to the patron's screen (several different orgs and series makes for a lot of abbreviations). We've discussed using Attributes but I am currently limited in which Attributes I can pull in List Builder.Any suggestions or best-practices that you have used?
Hi Cara -
We created Information Requests > Activity Types CSI's that are shared across organizations in the consortium. Particularly because there is a centralized box office, this now makes it really easy for them to pass along those requests to the specific organizations.
We don't seem to have access to the Info Request --> Activity Types function. I'll have to look into that. We recently got access to CSI's which we are using to track customer issues. Is it possible to run a list with complete mailing info from those?
Cara-
We use CSIs for our brochure requests even though we are just one company. You can pull a list based on this criteria. I often use it as a segment in my extractions for the appropriate mailings. I think that that is what Rebecca is talking about. When you pull the list you use this set of criteria from list builder and choose the appropriate one (which could vary depending on how you set up your CSIs).
Hope that helps!
Amanda Sheehan
Ticket System Administrator
Cincinnati Playhouse in the Park
P Please consider the environment before printing this email.
It does. Thanks to you both. I'm new to the Tessitura List Pull world. We do have the ability to use CSIs as a criteria. I'll see if we have the possibility to modify how it's currently used.