We're looking to use Wordfly for a triggered email campaign. What we want to do is send a same day email to all people who bought general admission tickets and attended that day, thanking them for their visit. Then, email that same set of people 2-3 days after the visit, soliciting membership at a discounted rate.
Has anyone else set up something similar? What were the results? Were there any roadblocks that you ran into that you could share with us as we start this process?
Thank you in advance,
Mike Dorsey
CRM Specialist - National WWI Museum and Memorial
mdorsey@theworldwar.org
Hi Mike,
This should be fairly easy to set up in Tessitura and WordFly.
The key thing for WordFly is that you need to set up the Tessitura list manager criteria first and then build your email. Do you use NSCAN?
If so, your Tessitura admin can set up a list manager criteria of attended. You would then add in additional criteria of >= and <= RunDate for something to deploy the same day.
You would then make a separate email and change the criteria to >= and <= -2 for two days after they attended your organization for the membership solicitation.
I'm not sure exactly how these criteria are used for a Museum, but here's a screenshot for a thank you email that sends the same day that a patron attends a play.
I'm not sure if that all makes sense, but hope it's a start!
Feel free to message me for more details. Thanks!
Wow, this is great! I was expecting a few horror stories and words of warning, but you've basically supplied the full instruction manual. Thank you, Gabriela! This makes this seemingly-daunting process a lot less intimidating for us.
-Mike
Thanks again, Gabriela. Thought of another question: is there a procedure involved that ensures that the list updates daily before Wordfly uses it to send the emails? Will this happen automatically?
Yes. When you save the list in Tessitura select TMS and DYNAMIC. That means that as you go through time the list will automatically update and it will mark it for use in WordFly.
In the WordFly setup you then create a Triggered email and for the final step set it to run daily at a specific time. So it will automatically re-generate your Tessitura list each day when it deploys.
You can also set it to go to a patron once or anytime they meet your criteria in WordFly.
Hope that helps! I found a lot of the WordFly documentation sparse, so happy to help make this easier for the next person.
Mike, our set up looks much like the Goodman's, though ours is configured even more dynamically. We're also a multi-venue organization, and need to address that within criteria.
EXAMPLE LIST (it's SQL only because we needed to have a join/union manually adjusted in order to skip over something related to invalid addresses_
Select Distinct a.customer_noFrom V_CUSTOMER_WITH_PRIMARY_GROUP a WITH (NOLOCK)JOIN (Select a1.customer_no From LVS_TKT_HIST a1 WITH (NOLOCK) Where a1.perf_dt <= DateAdd(dd,2,Convert(varchar,GetDate(),112)+' 23:59:59') and a1.season in (145) and a1.perf_dt >= DateAdd(dd,2,Convert(varchar,GetDate(),112)) and a1.venue_id in (2) and Role=2 ) as e ON e.customer_no = a.customer_noJOIN (Select a1.customer_no From T_CUSTOMER a1 WITH (NOLOCK) Where ISNULL(a1.emarket_ind,3) in (3)) as g ON g.customer_no = a.customer_noJOIN (Select a1.customer_no From vs_eaddress a1Where a1.address like '%@%'AND IsNull(a1.inactive,'Y')='N') as i ON i.customer_no = a.customer_noWhere IsNull(a.inactive, 1) = 1AND EXISTS (select * from vxs_const_cust WITH (NOLOCK) where a.customer_no = vxs_const_cust.customer_no and vxs_const_cust.constituency IN (186))AND a.customer_no not in (select customer_no from T_LIST_CONTENTS tlc with (NOLOCK) where tlc.list_no = 30549)UNIONSelect Distinct a.customer_noFrom V_CUSTOMER_WITH_PRIMARY_GROUP a WITH (NOLOCK)JOIN (Select a1.customer_no From t_list_contents a1 WITH (NOLOCK) Where a1.list_no in (2362,36890)) as e ON e.customer_no = a.customer_noWhere IsNull(a.inactive, 1) = 1
OUTPUT SET
The parameters for the above are start date, end date, theatre, season type.
The other thought I'd add is to reserve time to evaluate Appeal Structure for related sources. Advance strategy there can end up being a huge asset to data organization and to additional follow up. With promotions being created using the same name daily (or other repeated frequency), I've found it useful to send them all into a discrete Appeal rather than overwhelm the ones that perhaps have more interesting stories to review. Also, for some message types, you'll want to make sure people don't get something more than once during a time frame (like if you have a day buyer come two days in a row), and being able to add some sort of 'Not' idea can be much easier when you have a dedicated Appeal.
Re the question that you've posted while I have been typing:
As long as you list and output set are built dynamically, everything regenerates on the WordFly triggered send schedule.
Ah yes, Gabriela Jirasek's referencing something that might sound at odds with what I've just written, so I'll clarify:
The settings about 'get once' or 'anytime' etc are one way of handling the repeat visitor, but it's not always been the right fit for us and we've gone with the Appeal idea. It might have been that the restrictions didn't match our campaign needs, but it also could have been something like Drip Message 1 should go out for every instance, but Drip Message 2 only to those who didn't click on the first one. Combinations like that.
And another word of "warning" that occurs as these thoughts together... know that you'll need to consider any seed list names within this. We've definitely had a mild panic attack or two when the person monitoring a new campaign didn't get their copy.
Thank you, Jamie! This is another very helpful answer. We do want to make sure we are not emailing the same person repeatedly, so I'm glad you brought that to light.