Using Consents vs. Positive/Negative Solicit Codes
For those who use consents in conjunction with solicit codes, what's the benefit to consents and business rules, rather than just directly assigning positive and negative solicit codes and bypassing consents completely? My company has been using solicit codes on their own, and are considering moving to consents instead. Trying to weigh the pros and cons. Thank you!
Comments
-
@Lissa Wengronowitz I like the ability to have the reason right there to read why a code was given is the biggest plus I can see. Prior to consent we would also add an action when many of our solicit codes were added.
You can also easily see which codes were added at the constituents request vs. an internal decision depending on how you set it up.
You don't need to have the positive and negative for all - you can simply build it so that if someone say opts back in it removes the do not send ______ code or however your solicit codes were set up. Hope that is clear - I may be a little tired.
3 -
@Lissa Wengronowitz
We used default sets to add an Attribute timestamp with dd/mm/yyyy to record when the solicit codes were added, attribute types/categories communicated which area they were added from. We used notes to update solicit codes, like 'Never contact', were added with an explanation.All that was replaced by consent. I agree with Elizabeth that consent is easier to record, source, timestamp and opt-in and opt-out. we used an exclusion model, but now we might be moving to an inclusion only model. Has anyone seen on of those?
3 -
@Lissa Wengronowitz 100% agree with @Elizabeth Johnson. It really can become a streamlining of the process.
2 -
@Tracy Wadlow What a great question and now I'm curious:
- If anyone replies that they have seen a system where it is just opt-in.
- Why you would want to make that change to only opt-in.
- And most importantly the timing of that potential change. I think it is safe to say we can expect a lot of changes in the system over the next 13 months. In the database view certain functions only exclude solicit codes. Of course, one can query around it. If it was me I'd wait and see what the web view has in store for us as they build out the complete system. At bbcon there were some (dare I say exciting) announcements around consent.
1
Categories
- All Categories
- 6 Blackbaud Community Help
- 209 bbcon®
- 1.4K Blackbaud Altru®
- 395 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.5K Blackbaud Financial Edge NXT®
- 648 Blackbaud Grantmaking™
- 567 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 937 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.5K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 247 ResearchPoint™
- 118 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 239 The Tap (Just for Fun)
- 33 Blackbaud Community Challenges
- 31 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 782 Community News
- 2.9K Jobs Board
- 53 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)


