It is extremely unfortunate to not be able to view from a constituents record in NXT if they have accepted, declined, etc. from the response field on the database side. Seems like a simple fix and shouldn't require a group discussion. Also, being able to sort so the most recent events can be on the tops seems simple enough as well. Why do we need votes for common sense fixes?

Samantha,
I would be happy to sit in on a call. I'll be out next week, back on the 22nd, but send along the invite and I'll respond as soon as I get back.

Thank you
Brian

Hello! We have some preliminary designs for a first class "RSVP status" field and accompanying backoffice functionality that I'd love to run by some of you! If you'd like to join a call to review these designs the week of October 28th, please email me at samantha.mcguin@blackbaud.com and we'll get you setup with a time for a 30 minute call.

Thanks!
Samantha McGuin
Principal Product Manager, Events

I agree. We use the Registration as Registered, Not Registered to generate the quick view total count of how many are attending.  Currently, in the DB view it is displayed at the bottom, so it should be able to be added to NXT. 

So many times, the Chairperson, ED or CEO will ask "so how many people are coming" or the venue wants a count. A quick view to this number in NXT would be great. 

There are two fields. The 'Registration Response' field is located in database view in between 'Invite' and 'Register' it is customizable and it is NOT available in NXT. The 'Registration Status' field is NOT customizable and it is available in NXT. 

We really need the 'Registration Response' field in NXT.

Samantha, yes we do. For example, we have a bike ride where people are sponsored riders. Their registration is paid for but because of issues with the event website, they were comped for both their registration and $100 jersey. Using the "partially paid" status let me easily find who we needed to follow up with for jersey payment.

Amy Dana - do you have a status for partial payments, specifically?

We use it for payment, too. It's especially  helpful for partial payments.

Our table currently includes:

Accepted

Booked

Cancelled

Complimentary

Declined

Invited

Paid

Refunded

Waiting list

I'm not sure all of those are in the correct place and aren't replicated somewhere else,  or that they are all used, but that's how we have it at the moment.

Hope this helps!

We use status to track payment globally for an event, since we can't always use theregistration fees tab to know what's going on - especially if there's no gift to link, or we only want to use 1 Unit/ticket per table sponsor. We use Paid, Complimentary, Event Package, Pre-Purchase, and Not Paid. We have not needed Cancelled or Refunded since we expanded this field table, but those would also be valid. (Cancelled is also a Response option.)

Thanks for this Idea and votes! Since the Status field is user-defined - you can set what values you want within it, can you give me more information about what options you have set for your Status field?

We are evaluating several new status fields to account for many of the items we typically see in customer's status fields. Having additional information on your setup will be very helpful! Thanks!