WordFly Help

Hey there Molly,

I understand completely! It can be really hard to translate technical needs to folks who are responsible for the more creative parts of a project. I've tried, with mixed results, to come up with kind of a check list of the standard parts they might need from Tessitura such as do they want to include the customer name, if yes then what style (formal or casual)? Maybe Membership Level? A dollar amount? I'm just throwing things out there. Think of those questions you feel like you ask every single time (which it looks like you already have), and make that checklist part of their project process?

As for source codes I am a huge advocate for having those on the record for any communication, but if you feel like you could really do without those for perf reminders just don't fill in the Appeal and source info when you upload the list to WF.

Then it won't create the promotion on the record but it won't create the source in the Appeal either, which sounds like it would be fine for you but I just thought I'd point that out just in case.

I hope that's helpful! Good luck

Jenny O'Neill-Englund

Hi Molly - 

If you search the forums, I've got a bunch of older replies covering things that related to most of what you've called out--I think they'll still be helpful, even if from several years back.

The TL;DR answer to your last point though is--put all those perf reminder Sources into specific Appeal(s) you never really look at. You can also set up something to run in the background to close sources per your specifications, so that can help clutter too. (We had it; it stopped running and there's no one to resurrect it for us, but I like to remember it fondly occasionally.) Like Jennifer, I'll advocate for keeping the sources--you have the record of the touchpoint on the constituent record AND you won't have the engagement feedback recorded to Tess without these--but do agree that they don't deliver a ton of value as *sources.* (We do see some transactions off of ours, but won't make any claim that they'll feel relevant to your marketing review of what's driving transactions.)

Jamie

That is a good point, to create a new Appeal that's just for those transactional-type emails. Right now I have all of my emails lumped under "FY22 Emails" but I'm thinking that may not be the best option for perf reminders and post-show emails.

If I can hijack this reply with a question - I'm wondering if you (or anyone!) can share your best tricks for actually reporting on sources. The report for "Revenue by Source and Appeal" is so cumbersome! I really wish there was a way to pull revenue by promotion, but I haven't figured out how to do that. 

Yes, that is my current plan, to corral them into one ignorable appeal, but I genuinely feel like it is a waste of hundreds of source codes per year. Our patrons have only one noticeable response to a performance reminder, which is to exchange tickets. They will frequently not tell our ticket office that they got an email, just that they need to exchange tickets. And as we are going to send the emails regardless of whether they provoke exchanges, I can't see any purpose in tracking them. 

I can see where it would be helpful if tracking contact with patrons was crucial, but for us, it isn't a big concern (at least in this regard). 

I did see your previous posts and found the Triggered Email post particularly helpful, thank you! 

Molly

Tessitura Analytics is a great solution for this! Have you worked with it much? 

The Ticket Office Manager said she didn't choose an appeal and a source was still created. Perhaps it designated one appeal as the 'default' appeal?

Thanks!

Molly