Managing Contact Preferences

Sherry Aldrich

I'm wondering how others manage the various ways your constituents want to be contacted. Do you keep track if they only want emails, no phone calls and all the other variations. Do you use RE / NXT? The solicit codes seems to be the correct field, but I'm wondering about your process and tracking. All or nothing doesnt really work. There are people who don't want to be called but would love a visit. Or don't mind mail appeals but don't want to be called.

Using the email tools in RE/NXT if someone unsubscribes, I believe they are automatically removed from all communications.

Sharing any thoughts or processes would be greatly appreciated.

JoAnn Strommen

@Sherry Aldrich What I inherited is a mix. We have some preferences/consents in solicit codes, a few in consents and others in constituent attributes as well as some use of the ‘requests no email’ on bio1.

While solicit codes are front and center there is no place for dates or details. In attributes we can record “no phonathon calls," a date and notes about how we got the info. We use solicit code of “Never Solicit” that is used when pulling lists for mail, calls, or any type of ask. And we have folks coded for ‘no mail solicitations’ who we can call or email.

Am definitely not a fan of records getting marked ‘no email’ automatically as there are so many different types for us.

I would try to stay with “no” format. So for someone who only wants email, they would be coded as 'no mail/no phone asks/etc. IMO it makes querying easier to pull all the exclusions - criteria not one of….

Dan Snyder

@Sherry Aldrich I would just add to @JoAnn Strommen's comments to look at the consent module to track this information. You can include a reason why a code was added and set up business rules to add or remove the solicit codes for you.

It takes a bit of setup but in my opinion is well worth it and I know they are looking to make the process easier as outlined by @Chris Ager at #BBCON 2024