Tending To Your Pending Queue
Regardless of which system’s data we are pulling into Web Services, it all lands in the same place: the beloved Pending Queue (labeled as ‘pending’ or ‘pending requests’ in Revolution CRM).
What is the Pending Queue? It’s the place through which all your accounts and donations pass in order to have your custom matching, batching, etc. logic applied. Most of these queues are automated (if yours isn’t and you’d like it to be, contact your ROI Client Team), but some records are held either because of a processing error or because of the matching logic you’ve requested. This means that someone at your organization needs to review the record before bringing the incoming data into Revolution CRM.
A “Processing Error” can occur when there is difficulty processing a request. Typically, this is because of an incoming transaction that has an invalid source code or none at all. A “Hold Reason” is based on a need you have to put the brakes on an automated procedure so someone can take a look at the record. Commonly this can happen when we can’t find an exact match but a possible/loose match – here you aren’t quite sure if the record matches this Jamal at 596 Main Street or that Jamal at 777 Maple Road.
Whatever the reason, having someone review the Pending Queue every day helps push records into Revolution CRM. If you find a lot of records are held for the same, or similar, reason, please contact your ROI Solutions Client Team to help evaluate enhancements to your integration so we can get those records processing on their own.