I would love to see event registration information added to gift batches for easier processing. Currently, when processing registrations manual cross-referencing needs to take place between the gift batch and the event itself. It would be much more effective to be able to see which event the person registered for right in the gift batch. This would save tremendous time and limit data entry mistakes.
I am trying to process gifts while the gift entry person is out of office, and I don't know how I am supposed to link the event appeal to event registration forms, or assign the correct campaign if I can't see which event registration form the person gave through. I have been searching through my inbox to find the Blackbaud email confirmation.
Like Mohamed, I don't know if the person is purchasing one ticket and making a gift, or multiple tickets and exceeding fair market value. I am not the event manager, so I am not sure if the event is ticketed or there is a full donation.
I think batches should process via appeal/donation form. I don't find the current method helpful. Like gifts in my opinion are types of asks, or larger categories of giving vehicles.
Hi Samantha,
We currently have the same issue.
1) Event name and Event ID
2) The data entry mistake would be not knowing how many tickets the registrant bought and what is the participation level. for example we have events where an attendee ticket would cost 100, a silver sponsor ticket would cost 200 and a gold sponsor would be 300 if the registrant buys more that 2 attendee tickets for him and his guest it would be 200 and there is no way to know if it's an attendee ticket or a sponsor ticket.
3) One batch per event per day would be the right way to go.
Thank you
I think this idea should be merged with RENXT-I-5664
Seeing the ticketing information in the batch before it's approved would be fantastic. Right now, it's anyone's guess what the gift was for or if it was part of a fee or donation.
1) I would love to see the event, name, event ID, ticket information that was purchased (i.e. number of tickets, type of ticket when there are more than one type of ticket option available)
2) Right now it's easy to make data entry mistakes because of the manual cross-referencing that needs to happen. I have the batch open in one tab and the event open in a second tab. Going back and forth can cause unnecessary issues if the data entry person isn't careful.
3) I don't think this is necessary to separate out the batches by events. If the information is in the batch itself with the gift entry details, I think that would suffice.
Thanks for your idea!
I have some followup questions:
1) What specific event information are you looking to show up in the batch row? Event name, event ID?
2) What type of data entry mistakes will this prevent from happening? Can you give me an example?
3) Would it help to separate out gift batches so they only include gifts from one event (therefore if you are getting registrations for multiple events at the same time, you'd have one batch for each event, per day.)
Thanks for any additional info you can give!
Samantha McGuin
Principal Product Manager