Totally agree with you - we do the same. We have a very complex mail merge template that pulls letters in based on what the letter code of the gift is, and it's also on legal sized paper. It allows us to get specific based on the appeal they responded to, and we can add stock details and such. We also have an older demographic and always mail receipts by default. If database view is sunsetting next year, this needs to be a functionality instead of having to rely on NXT's e-receipting.

Also, I forgot to mention in my Aug 19 comment below, that bringing the Mail function into web view will also allow something MUCH NEEDED by my organization and that is eReceipting $0.00 gifts -- We issue many Complimentary Memberships using a $0.00 gift and using the eReceipt function to send recipients all their Membership information. AND I wanted to show you a sample of the VERY DETAILED eReceipt we currently send using the datbase view Mail function, see this attached. So yes I fully believe that Mail functionality is needed in web view. Thank you.

I agree 100%. Being reliant on email is not practical nor sustainable for my org. its frustrating that this was changed and I'm hoping that this can be amended. the lack of consideration of users getting a bit ridiculous... not sure if the intention is to save money or something, but whatever it is, think about the people and orgs who are using NXT before you make changes like this.

Blackbaud has gone way backwards in eReceipting functionality in this move from Database view to NXT -- The eReceipting functionality is NXT is ridiculously basic and to be honest this major lack of function and lack of ability to personalize and put graphics, etc. into eReceipts could make the difference in whether my org' stays with Blackbaud or moves to Bloomerang. We use the eReceipting function in Database view several times a week to send DETAILED eReceipts, with several different graphics of how to download your Membership eCard onto your phone etc. etc., so much more functionality is needed, so yes I agree, Mail functionality is absolutely needed in web view. Thank you.

We use the Mail functionality to generate gift-acknowledgements and tax receipts daily. We export the .csv with the gifts and do a mail merge in Word. This allows us to have customized letters for each of our fundraisers and appeals. We do not use email for these. We could potentially use emailed acknowledgements and receipts if it were possible to have a form letter that would pull in specific merge fields. The AI generated emails that require review for every gift is not something we find helpful. We know what we want our letters to say and we don't need anything generated by AI, we just need dynamic merge fields that will populate based on logic we set up, like we do with our mail merge in Word. We print our letters on our own letterhead, so we need to be able to customize the entire letter, not just specific data that gets merged.

Also agree. Our organization uses it for acknowledgement and tribute letters. It's a must. Weekly use in our shop.

Database "Mail" functionality is absolutely needed in web view! Our organization uses it 3 - 5 times per week to create donor acknowledgement letters and other mailings.

Like poster Jenn L, the majority of donors at our org are an older demographic who prefer print mailings and communications. Email is not the solution for everyone.