JT
My feedback
13 results found
-
23 votesJT supported this idea ·
-
74 votes
An error occurred while saving the comment JT supported this idea · -
11 votesJT supported this idea ·
-
60 votesJT supported this idea ·
-
86 votesJT supported this idea ·
-
143 votesJT supported this idea ·
-
215 votes
An error occurred while saving the comment JT commentedThis would help immensely.
JT supported this idea ·An error occurred while saving the comment JT commentedIt would be great to have fields in event registrations that are only available to members.. We often have $ add-on options that are only available to members, which means members have to call in and we manually add the additional fees.
-
239 votesJT supported this idea ·
-
240 votesJT supported this idea ·
-
366 votes
We're considering to take Donations during registrations/applications into development right now, but during analysis of the feature we ran into an issue where we would love to hear your feedback.
Essense of question: how would you like donations during applications or registration to be processed for offline payments (when your member/prospect decided to get an invoice and pay later)?
Some more details:
We can implement donations during event registrations/membership renewals for online payments - not a problem.
But when we're talking about offline payments, straighforward solution seems to be a bit expensive - we don't have invoices for donations or pledges yet.
So right now we're considering going on with straighforward online payments solution (donation will be added to payment transaction) and for offline payments - just include an invoice memo to buyer to add $XXX to his payment as donation for event/membership he has selected.
This way administrators would…
JT supported this idea · -
15 votesJT supported this idea ·
-
93 votesJT supported this idea ·
-
250 votesJT supported this idea ·
This would be incredibly helpful.. We are currently looking to have our other branches use wildapricot.
Ideally, for us, having each chapter manage payments and events, but share membership database information, so that members(or database managers) have to manually make a new login for each branch site.
For example, we have one main branch and put on many events each year, currently we have a hidden membership level to which we manually upload "other branch" member information so they are able to take advantage of online member perks.
It would also be wonderful to have main branch database managers be able pull reports from the organization as a whole.
I hope this goes forward soon!
Any updates from WA's end on this topic?