• Replies 10 replies
  • Subscribers 413 subscribers
  • Views 92 views
  • Users 0 members are here
Related

Constituencies

Former Member
Former Member $organization

We are in the process of trying to clean up our records, including attributes and constituencies. In doing this, we've realized our constituencies tend to be repetitive with information found in other places in a Tess record. Out of curiosity --

What do you have constituencies for and why?

Does it seem like better practice to track your prospects for foundation, gov, individual, etc. in a solicitation rather than a constituency?

Thanks!

Parents
  • $organization

    I concur.  One nice thing about constituencies is that during gift entry/ticket purchase the staff member can see the constituency such as a board member, when processing a transaction.  Another useful item is that when I use the output set and pull constituencies, those that are on an individual account, like board member, are included when pulling the household accounts.

     

    For solicitations, we have the Flex header set to show the latest solicitation in the header. 

     

    T.C. Brown

    Database Administrator

    412.392.4834

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Marta Garczarczyk
    Sent: Thursday, April 11, 2013 2:41 PM
    To: TC Brown
    Subject: Re: [Tessitura Development Forum] Constituencies

     

    I agree with what everyone has already said. The other thing that constituencies can be really useful for are pulling quick lists. If you have a constituency that gets assigned to everyone that is an active subscriber than it's really easy to pull a list just based on that constituency of "Sub" for example. In addition to the quick glance header functionality I think that's the other advantage of various constituencies. 

    And yes, solicitations are the best place to manage all of your prospect information. You could put it in constituencies as well if it was helpful for you in the header. 

    From: Sara Fellman <bounce-sarafellman8179@tessituranetwork.com>
    Sent: 4/11/2013 12:04:51 PM

    We are in the process of trying to clean up our records, including attributes and constituencies. In doing this, we've realized our constituencies tend to be repetitive with information found in other places in a Tess record. Out of curiosity --

    What do you have constituencies for and why?

    Does it seem like better practice to track your prospects for foundation, gov, individual, etc. in a solicitation rather than a constituency?

    Thanks!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!

Reply
  • $organization

    I concur.  One nice thing about constituencies is that during gift entry/ticket purchase the staff member can see the constituency such as a board member, when processing a transaction.  Another useful item is that when I use the output set and pull constituencies, those that are on an individual account, like board member, are included when pulling the household accounts.

     

    For solicitations, we have the Flex header set to show the latest solicitation in the header. 

     

    T.C. Brown

    Database Administrator

    412.392.4834

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Marta Garczarczyk
    Sent: Thursday, April 11, 2013 2:41 PM
    To: TC Brown
    Subject: Re: [Tessitura Development Forum] Constituencies

     

    I agree with what everyone has already said. The other thing that constituencies can be really useful for are pulling quick lists. If you have a constituency that gets assigned to everyone that is an active subscriber than it's really easy to pull a list just based on that constituency of "Sub" for example. In addition to the quick glance header functionality I think that's the other advantage of various constituencies. 

    And yes, solicitations are the best place to manage all of your prospect information. You could put it in constituencies as well if it was helpful for you in the header. 

    From: Sara Fellman <bounce-sarafellman8179@tessituranetwork.com>
    Sent: 4/11/2013 12:04:51 PM

    We are in the process of trying to clean up our records, including attributes and constituencies. In doing this, we've realized our constituencies tend to be repetitive with information found in other places in a Tess record. Out of curiosity --

    What do you have constituencies for and why?

    Does it seem like better practice to track your prospects for foundation, gov, individual, etc. in a solicitation rather than a constituency?

    Thanks!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!

Children
No Data