• Replies 4 replies
  • Subscribers 160 subscribers
  • Views 69 views
  • Users 0 members are here
Options
Related

Seeking feedback on a possible new feature

Meaghan Metke
$organization

Hello all!

As I mentioned on our call last week, I am looking for feedback on a suggestion we received to create some sample lists and output sets to include as standard features in Tessitura, similar to what we do with sample HTML templates. We believe this would help new or less experienced users get a feel for how to pull a list, as well as possibly saving time by pre-building some basic lists/output sets that are commonly used - for example, current subscribers/members/donors, un-renewed subscribers/members, ticket holders for tomorrow, subscriber/member info for renewals, membership/subscription info for general communication, membership/subscription info for welcome communication, etc. This also seems like a great way to make the output set recipe book more accessible, as we could build out those recipes as sample output sets, rather than making you all build them from scratch.

As we contemplate adding these sample lists and output sets, I'd love to hear what you all think about the following questions:

  1. It seems to make sense to add these sample lists into a new "Sample" category, so they are easy to find. However, output sets don't have the concept of a category. Would it be helpful to add categories to output sets so they could be bundled or grouped similar to lists?

  2. If we move forward with this, what sample lists and/or output sets would you find most helpful? Don't forget that these could be lists referenced by reports, utilities, pricing rules, etc. or output sets used with an extraction (re-named to segmentations in v16).

  3. Do you think sample extractions/segmentations could be valuable as well? Because of all the data nuances that are so personal to each org, this begins to feel maybe one step too complicated to me...unless we do something like generic sample sets that include commonly used segments for import. For example, basic suppression segments, some of the lists I called out above, etc.
    1. If yes, what sample sets or segments would you find most helpful?

Thank you for your time and thoughts!

Meaghan

  • $organization

    Hi Meaghan,

    First off, I just want to say what a wonderful idea this is. I wish I would have had something like this when I first started in Tess, I feel this could become incredibly useful for so many people.

    My thoughts on your points listed:

    1. This reminds me of Analytics, where Tessitura offers pre-built dashboards you can download and edit to make it your own. If output sets could have categories, I think it makes sense to bundle these "pre-built" output sets together - if not possible, could we categorize them another way? Perhaps simply by naming the output sets with the same first word or number, so that they list alphabetically all together?

    2. I think some of the examples you listed above are really common to a lot of different organizations. I know in my organization, I get asked a lot about subscribers and single ticket buyers and their purchasing habits (ex. STBs how many unique performances have they attended in three past seasons), their geographic location, etc. I'm also starting to get a lot of questions regarding ticket buyers who used specific promo/source codes, so anything along those lines might also be helpful.

    3. Definitely! Extractions are still challenging for me, so having a framework I can work off of would be super helpful! You could definitely start with the basics, honestly anything is helpful to start. I'll have to think on if I have any specific suggestions for sample segments.

    Again, I think this is a fantastic idea! 

  • $organization in reply to Amy Culliford

    Thanks so much, Amy! I really appreciate your feedback.

  • $organization

    Meaghan,

    1) I would love to be able to categorize output sets.  We have so many and they are so messy.  Having sample output sets would also be helpful beyond just the default mailing data.  This might already be a thing in v16, but being able to favorite output sets would also be helpful in this area.

    2) I would include examples of pre-show reminder and post show thank you lists for triggered emails, as well as donor lists with accompanying outputs for last three years of fiscal giving, board list.  So many ideas, but I realize how these are pulled would vary by organization, so it may be that these would need to be tweaked by sysadmin or as part of implementation?

    3) In our org we have a "standard inclusions" and "standard exclusions" extractions that we update regularly.  We use these for importing and are especially helpful for new staff to use as a shopping list when creating an extraction. Within them there are a wide variety of segments and we add more regularly. I realize this is again something that would need to be evaluated by each org.  Perhaps more useful would be including one of each type of common segment.  Some of the ones that new staff struggle with is, using promotion source code and response to suppress people who have already opened or clicked through an email that was sent.  Good luck!  It's a big task to undertake for sure.

  • $organization in reply to Kanani Reichlin

    Ooh! Great ideas, Kanani! We didn't add output set favorites into v16, but I'm totally logging that as an enhancement! Thanks so much for taking the time to respond.