Event Registration Transactions Headache

Options
When I'm linking someone who typed in their alternate email or phone number or used their nickname, RE ought to be able to check and see if First Name is a match or if Nickname is a match so I don't have to open up "Rob's" record to see if we have his nickname of "Rob" in there since RE wants to change Robert to Rob because the person typed Rob as their name.



Same with the others.



Rob puts in his work email and RE wants to replace his primary with this work email instead of checking alternate emails to see if it matches those.



Rob gives me his work phone number and RE wants to replace it with his home number instead of checking to see if we already have that phone number.



You catch my drift. I'm sure this is the same with gift processing.

Comments

  • Jesse - This sounds to me like it might fall into the IdeaBank suggestion named 'Improvement to transaction processing in NetCommunity tab'.  I think there's a lot of us who feel that the transaction processing could be greatly improved.

     
    Here's the description of the idea:  

    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).

     


  • Ditto on Gina's answer.



    I have had to struggle with this daily.  It seems like a flaw in the programming.
  • Gina Gerhard:

    Jesse - This sounds to me like it might fall into the IdeaBank suggestion named 'Improvement to transaction processing in NetCommunity tab'.  I think there's a lot of us who feel that the transaction processing could be greatly improved.

     

    Here's the description of the idea:  

    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).

     


     

    Wonderful! Thank you.

Categories