Flaging Patrons w/out Development Module

You could create an attribute or constituency that tracks those patrons. That’s an easy solution and then easy to pull lists as well.

Christopher Cuhel | Database Coordinator

The 5th Avenue Theatre

1308 5th Avenue Theatre, Seattle WA  98101

p 206.971.7916 f 206.292.9610

Seattle's Acclaimed Non-Profit Musical Theater Company

Website |  Facebook |  Twitter |  Youtube

Hello

I need to flag patrons that are entered as a result of forms being filled out. We do not have the development piece of Tessitura that offers these options.  We're also in a consortium and don't have the ability to customize.

I can use original source but eventually, that will get very full with multiple labels.  I thought of Patron Source or a Temporary List Keyword but we don't have that option open to us.

Has anyone else worked around this?

Thank you!

Michelle

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

I completely understand not wanting to have constituency codes littering the header. Your other option is to create an activity for this tracking. The nice thing about using activities is if the patron left any comments on the form, there is a notes field you can use to enter that information.

Hopefully you are given full access to Tessitura soon. There are so many things you can do with full access.

Christopher Cuhel | Database Coordinator

The 5th Avenue Theatre

1308 5th Avenue Theatre, Seattle WA  98101

p 206.971.7916 f 206.292.9610

Seattle's Acclaimed Non-Profit Musical Theater Company

Website |  Facebook |  Twitter |  Youtube

Thank you Christopher!

I'm a fan of constituent codes but have a concern the header will become littered with them.  The attribute is a great idea.  I currently use attributes to flag prospects for development. They provide a good work around for identification until we get on board with the development module.