As we review our membership functionality for the v16 membership overhaul, we have a couple of questions around the pledge suspend and cancel functionality.
First, is the status Awaiting Payment important or useful to you? If so, how do you use it? Unless I’m missing something, there doesn’t seem to be much distinction in the way the system acts between an Awaiting Payment membership and one that is in Upgrade status.
What about suspended? It seems like this would be useful for pulling lists of people to remind about paying their pledge. Do you use it for that purpose? Is there anything else this status signifies to you or that you use it for? It also seems like there is a disconnect between how it is named and what it does, in that a Suspended membership still shows up as active. We have changed the field name in membership level setup to Pledge Warn. Would a better name for the status be “Warned”? “Pledge Warn”? “On Notice”? Something else?
Thanks,
Mark Rhodes
Business Analyst
Tessitura Network
Hi Mark,
In my organization (Museum of Science, Boston), we currently use “Awaiting Payment” on memberships when the membership is linked to a pledge that has not been fully paid off. If “Awaiting Payment” will be eliminated as a status in v.16, how will we be able to identify and track these membership situations?
We have not used "suspended" as a membership status.
We've also seen the error message that Rachel Stone identified, usually when trying to add a standalone membership to a record that already has a current one. I agree that it would be ideal if this issue could be corrected in v.16!
Katie