A member calls to ask whether their card will be charged next month. The person who answers opens the constituent record, sees an active membership and an expiration date, and still can’t say for sure whether that membership is set to renew on its own. They put the caller on hold and go digging. That’s the problem worth solving: auto-renewal status exists in Altru, but it usually isn’t sitting where frontline staff look first.
Where the information actually lives
In Altru, auto-renewal is a property of the membership, not of the constituent. The constituent record shows that a person has a membership, but the details that matter for renewal (the level, the term, the expiration date, and whether the membership is set up to renew automatically with a stored payment method) live on the membership record itself.
So the honest short answer is: open the membership from the constituent record and look there. How prominently the auto-renew setting shows on that page, and whether it appears on the constituent summary at all, can depend on your Altru version and how your pages are configured. If you aren’t sure, check one known auto-renewing member in your system and note exactly where the setting shows up, then turn that into a one-line instruction for staff.
Why it gets missed
- It’s one click deeper than people look. Desk and phone staff tend to read the constituent summary and stop. If auto-renew isn’t visible there, they assume it’s off or guess.
- Households complicate it. The person calling may not be the constituent the membership is recorded under. Staff search the caller, find no membership, and give the wrong answer.
- Payment status and renewal status are different things. A membership can be flagged to auto-renew while the card on file has expired. Staff see “auto-renew” and promise a renewal that will actually fail.
Ways to make it visible to staff
None of these require anything outside Altru. Pick the ones that fit how your team works.
1. Add a visible flag on the constituent
Many organizations create a constituent attribute (for example, “Membership auto-renew: Yes”) or add a note on the record, so the flag shows where staff already look. (Which of these displays most prominently on the constituent page depends on your configuration, so test with one record first.) The catch is that an attribute you set by hand will drift out of sync when members opt in or out. If you go this route, assign an owner and refresh it on a schedule from a query, rather than relying on staff to update it one record at a time.
2. Build a membership query staff can run
Create a membership query that returns active memberships with the auto-renew setting, expiration date, and the primary member’s name and household. Before you build it, confirm in your query designer that the auto-renew field is exposed in your membership view; if you can’t find it, Blackbaud support can tell you which view holds it. Save it as a shared query so the membership team can answer “is this person on auto-renew?” in seconds, and so you can spot accounts likely to fail.
3. Check card expirations alongside auto-renew
Add the stored payment method’s expiration to the same query if your data model allows it, or run a separate check. Members whose cards expire before their next renewal date are the ones who will lapse without meaning to. Reach out to them a few weeks early.
4. Consider a smart field
If your team uses smart fields for membership data, see whether one can surface auto-renew status at the constituent level so it can be used in lists and reports. Test in a sandbox first; smart fields that summarize membership data can behave unexpectedly for households with more than one membership.
5. Write a short desk script
Even with better visibility, give staff three steps for renewal calls: find the household (not just the caller), open the active membership, and check both the auto-renew setting and the card on file before answering. Tape it near the phones.
Keep the record and the member’s view in agreement
Visibility for staff solves half the problem. The other half is the member’s own understanding. If renewal reminders and acknowledgment letters state clearly whether a membership will renew automatically, and on what date, fewer people call to ask. Review your renewal letter or email templates and make sure the auto-renew language comes from the same data staff are looking at, not from a generic paragraph.
Quick answers
Is auto-renewal set on the constituent or the membership?
On the membership. The constituent record links to it, so staff usually need to open the membership to see the setting.
Can I make auto-renew show on the constituent summary?
Possibly, depending on your version and page configuration. If it can’t be shown natively, a constituent attribute kept in sync from a query is the dependable workaround.
How do I find auto-renew members whose cards will fail?
Run a membership query that includes the auto-renew setting and the stored payment method’s expiration, then compare that date against each membership’s expiration.
