Difference between Requests No Emails tick & Solicit code Do Not email
Hi. I am relatively new to RE, and was wondering whether there is a difference between using the tick box Requests No Emails and adding a solicit code to the ‘Consent’ module Do Not Email? Which do you use and why?
Comments
-
@Lena Payne - This is what's fun about RE, there are lots of ways to do the same thing it just depends on your internal processes for which makes the most sense. If you already have a process built around tracking opt-outs through Consent/Solicit Codes, I'd go that route.
For most orgs I've worked with, they've used both interchangeably. One thing to note, the system/NXT email marketing will add a consent record when someone opts-out you can set that up on the back-end to automatically apply a ‘Do Not Email’ solicit code to the constituent.3 -
@Lena Payne I agree with @Austen Brown here. I use both pretty interchangeably. They both have different visibility so in this case I think using both might work well. What is a simple checkbox in database view is a blue bubble in the constituent header in web view. Conversely, solicit codes can get very lost in web view, as opposed to their location in database view.
2 -
@Dariel Dixon and @Austen Brown I don't use NXT email, but would the checkbox prevent email from being sent to that constituent?
1 -
@Lena Payne I will use solicit codes and the No Email checkbox in tandem - the checkbox will ensure they don't get email, where the solicit codes have to be included/excluded from a mailing list manually. One quick FYI in case it's new to any readers: if you are using Solicit Codes and want them to be highlighted at the top of a Web View constituent, click on the cogwheel by solicit codes and pick the ones you want highlighted if they are used. Editing to add: I am a big advocate of using solicit codes via Consent because it gives us the “why.”
4 -
@Lena Payne Welcome! First I would verify if there is any documentation on how your org has used this in the past. At my org, we consider the “Requests not email” as Requests no Bulk email, and sending a very personalized individual email is fine unless that email address has the Do not contact (dnc) icon next to it.
Like @Aldera Chisholm we use them in tandem.You have some seriously sage advice going on in this thread!
0
Categories
- All Categories
- 6 Blackbaud Community Help
- 213 bbcon®
- 1.4K Blackbaud Altru®
- 401 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.6K Blackbaud Financial Edge NXT®
- 655 Blackbaud Grantmaking™
- 576 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 939 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.6K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 248 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 241 Member Lounge (Just for Fun)
- 34 Blackbaud Community Challenges
- 34 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Chat for Blackbaud AI
- 3 (Closed) 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
- 791 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)




