Just started using Mail in RENXT and was shocked that Salutation wasn't a merge field. Even more shocked to see that we're in "voting open" phase for the dire need for more merge fields that was originally requested TWELVE years ago! Seeing as the big draw for us to use Mail is having it as part of a workflow, the inability to correctly personalize these is a huge issue.

Requesting last gift field in mail tab. URGENT need for mailings needing gift arrays based on last gift amount. How have others been pulling clean mailings all this time with gift information included? It's simply not possible.

Tribute First and Last Name would be helpful to have as options to include. When we thank a donor for a tribute gift we like to include who they made the gift in honour or memory of.

Yes! Set up as is, mail is much more convoluted than it needs to be.

Long overdue. We need to have benefit information available to move to eReceipting.

At least offering the same fields as available in donor acknowledgements would help us.

Long overdue

Changing the status of this idea to Voting Open because it's been reviewed. While not currently planned, this will remain open for voting and future consideration as a change.

Please note that this only represents expanding the list of available fields within mail functions, and doesn't reflect any other changes to the mailing process. If other changes are desired outside of additional fields outside of making the fields from Export available in Mail, please create separate suggestions for those.

For all the reasons already listed, this would be incredibly useful. Currently limited by the fields available with no way to add more. This list has started to dictate how we put our TY letters together. Very uncreative way of working. Please consider full field list.

AGREED! I'm looking to very simply add the field FUND to an email gift acknowledgement in Online Express. It seems silly that even very basic fields aren't available for to use in merges. This seems like such an easy fix. WHY IS THIS 8 YEARS OLD AND STILL NOT ADDRESSED?!

Making event information would greatly help. example of usage: "Thank you attending {Event Name} on {event date} at {event location}." Your gift of {amount} for {number of units} {unit description] is greatly appreciated. {receipt amount} of your gift is tax deductible."

Yes!  Event participant attributes would be so helpful for acknowledgement letters.

I can’t believe this has not even been addressed in over 7 years! No unique Gift ID field available for mail merge! I’m just at a loss for words (no pun intended).

I agree. The Mail module should incorporate more data fields such as the stock issuers name, median price, total value, value at the time of sale, issuer symbol etc. It would also help if data fields such as the first gift date are available to include in the letter. Currently that's a limitation in RE. I hope the next edition supports this.

Phone and email fields please in RE> Mail> Quick letters. We would like to create segmented emails in the same way we create segmented mailing lists. Many thanks

I need donor email address AND phone number printed on Honour/Memorial acknowledgment cards

It's somewhat disheartening that this still hasn't been addressed by Blackbaud. You can't list the Benefits or their count like you can in Export, are extremely limited in what you can include from a Tribute's record, can't include any of the stock information that Export readily supplies.

How hard is it exactly to allow these fields that this still hasn't been fixed more than 5 years later?

I need more summary fields available in "Fields to include" in the Donor Acknowledgment Letter." We like to communicate with our donors what they have given in 2017 (so far), 2016, and 2015 separately. Currently I can only tell them what they've given YTD this calendar year, fiscal year, or from specific date. 

I need the Letter conditional field to be available when choosing "per donor" on the Fields to include tab of Donor Acknowledgment Letters.  We have donors that give multiple checks on the same day all receiving the same letter code and we need that to roll up into one letter instead of 35-50 that we then have to manually edit.

This same issue used to have over 2,000 votes, and the votes and most of the comments then disappeared. The core problem is RE's silo-based file structure, rather than being a true relational database. We can capture all of the detailed info imaginable, we just cannot use it. The 'Emperor's New Clothes' syndrome - for those who understand the file structure well enough to handle work-arounds and unbelievably complex queries, it is job security. For the rest it is constant pressure from above to get basic functionality out of a  relatively expensive software package that boasts of bells-and-whistles when it can't deliver on basics. RE is designed to archive data, not to use it.

I agree, I have just been trying to set up a number of letters but unable to select the fields required so have had to set these up through Export instead.