Improvement to transaction processing in NetCommunity tab
Current process for processing transactions coming from NetCommunity (signup requests, profile updates, donations, event registrations) are confusing for staff. Staff make many errors which inadvertently update records with wrong data.
Would like this process reengineered to minimize confusion and errors when processing transactions (like option to disable updating of address information).
-
Guest
- May 2 2014
Related ideas
There are so many areas to improve in aligning and connecting BBNC data to RE records. Wish list would include:
OH DEAR LORD YES.
Also, if the plugin could retain batch info... Too many gifts get dumb-ped into batches incorrectly.
relationship functionality within export
So much work to process one transaction especially when it involves a New Constituent, Tribute/Memorial and the "donater" enters the information wrong! Also, have a "question box pop up" to asked about adding to another batch versus just creating a new batch.
It also doesn't help that the interface is completely different for memberships than it is for other transactions.
I could gripe violently for hours about the whole creating batches business. It is the number one problem that my users have. Number 2 problem is updating address or name. I can't tell you how many times a Robert uses Bob and they overwrite the name. And no one enters ZIP+4, so every single time it comes up as not a match.
Also, the constituent search function appears to be exact. It doesn't look at nick names or spouse names or fuzzy matches. Users have to be far more diligent about looking for donors.
Is it possible to avoid all these mistakes? Sure. I can. On most days. But get one careless user in your system and you are screwed. Besides, a lot of these mistakes are easy enough for some of my best users to make if they forget any little thing...
Hallelujah! This is so TRUE! Particularly when a donor enters their own description of a fund name (and then you can't override it in the batch to the fund you know that they want). Or worse yet, an honorarium or memorial where a donor enters two names (or a married couple, per say), but you can't get it to pull through in RE because the tribute can only be attached to one record. Or even worse, when the give in memory of deceased pet and we have to add the pet as a constituent just to track the memorial gift. UGH!
Transaction processing is very confusing and staff are prone to make errors that can have serious consequences. Would like to see this redesigned.
Transaction processing is very confusing and staff are prone to make errors that can have serious consequences. Would like to see this redesigned.”
Improve this and guest processing!
@Julia -- I once got a gift in memory of Kermit the frog who I was not aware was dead not did I want to add to my database.
Transaction processing is very confusing and staff are prone to make errors that can have serious consequences. Would like to see this redesigned.”
Transaction processing is very confusing and staff are prone to make errors that can have serious consequences. Would like to see this redesigned.”
Transaction processing is very confusing and staff are prone to make errors that can have serious consequences. Would like to see this redesigned.”
Transaction processing is very confusing and staff are prone to make errors that can have serious consequences. Would like to see this redesigned.
transaction processing is confusing and staff tend to make errors that can have serious consequences. Please redesign.
A redesign would be very useful, especially since this is such an important feature set.
I would also like to be able to add notes to gifts from the plug in. As it stands, if something needs to be noted on the gift, I have to write it down or remember it, put it in a batch, and then find it and add the note. Lots of steps that when you are dealing with a high volume of gifts becomes very cumbersome.
And if those gifts are for the same amount from the same donor... those notes are even harder.
Transaction processing is very confusing and staff are prone to make errors that can have serious consequences. Would like to see this redesigned.”
I would add that it would be very helpful if NetCommunity had its own database for retaining the original selections/entries made by the online user. As it stands, all the information gets dumped into the RE Connector, and if the staff user makes a mistake when putting the gift in a batch, there is absolutely nothing to refer back to in order to see what the user originally entered - if we change or delete key information (address, etc), it's just gone forever. The raw data should be retained somewhere where we can look at it when we need to.