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
  • 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. 

Reply
  • 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. 

Children
No Data