I would give my eyeteeth for a "one size fits all" document to walk me seamlessly through set-up of our first Triggered email campaigns. Short of that, I am grateful for any assistance more experienced Marketers can provide.
We are working on setting up pre-show reminders right now.
We are a performing arts centers with multiple campuses and venues.
To keep things as streamlined as possible, we are hoping to set up a SINGLE list that pulls people with a show coming up in the next 48 hours.
My example: One list, with 5 different performances pulling into that list.
Those performances are on separate campuses that may each have different traffic alerts/warnings related to city-wide construction projects.
For events that may each have different security procedures (some involve bag check, some involve wanding, some involve metal detectors).
For events that may also have specific pre and/or post-show entertainment in the lobby or bar.
I am not involved in building events in Tess; just in marketing them.
WHERE in Tessitura should I be asking my Ticket Set-up peers to start inputting these (special instructions) blocks of text that relate to traffic, security, pre/post-show events?
So that I can create a Tess Output set that then pulls those blocks of text [for a specific campus, or specific event] dynamically into my Triggered Wordfly email template?
Thanks for your help!
Christine
Jamie is correct to suggest splitting these into more than one e-mail. One example I ran into in a past life was parents coming to see their children in The Nutcracker—parents come to the matinee and the evening on the same day and won't be satisfied with only getting an e-mail about one of their performances.
Tessitura lets you assign a timeslot during ticketing setup so we brought that into our views and custom elements so our lists and outputs would reflect either matinee or evening. We used these to create two triggered e-mails that fire within five minutes of each other. (Hopefully no parents get upset and call us within that five-minute window between "see you tomorrow afternoon" and "see you tomorrow evening"!)
Facility can be used to do the same thing for venue if necessary—ex: a parent could buy tickets for their children at one venue and themselves at another using the same e-mail but that's the only edge case that pops to mind for me venue-wise.
-- Mike
Thank you Mike. That's a great example.
In the second paragraph of your response, when you mention "views and custom elements"...where do those live? I am sorry to sound so green - but is that something to do with Output Set Manager?
Yes; the custom elements eventually live in Output Set Manager. For our e-mails we needed information from several Tessitura tables so we used a custom SQL view to put them together in one place. Then in GoTo -> System Tables -> TR_QUERY_ELEMENT we added new lines for each custom output set element we made in our view). After we saved our changes the new elements showed up in Output Set Manager.
This requires help from whoever in your organization can edit SQL/access System Tables/etc.
The new version of Output Sets reduced our need for custom elements since the filtering is really good, but this is one case where we still use them.
Mike, thanks for this level of detail. I know our database manager will appreciate it. Chris