Sending reminder emails to your patrons is a great way to connect with your subscribers before their show. Use Triggered Campaigns in WordFly to send these pre-show emails. Triggered Campaigns are set up one time and sent at regular intervals to any subscribers that meet your Tessitura list criteria.
We’ve put together basic reminder email list criteria to help you! Follow the steps in this post to get started. If you need additional help, feel free to email us or contact Tessitura Support for expert advice.
Topics covered in this article:
Let’s look at three questions for the Dynamic List Manager list criteria:
• Is the subscriber coming to the show?
• Does the subscriber have an email?
• Has the subscriber opted out from anything?
Where does this information live in Tessitura?
• Ticket history is usually on the household in Tessitura.
• Emails can exist on Household, Affiliates and Individuals. Both a Household and their multiple affiliates can have emails.
ADD THE FOLLOWING CRITERIA TO YOUR LIST:
• Use this criteria with the “> =” operator. Your value will include DayRunDate and you can specify details here. In our example below we use +2 here but you can also use +1. Decide what works best for who you would like it to pull when the list is imported.
• Use this criteria again with “< =” operator. Your value will include DayRunDate and you can specify details here. In our example below we use +3 here but you can also use +1. Decide what works best for who you would like it to pull when the list is imported.
“Ticketing Performance Name”
This comes from Ticket history. Your value will need to match your specific performance code and not the one in our example below.
• Eaddress Purpose 5 in ‘Yes’ :: Checked Purpose
• Eaddress Inactive in ‘No’ :: only active emails
“Primary Eaddress Flag”
• Primary Eaddress Flag has ‘Yes’ :: Has an email addressed marked as primary address
(a primary Eaddress can’t be inactive so you don’t have to check for that)
• Subscription Season does not have ‘Current Season’ :: Single ticket buyers only!
Example of criteria set up:
Another criteria example using slightly different criteria and DayRunDate settings:
*New in v11 is the ‘Search Household’ check-box. Checking this box will include both the household and the primary affiliates into the pool of people which will later join with the email criteria. This does limit the patrons pulled to household and primary affiliates only. If you want to include ALL affiliates you will have to build a separate dynamic list and then use that list instead of this criteria. Also, if you have multiple shows per day, you may have to add extra criteria or suppression lists or create two triggered emails for evening shows and one for matinees.
Not quite done! There’s one more important piece of criteria to add:
Don’t forget to suppress any addresses that have restrictions under the subscriber’s record on the General Tab > Emarket Restriction.
Typically a reminder email will contain performance date and performance name information for the subscriber's email. The output set elements for performance date and performance name usually have a * next to the element. This symbol means the element returns multiple rows per subscriber, which unfortunately means WordFly can't use this output set.
How do you include elements that return multiple rows? You can adjust your elements with some SQL to avoid multiple rows.
We have put together an example of a SQL output set that might help your team. Since every Tessitura database is different you will need to review this with your team to ensure the examples will work with your data. In most cases the SQL will need to be modified to meet your criteria.
Review your Output Set in Tessitura:
The output set will probably return the following dynamic information:
• Customer Name
• Inside Salutation
• Is Subscriber
• Perf Dt *
Building the SQL Output Set Elements:
“Performance date” by default returns multiple rows per subscriber. You can verify this by looking in TR_QUERY_ELEMENT, you should see a * by this criteria. Any element with a * returns multiple rows. There is a checkbox “return single rows) to the right of the element but checking this will not change the results for this element, it will still return multiple rows.
Here’s an example of what your output set might look like:
The column “Data From” is referencing the custom SQL.
This is where the custom SQL comes in handy for your output set. The attached ticket history view example goes along with the criteria referenced above. This is only an example, changes will be required to work with your specific data.