Contact type advise

Options

We are wanting to clean up our contact types. If you have a contact that falls in to more that one contact type category how would you handle this. For example John Smith is both a food drive contact and a grant contact. We are currently creating two relationship records. Is there a better way?

Comments

  • JoAnn Strommen
    JoAnn Strommen ✭✭✭✭✭
    Ancient Membership Facilitator 4 Name Dropper Photogenic

    @Monica Curl Great question. I wish there were a better way but I don't know that there is.

    We have been contemplating adding a second relationship to track who receives the scholarship thank you letter from student as sometimes it's primary and other times not. Makes pulling data into new scholarship manager software a real challenge.

    Will be interested to see what others say, especially those that do use second relationships.

  • @Monica Curl A way that I've done this in the past was to have a contact type called ‘See Attribute’ and store extra contact types as attributes. This allows you to have as many contact types as you want against the one relationship. I haven't done it in a while but I think it creates complications with export, like trying to get out a specific contact type stored as an attribute. Because it can get quite complicated, it's workable if your relationships are being managed by the database team, but pretty hard to enforce if it's open to a wider set of users.

  • Karen Diener 2
    Karen Diener 2 ✭✭✭✭✭
    Ancient Membership Facilitator 3 Name Dropper Photogenic

    @Monica Curl I will start by saying that I've never worked with an organization that has this figured out. The coding is less of an issue than knowing who the correct person is though!

    I think Attributes, as Brian suggested, is the best option. I don't think you need to add a “see attributes" contact type though. Your organization's policy simply becomes “we don't use contact type - we define those details on the Contact Attributes tab”. But one contact can have multiple attributes and it works just fine.

    When using any of the functions in the Mail section of RE, you can specify the contact attributes on the Org Address tab. Skip the top checkbox to include selected contact types only, but click the button to specify which contact attributes to include:

    2c47231cfec782e143100cc5260af89d-huge-im

    In Export, you will have a similar screen available to filter contacts, but only if you select “Address Processing” from the Address node:

    140a3398d8dd705020ccc2c845242f14-huge-im

    Either of the above should ultimately provide one row per contact in your final mailing list. If you uncheck that box (named “print one for each contact found” in Mail, vs. “Export one record for each contact found” in Export) you will get only one row for the organization. I forget the hierarchy it will use to select the contact if multiple meet your filtered criteria, but I believe that can be found in the knowledgebase if needed.

    Karen

  • @Monica Curl we only use Contact Types for Solicitor Types, for the most part. If contacts on a record have 2 (or more) contact types for that relationship, like in your example, we use Attributes.

Categories