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
We are investigating what happened to Jamie O'Brien's reply via email, but for posterity here is what she said:
"Christine - The very short answer to your very big project is that you probably want to aim to do your content variations via dynamic content within the email campaign. Obviously, this still requires advanced set up, but it means you get to avoid commissioning custom content fields and output set queries. It also helps keeps the content management directly in your world, which (from the way you've phrased it) is probably an improvement on needing to enlist data entry from another department as you need to tweak things.
Mine, in WordFly language, looks like this in one instance:
{{##Production## || Show}} is playing at {{##Location## || venue}}. {{if(##Location## contains Victory) then (The entrance to the theater, pictured above, is underneath the grand staircase, on the north side of 42nd Street, closest to 7th Avenue.) endif else(The entrance to the building, pictured above, is located to the west of The New Victory, in the middle of the block.) endelse}}
A moment of caution though: your plan for one list and one campaign *only* works correctly if your patrons are only ticketed for a single event during the specified timeframe. As the point of email systems is that (1) email is the primary identification for the constituent and (2) to help ensure you don't act like a spammer, only *one* instance of an address being in a List will get recognized and delivered. Repeat instances, however valid the inclusion is given Ticket History, will be dropped and the patron will not receive that additional version of info. I hope you luck out and this isn't a concern, but I was proven wrong when I assumed it wouldn't be for us.
What we found we need to move to was a singular template with dynamic content, but distinct campaigns per venue with list and output criteria narrowing the data scope by venue. The reliance on dynamic content can make it feel a bit complicated, but I prefer managing one centralized file of content than worrying about maintaining/updating a range of very, very similar files.
This all being said (in now a not so short response), I do rely on a lot of custom content fields and custom list/output set elements, too, and you may need to as well. But in terms of displaying standard content, test how much you can achieve with dynamic expressions."
Thanks Todd.