Jeff
My feedback
19 results found
-
15 votes
-
208 votes
-
13 votes
Frank
responded
Sounds interesting, collecting comments.
An error occurred while saving the comment Jeff
supported this idea
·
-
66 votesJeff
supported this idea
·
-
61 votesJeff
supported this idea
·
An error occurred while saving the comment Jeff
commented
Bundle billing is a problem. You need to implement variable billing based upon the number of members in a bundle. I have a number of government agencies and organizations that love the ability to manage their own bundle, but don't want a flat rate for the whole bundle. They feel a real need to have their bill tied directly to the number of members in their bundle.
-
18 votesJeff
supported this idea
·
-
47 votes
Team Payments
responded
Due to priorities shift we had to put this issue on hold.
We’ll post any updates as we have themOleg, Product Owner @ Payments crew
Jeff
supported this idea
·
-
104 votesJeff
supported this idea
·
-
2 votesJeff
shared this idea
·
-
101 votesJeff
supported this idea
·
-
73 votes
Evgeny Zaritovskiy
responded
Current proposal: https://drive.google.com/file/d/0B0f9kMyQqlBsV1UzVVYwS21ZU28/view?usp=sharing
We do not have plans yet on when we’re going to deliver on this.
Jeff
supported this idea
·
-
203 votesJeff
supported this idea
·
-
43 votesJeff
supported this idea
·
Jeff
shared this idea
·
-
37 votesEvgeny Zaritovskiy
responded
For now, this is not something we’re going to change – not sure if ever.
Workaround to use: create a special “entry” free level to apply to, and close “normal” ones for application. For the entry level, create also a dropdown field where a potential member can choose a level they want to apply to. Add other fields you need to assess the application. When application is successful, your admin is to change membership level to required one and generate membership invoice (membership upgrade invoice). The member will be emailed with the invoice and can pay.An error occurred while saving the comment Jeff
commented
I have worked around this by creating a "member level" called "member applicant" with no cost and another called "member-probationary". It still doesn't really do the trick, because I would like to have a button that I can select when the administrator upgrades an "applicant" or "probationary" to full membership and send the bill at that time. As it is now, you bill them as soon as they fill out an application for a membership that has a price, and you don't automatically bill if an administrator upgrades them from "applicant" to "full member".
An error occurred while saving the comment Jeff
commented
We have a waiting list for members to join. We want them to sign up on the waiting list, but not get an invoice for membership dues and fees until they clear the waiting list. It would be nice to have a "delay billing until <condition> is met" feature, with ability to have more than one <condition>.
Jeff
supported this idea
·
-
120 votesJeff
supported this idea
·
-
240 votesJeff
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…
Jeff
supported this idea
·
-
98 votesJeff
supported this idea
·
-
31 votesJeff
supported this idea
·
Other software I have seen does this by including a field in the upload spreadsheet file that contains the full path to the photo to be uploaded for each record. The software understands that if it finds data in the spreadsheet for a photo field in the DB, it's looking at the path and goes there to upload the photo.