Best Of

When people give online, they are used to getting a confirmation email, so use that space to make it a good interaction. For this automatic email reply when they do an NXT form I:

1. Redirect them back to our website instead of the default content. Land them on a page that has some impact stories, newsletter, whatever works for you.
2. The thank you email that goes out automatically: I keep it short, but ensure that it includes basic transaction info, a short thank you statement that is relevant to the specific form they used, who they can reach out to if they have questions, and letting them know what to expect next, whether that is follow up information on event tickets or your tax receipt will follow, etc.
3. Ensure you cc yourself on the notification (even if you filter notifications to a sub-category in your inbox)

Once you approve the batch in NXT, the Email and Receipt goes out. I like a short heartfelt thanks, affirm their giving decision by letting them know the impact it has, give them an opportunity to engage with a real person by name and direct phone number. Same basics as the initial email, but a little bit more detail. I aim to do this as soon as you can within your team's process rules.

After that? Do you want to subscribe them to an email welcome series - there are some great articles on here about how to do that. Do you follow up on some or all gifts with a phone call? Use a workflow to automate adding an action to assign that call to happen.

There are a million different opinions on content, timing, etc, but we all know retaining donors is the hard part so it's worth taking the time to get this right.

Austen, yes. I accidently looked at the calendar wrong. It is Monday, November 3. I'll send out the link soon for everyone. It'll be mid-late central time zone to help accommodate as many people as possible.

Thanks Austen, that sounds like a good way to address it. We did just hear from someone on the APRA forums who says the integration doesn't work all that well so if that's the case I'm not going to bother with it.

Hello! I am new here and would like to know how experienced pros deliver the chain of thank you email > receipt > acknowledgement.

From what I can tell, the thank you email goes first and is an auto response to a gift. Then once I've batched the gifts, I can send a receipt and an acknowledgement.

What is the best practice for making all these emails effective (do you even use them all)?

I think I would like to use them, partly just because I hate seeing things left sitting in the unacknowledged list and it seems like a good opportunity to check back in with a donor, but it clearly does not need to be the same message going out several times.

Would anyone be willing to share an example of how you use each of these, what content you include, and what your timing looks like in sending them out?

I thought this was going to be easy. We have 10 people coded with a "Board Member" constituency code. I recently change to the "To Date" to one of them to 6/30/25. Today is 9/19/25.

I then created a Constituent List that looks for everyone with a Constituency Code of "Board Member" and the "As Of" date of Today (9/19/25)… And the expired/ended member still appears in the constituent list.

Is there a delay? Is there some other simple way around this? Do Constituent Codes just not work? I feel like I'm missing something super simple.

It's not actually inconsistent. Query won't let you paste in a set of values if the field you want to paste in is a table field. So, Fund IDs and Appeal IDs are a table field and you have to select them from a list. Constituent IDs are a fill-in field so you can paste in those values. For me, the real issue is that the UX in webview for choosing your one-of fields is so laborious (if you have 400+ Fund IDs like us, you end up having to click "load more" more than 30 times to get to all your values) that it makes it very difficult to do what was a fairly simple task in database view.

I created an Idea in the Idea Bank to adjust the UX to make this type of process more functional. Please consider voting for it!

https://renxt.ideas.aha.io/ideas/RENXT-I-7542