Rick Rogers
My feedback
16 results found
-
21 votesRick Rogers
shared this idea
·
-
100 votes
We started working on providing members ability to stop their own membership. Stay tuned for updates!
Rick Rogers
supported this idea
·
-
178 votes
Evgeny Zaritovskiy
responded
Merged together several closely related by meaning ideas – so we can properly resolve them all together, in different live scenarios
Rick Rogers
supported this idea
·
-
72 votesEvgeny 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.
Rick Rogers
supported this idea
·
-
24 votesRick Rogers
supported this idea
·
-
211 votesRick Rogers
supported this idea
·
-
103 votesRick Rogers
supported this idea
·
-
85 votesRick Rogers
supported this idea
·
-
240 votesRick Rogers
supported this idea
·
-
236 votesRick Rogers
supported this idea
·
-
159 votesRick Rogers
supported this idea
·
-
119 votesRick Rogers
supported this idea
·
-
356 votesRick Rogers
supported this idea
·
-
266 votes
Dmitry Smirnov
responded
Even though it is not a direct implementation, I hope this could be helpful:
We just launched integration with Integromat platform, which helps to build automated workflows. We also provide several templates for quick start, and one of them allows to copy google calendar events into WA events. So if you share a google calendar for events submission, then the scenario could copy submitted events into your Wild Apricot account.
You can try this integration by this link https://www.integromat.com/en/integration/2275-copy-google-calendar-into-wild-apricot-eventsRick Rogers
supported this idea
·
-
3 votesRick Rogers
supported this idea
·
An error occurred while saving the comment Rick Rogers
shared this idea
·
-
102 votes
An error occurred while saving the comment Rick Rogers
commented
Nevermind, I see the other thread on changing levels upon renewal. :)
We also use this kind of business process. We've implemented a change of level from "Member" to "Late Paying Member" and we have to manually move members back after they renew. Luckily we are a small organization.
Implementing a late fee structure would be the most elegant solution, but a simpler solution comes to mind: how about just having actions that can be triggered upon renewal. In this case, upon renewal of a "Late Paying Member" we would change their level to "Member" again.
Sorry for the lack of clarity and the clear mistake regarding the email header. I should have double checked before posting. It was actually a reply from a member to an automated renewal email that didn't have the cc'ed admins. WA obviously can't control whether someone hits reply-all when responding to the renewal email or not.
Some email clients don't include the cc list from the initial email in a reply. However, if in the text of the email the cc list was included, the recipient(s) of the reply that may be on the guild's executive but not an admin, would still be able to find the email addresses of the admins involved. Then, rather than having to forward to an administrator, who then has to reforward to the membership admins, the email can be properly directed.
Ideally, the role and persons in the role would be listed. That will also help to educate people about which emails flow to which roles set up in WA.