PLEASE let us create bulk acknowledgement conditional acknowledgement letters within NXT without having to do a conditional mail merge outside of the system (much like the old days of RE7 mail)
There are external apps that have this functionality, but it is something that is an essential part of every fundraising organisation's activity (even more so for those who have not yet embraced email acknowledgements). If Blackbaud wants NXT to be a comprehensive solution, organisations should NOT have to pay additional money for bolt-ons, and it should be an integral part of NXT.
We do all our gift acknowledgements through the mail, not email. So, this is important functionality for us.
While I personally appreciate receiving acknowledgments via email, I know many of our donors prefer them in the mail still. It would be nice to be able to generate the letters as we were able to do in RE7.
We onboarded right before the old Microsoft functionality was ripped out of 7, so this would be super helpful to see implemented in NXT. The other posts are right that this functionality is flaunted in front of us every time we open a gift and see the field for Acknowledgement Letter. If it isn't planned, please just remove that option.
Agree with all the comments below - we need the full functionality of database to be in the unified view
This is truly critical functionality, and it’s increasingly embarrassing that Raiser’s Edge NXT still doesn’t support it. Conditional mail merges, bulk acknowledgements, and the ability to generate physical letters directly from the system are standard features in most modern CRMs. They’re not “nice to have”—they’re foundational to donor stewardship and basic fundraising operations.
Maya articulated the core issue perfectly: organizations need to control their acknowledgement templates, use their own merge fields, and generate letters in bulk based on Letter Codes selected during gift entry. That workflow existed for decades in RE7, and it’s still the expectation for any serious fundraising database. Losing that functionality when Microsoft integration ended—and not replacing it in WebView—has created unnecessary manual work and forced nonprofits into third‑party tools just to perform routine tasks.
Quick Letters, Tribute Letters, and Honor/Memorial Letters are also huge losses. Quick Letters in particular were an incredibly efficient way to segment and produce targeted stewardship and solicitation communications. Removing them without a native replacement diminishes the usefulness of the entire platform.
Nonprofits should not have to pay extra for add‑ons to perform the most basic, universal task in fundraising: thanking donors. And as much as I love our Partners and the incredible tools they provide—LetterBox from Red Arc being a great example—we shouldn’t have to purchase an additional product to restore functionality that used to be native to Raiser’s Edge.
If Blackbaud wants NXT to be a comprehensive solution, core acknowledgement workflows must be rebuilt natively in WebView.
Agree with everything others have already so eloquently stated.
I'll just add that in the past, the strength of RE was that it was extremely robust, flexible and offered many functionalities. For all that, it was worth paying a higher price, if an organization could afford it, of course.
As flexibility is being limited in WV and functionalities, such as conditional mail merge, are being removed and users are steered to pay for 3rd party apps to regain functionalities previously native to RE while the cost of RE itself is still rising, many organizations are and will continue to look at and move to alternate systems.
Agreed, many orgs do not exclusively use email acknowledgements. More still send postal acknowledgement letters, including my organization.
This is a standard fundraising task common to all non-profits. A software specifically designed for non-profits should include this natively.
We NEED to be able to send physical acknowledgement letters and Blackbaud should be facilitating this before focussing on additional bells and whistles like AI email. It really should have been worked on straight away when the Microsoft integration ended.
This is considered basic functionality in any other system- we need a robust solution that will accommodate different merge letters, attention to letter code and gift code for conditional content
My organization does not want to AI acknowledgements, and the way those are processed run counter to how we need to create them (in bulk, based on templates that we set, not AI generated letters). In an ideal world, Blackbaud would provide us with the functionality we lost when database view stopped integrating with microsoft products - the ability to create letter templates within RENXT Webview using system merge fields to customize and using the Letter Code (Letter Description) selected during gift entry to choose which letter template is generated and have the merged letters output from RE in word. This also gives you the ability to mark all the gifts for the processed letters as acknowledged.
Bare minimum, I would want the ability we currently have in database view, which is to generate an excel file with all the data we need to generate the merge document ourselves that ALSO marks those gifts as acknowledged once we run the data.
The other thing that is critical to this process is that we be able to manage the Letter Code in RENXT webview. This currently does not exist there. The only place you can access the Letter codes in Raiser's Edge are in Database view > Configuration > Letters. Bare minimum, we need Letters in webview as a code table that we can edit and update so that the letter codes we are able to chose as part of the gift entry process are in line with current needs.
Our gift officers do not have time to create emailed letters one by one in AI Acknowledgements. This has never been a gift officer task. This is a back office bulk task. Our donors expect a hard-copy acknowledgement letter and AI acknowledgements do not fulfil this need or work with our operational processes.
In addition, other parts of the database view mail module are fantastically helpful and are missing entirely from webview. Honor/Memorial Letters, Tribute Letters, and Quick letters come to mind. Quick Letters are especially helpful with segmentation and augment our stewardship and solicitation capabilities. It would be extremely detrimental to Raiser's Edge's overall usefulness to neglect these areas of functionality.
I know some think AI is great, but my organization wants to control the message of in our acknowledgement letters. And "receipting" donors is not really appealing either. We need a to be able to generate acknowledgement letters to send via mail. Thank you.
We need an efficient way to produce our acknowledgements. Removing this function has hindered our process, and I have yet to see a credit for the lack of functionality.
when this functionality was lost to merge acknowledgement letters within RE and have them automatically saved in the gifts, this added to the workload of staff, but was not seen as a credit to the contract.
The majority of charitable donors are over 65 years old (ours are over 80 years old). They respond to mail campaigns and expect mailed receipts. Mailing should be an integral part of the database. If it must be kept separate from RENXT then we should not be expected to pay extra to use the RedArc APP or any other APP. Extra payments should only be for unusual non-standard funtionality.
Yes, acknowledgement of donors is a critical piece of fundraising. It should be a function native to Blackbaud.
I don't understand how this key part of donor communication and advancement work can be missing from the RE software.
It's one of the strikes when we start looking for other CRMs.
It boggles the mind that Blackbaud has made something so difficult for their nonprofit customers.
What do we do? We solicit donations and thank people / organizations when they make them.
This is SO critical to the work we do, and has never been easily configured in Raiser's Edge. Making it easy to enter these donations and thank people are priorities.
Yes, as this is a standard fundraising-related task, it should be a standard function of a fundraising software and not require third-party plugins or extracting data to work with outside the system. My goal is to keep donor/gift data contained and secure within the system if at all possible, so pulling it out to do merge letters is counterintuitive and contrary to that goal.