Hello,
We are working on integrating WordFly and are having some problems. I am trying to provide Tessitura support to the Marketing department, but we're having a breakdown in communication because they don't know what they need to ask for so I don't know what to provide them. Basically, we need to know how to pull data fields such as performance name/date/time for performance reminders, at least as a first step.
Also, I am LOATHE to have WordFly create a new source for every single performance reminder. Has anyone found a work-around for that? I really don't want 250+ sources created that will never be used.
Thanks!Molly
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
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