Clark Bavin
My feedback
6 results found
-
135 votes
An error occurred while saving the comment Clark Bavin
supported this idea
·
-
34 votes
An error occurred while saving the comment Clark Bavin
commented
Being able to arrange & display Event Ticket Types in a particular order, either Highest Ticket Cost to Lowest or in a particular fashion. Only way this happens now is to add a number or alphabet to the Name. We should be able to move the types around, just like you move other blocks of things around in the website.
Clark Bavin
supported this idea
·
-
26 votes
An error occurred while saving the comment Clark Bavin
commented
We would like an easier way to have multiple Event Ticket Types - where a member can go in and buy X number of tickets at $35 and X number of tickets at $10l. And have it count toward the total event cap. We have limited number of space due to the Fire Marshall - so it's extremely important to have an accurate attendee account. It's almost like a checkout cart feature. We want to have people pay on line. Now they have to run their credit card multiple times for an event instead of once.
Clark Bavin
supported this idea
·
-
18 votesClark Bavin
shared this idea
·
-
369 votes
Evgeny Zaritovskiy
responded
I merged another very similar thread into this one, they should be solved together – the registration to multiple events should be simple and fast if possible. There are a number of suggestions in comments on how to achieve this.
Clark Bavin
supported this idea
·
An error occurred while saving the comment Clark Bavin
commented
I would just like to jump in and say I think these are all good ideas and would like to see these get bumped up the Wish List for the next version ASAP. Our organization runs a lot of events. We want to provide option of purchasing a table of 10 and let the person organizing the table, enter their guests and cap it at 10 people. Same with different sponsorship levels, we offer an allotment of tickets per sponsorship level. What makes it confusing is that we have individual Event Sponsors, as well as, Annual Sponsors - both have different sets of ticket allotments.
For Annual Sponsors, we've considered giving out Event Codes/Coupons but right now there's no way to monitor the usage or limit the number of times one can use the code. With Event Coupons, we want to have the ability to put a limited # of uses by a given member. Perhaps, we should first create a group from within the membership database and apply the coupon/code to this particular group. Then, it would be helpful to then be able to set a total number of uses of the coupon, or total number of registered attendees. In other words, let's say a member is entitled to 4 tickets to 6 out of 8 events over the course of a year. We would like the system to monitor and know that this member has used the coupon for their 6 events.
Another example, we sell a "Passport" to attend our monthly breakfasts - good for 10 breakfasts. We'd like to know if the person has used up all that they're entitled to and not over-registered or trying to attend for free. Some times these people split their 10 breakfasts and bring a co-worker, so they might use 2 tickets at once, thus reducing their total allotment. We'd like the system to be able to give this kind of flexibility, but also to track usage. And it probably wouldn't be bad to have an e-mail generated to these members letting them know where they stand on their allotment, so that they're also aware and monitoring the usage of their coupon.
I hope that this is helpful to others.
[quote user="CJoeG"]
Hi,
The new feature for multiple event registrations is a very significant step forward. However, it falls short of being useful to one of our main customers. That customer stages races which include teams of up to 8 people (but no more than 8).
Here is a list of features which they need to be in place in order for this important new feature to work for them. They are looking for the ability to:
1) set a limit on the number of additional people who can be registered (e.g, 7 additional or 8 total),
2) update the list of additional people registered (by the original registrant) until a specified date (e.g, add two people now and then add more people later until the time limit, and max registration limit (see #1 above) has been reached), - After further testing it seems that the original registrant can keep the registration in a "Pending" state that may resolve part of this issue!
3) create a registration for the initial registrant and associate it with a group/team name,
4) either: list the name of the registered groups/teams (not just the name of the person which created the initial registration) so that a person can search the list to ensure uniqueness, or the ability of the system to veryify uniquiness of a field (group/team name in this case),
5) specify the exact number of characters of a text field on a registration form (group/team name can not be more than 20 characters long on two lines of no more than 10 characters each), and
6) modify the wording of "guest" to something more appropriate on the registration form (e.g, team member, etc.),
The customer's original request asked for the ability of "guests" to add themselves to a named "team", but requiring the person that created the original registration, (the team captain) to add the other members will work with a modification to their team registration work flow.
I look forward to working with you to understand these requested features in more detail.
Joe
[/quote]
-
58 votes
Team Events
responded
WORKAROUND: it is possible to set different colors using custom javascript. See section “Color coding events using event tags” at
https://help.wildapricot.com/display/DOC/Event+tags#Eventtags-colorcodingColorcodingeventsusingeventtagsClark Bavin
supported this idea
·
An error occurred while saving the comment Clark Bavin
commented
I would like to recommend the option of color coding events on the calendar postings, so that we could more easily identify between Board Meetings, Member Events, or Community Events, etc.
Not only do we need the ability to have feedback text boxes, but we need the option to be able to make the questions themselves mandatory or non-mandatory. We also need to be able to reorder or re-arrange the questions, just as you can with the options. I found myself having to rebuild the entire survey because we wanted a new leading question.