Would like the option in a event campaign to have the ability to register in the same event for more than one day. Example, I hold a banquet two nights in a row at a large trade show. In the same event invite I would like for my customers to choose which night, or both nights if they wish, to attend. As it stands now I have to send out two separate invitations forcing my customers to go through registration more than once.
... View more
Jim Mariano, CTCT_Event , I have provided similar feedback ever since Constant Contact launched Event Marketing (aka EventSpot). I have entered it into the Feedback form. I have called it in. I've sent it via Chat, and I've emailed it. I usually hear that the engineers prioritize based on what's most important, and that the backend administrative functions just aren't being requested. Even though this may be duplicating what others say, here's the very BASIC functionality EventSpot should have: 1) Administrators should be able to add registrants through a back-end feature, and not have to go through the client-side registration. This should be as easy as entering data into a spreadsheet, with multiple columns that can be quickly selected (Paid, registered, etc.) 2) Administrators need to be able to enter notes into the registrants' files. If someone needs special services, if they will need to arrive late, if they are bringing a friend, etc. etc. 3) Adminstrators should be able to add guests into a registrant's record. We get people who call in to add a "plus one" or "Plus two" all the time. 4) People should be able to enter their email more than once. Many couples share an email, and often times I'll have both parties wanting to register, at different times. 5) Administrators should be able to enter VIPs, Speakers, etc. without having to make up email addresses. We need them in there for food and seat counts, name bagdes, etc. If they get an email telling them they are registered, it often causes confusion. 6) Administrators should be able to enter people who pay on-site, by phone, or who are comps, without making up an access code and entering it. When I have to make that workaround of an access code that says, "PAID_PHONE" it gets emailed in the confirmation to the registrant, and then I have to make new access codes for the next function so that people don't test that access code in the future. Likewise, access codes shouldn't be listed on confirmation emails.... 7) Payment pending: when the payment arrives, I should be able to mark if it was made by check, cash, etc. 8) EventSpot mobile: we need to be able to enter people who are walk-up registrants via EventSpot. Having a mobile app for live check-in is great when we have multiple people at multiple spots, but I still have to have a paper system for notes, entering those walk-ups, etc. Thanks for your interest in making this a better environment for US, your CC customers
... View more