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

Do Not Share Request coding

Former Member
Former Member $organization

While we have a practice of not sharing constituent contact lists from our database, there are times when we might want to provide a specific constituent list to a close alliance for our own purposes.  In a recent list share, we extracted all who have no mail and no contact codes in the constituent field of mailing restriction from the list.  Since the three restriction fields (mail, phone and email) only allow one code entry, I am trying to figure out how to ensure that those who both do not want any postal mail from us as well as do not want their contact ever shared to be coded.  

Do any of you track specific requests for Do Not Share Contact Info separately from these three restriction fields? If so, where?  How do you handle restrictions that extend beyond the capacity of the three fields on the general tab of the constituent record?

Thank you. Laura

Parents
  • $organization
    We now have a firm no trade/share policy. However, we also use attributes to track all our mailing purposes, because three options just isn't enough. One of our options for mailings has been "do not trade" - that would be what we would exclude if we were doing a trade in the past. We also marked that attribute on anyone who requested that they be removed from all our mailing lists, just as a courtesy.

    Beth Varro
    Science Museum of Minnesota


    *   *   *   *   *
    How do astronauts get to space? How do they eat, sleep, and do research in a weightless environment? And how do they go to the bathroom? Find out during an unforgettable day of space exploration at the world premiere Space exhibition. It's now open at the Science Museum of Minnesota, along with the brand new Omnitheater film, Journey to Space. Visit www.smm.org/space to plan your visit today!

    From: "Laura Chaney" <bounce-laurachaney2031@tessituranetwork.com>
    To: evarro@smm.org
    Sent: Thursday, July 23, 2015 12:22:15 PM
    Subject: [Tessitura Development Forum] Do Not Share Request coding

    While we have a practice of not sharing constituent contact lists from our database, there are times when we might want to provide a specific constituent list to a close alliance for our own purposes.  In a recent list share, we extracted all who have no mail and no contact codes in the constituent field of mailing restriction from the list.  Since the three restriction fields (mail, phone and email) only allow one code entry, I am trying to figure out how to ensure that those who both do not want any postal mail from us as well as do not want their contact ever shared to be coded.  

    Do any of you track specific requests for Do Not Share Contact Info separately from these three restriction fields? If so, where?  How do you handle restrictions that extend beyond the capacity of the three fields on the general tab of the constituent record?

    Thank you. Laura




    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
    We now have a firm no trade/share policy. However, we also use attributes to track all our mailing purposes, because three options just isn't enough. One of our options for mailings has been "do not trade" - that would be what we would exclude if we were doing a trade in the past. We also marked that attribute on anyone who requested that they be removed from all our mailing lists, just as a courtesy.

    Beth Varro
    Science Museum of Minnesota


    *   *   *   *   *
    How do astronauts get to space? How do they eat, sleep, and do research in a weightless environment? And how do they go to the bathroom? Find out during an unforgettable day of space exploration at the world premiere Space exhibition. It's now open at the Science Museum of Minnesota, along with the brand new Omnitheater film, Journey to Space. Visit www.smm.org/space to plan your visit today!

    From: "Laura Chaney" <bounce-laurachaney2031@tessituranetwork.com>
    To: evarro@smm.org
    Sent: Thursday, July 23, 2015 12:22:15 PM
    Subject: [Tessitura Development Forum] Do Not Share Request coding

    While we have a practice of not sharing constituent contact lists from our database, there are times when we might want to provide a specific constituent list to a close alliance for our own purposes.  In a recent list share, we extracted all who have no mail and no contact codes in the constituent field of mailing restriction from the list.  Since the three restriction fields (mail, phone and email) only allow one code entry, I am trying to figure out how to ensure that those who both do not want any postal mail from us as well as do not want their contact ever shared to be coded.  

    Do any of you track specific requests for Do Not Share Contact Info separately from these three restriction fields? If so, where?  How do you handle restrictions that extend beyond the capacity of the three fields on the general tab of the constituent record?

    Thank you. Laura




    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