• Replies 4 replies
  • Subscribers 333 subscribers
  • Views 189 views
  • Users 0 members are here
Related

Seeking feedback on a possible new feature

Meaghan Metke
$organization

Hello all! My name is Meaghan and I'm a Business Analyst with the Tessitura Network.

We received a great suggestion 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 get some feedback on 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 in advance for your feedback! It is incredibly helpful to us as we keep working to make Tessitura the best tool it can be.

Meaghan

Parents
  • $organization

    Hi Meaghan, 

    I love this idea and think it would be a valuable resource.

    1. I think output set categories would be great! 
    2. Sample lists/output sets that would be useful:
    -contribution history with date range/campaign/fund output filters
    -membership history and status
    -ticket history with date range/season/production filters
    -email communication preferences with primary email address
    3. I agree that since extractions are more nuanced than lists, samples could be more difficult to craft. But I think a sample that could be helpful are samples for general email blasts or mailings with some common suppressions segments (like no mail, no contact, inactive and deceased records, etc.) and common segments like ticket history and giving history.

    Thanks,
    Michelle

Reply
  • $organization

    Hi Meaghan, 

    I love this idea and think it would be a valuable resource.

    1. I think output set categories would be great! 
    2. Sample lists/output sets that would be useful:
    -contribution history with date range/campaign/fund output filters
    -membership history and status
    -ticket history with date range/season/production filters
    -email communication preferences with primary email address
    3. I agree that since extractions are more nuanced than lists, samples could be more difficult to craft. But I think a sample that could be helpful are samples for general email blasts or mailings with some common suppressions segments (like no mail, no contact, inactive and deceased records, etc.) and common segments like ticket history and giving history.

    Thanks,
    Michelle

Children
No Data