Daily Reports

After the robot completes its daily run, it will send out an email report that will provide information on the following:

• Document processing rate 
• Activity processing rate 
• Exception errors that will require human processing
   

Document Processing 

The document processing report will provide an overview of documents that were successfully renamed, documents that could not be renamed due to errors, and documents that were skipped for processing if the document type renaming was turned off. 
 

Understanding Document Processing Errors 

It is normal to encounter a daily exception error rate of about 5-10%.

The following are the most common types of errors customers may see on their daily reports: 

Exception Error: Failed to extract: x, y, z 

What does this mean? The robot was unable to extract the required data point(s) for renaming from the policy document.

What happens next? Quandri confirms the data points exist on the processed document. Once confirmed, the team will prioritize additional robot training to enable accurate and complete data extraction.

Exception Error: Failed to identify carrier

What does this mean? The robot has not yet been trained to read the carrier's documents. 

What happens next? Quandri currently supports 90%+ of Canadian carriers; however, the team is always working on adding more carrier coverage. If a currently unsupported carrier makes up a significant portion of your policy volume, please let the team know. 

Exception Error: Failed to identify document type

What does this mean? The robot was unable to recognize the document type.

What happens next? Quandri will prioritize additional robot training on the failed document types. 

Exception Error: Failed to identify policy type

What does this mean? The robot was unable to determine the policy type.

What happens next? If the robot should have found this policy type, let us know.

Exception Error: Document not supported yet

What does this mean? The robot recognizes the document type but isn’t yet able to extract information. 

What happens next? Quandri will prioritize additional training for unsupported document types. 

Exception Error: No matching SSR with effective date: [date]

What does this mean? The robot looked for a service summary row with a matching effective date but there was none present. 

What happens next? Customers should verify if there is a service summary row with a matching effective date. 

Exception Error: Multiple matching SSR rows

What does this mean? The robot was unable to select a service summary row because there was more than one service summary row that matched. 

What happens next? Customers should verify if there are multiple service summary rows with matching effective dates. 

Activity Processing 

The activity processing report will provide an overview of activity management and processing. 

If the robot was not able to reassign or close the activity as configured, depending on configured workflow requirements, it will be noted as a failure on the report. These types of failures are rare; however, if you are noticing a higher volume of activity processing errors, please let the Quandri team know.