Follow

ID123 - FMAudit Calls where Installation was not Successful Overview & Sample:

Alert for FM Audit calls where the installation was not successful.

Jump to Overview | Samples | Variables | Alert Functionality | Best Practices & Tips |  Related Alerts 

Click to Subscribe 

Overview

Overview

This is the contra alert for ID122 (Successful FMAudit installs). ID122 works by reporting all the calls with the Problem code you specify in VariableW for that event, and that problem code should indicate the successful installation.

This alert is to report all the unsuccessful installations, so instead of listing all the possible reasons different dealerships might want to track, we use some logic around your Problem Codes. You would need to have all your FMAudit problem codes start with FM for example and have only one of those problem codes indicate success. All the others would be reasons why the install was not successful (pc issues, customer declined, firewall issues, etc..). Some Examples we've seen used are: FMREFUSE: FM AUDIT REFUSAL FROM THE CUSTOMER FMRDSI

 

Run Schedule: Weekly on Fridays

Type of Output: Email

 

*  *  *

Sample

Sample

ID123.png

 

*  *  *

Variables

Variables

ID123_variables.jpg

Variable W: Problem code used for successful installation of FM Audit, the default value is FMInstall.

Variable X: First two characters of the problem codes used for FM Audit installs, the default value is FM. All problem codes for unsuccessful installations of FM Audit must start with these two characters.

 

 

*  *  *

Alert Functionality

Alert Functionality

The alert is designed to let you know of unsuccessful installations of FM Audit, it does so by listing completed calls with problem codes starting with the two characters indicated in Variable X. Problem codes are set in eAutomate in Tools - Lists and Codes - Problem Codes:

ID122_problem_codes.jpg

It's important that all problem codes that you want to monitor start with the same two characters.

The problem code is then used on the service call to indicate that the installation of FM Audit was not successful:

ID123_invoice_call.jpg

 

*  *  *

 

Best Practices & Tips

Best Practices & Tips

It's important to set the problem codes correctly in eAutomate to track all the reasons why installation of FM Audit at the customer site was not successful. All of these problem codes will need to start with the same two characters to be tracked by the alert.

 

 

 

*  *  *

Related Alerts

Related Alerts

ID122 - FM Audit successful installations

 

*  *  * 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk