Alerts for successful installations of FM Audit.
Jump to Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts
Overview
Overview
Installation of FMAudit in new accounts is the most critical part of implementing that system. Dealers who are having the most success with FMAudit have embraced the challenges of installing and maintaining the software in their accounts and use the dispatch system to create calls for their techs for installation.
They do this by creating specific calls for a specific problem code (FMInstall for example) so that they have a closed call as evidence that the software was installed and tested. They then can notify the appropriate personnel that FMAudit is in an account so that others can continue with their part of the process (linking the FMAudit records to e-automate, to their CRM, etc). This alert is only useful for dealerships who embrace the idea of a separate FMAudit call for the tech for the installation, and this alert is only for completed calls.
There is a second alert to list all the FMAudit installs that failed, see here for ID123.
Run Schedule: Weekly on Fridays
Type of Output: Email
* * *
Sample
Sample
* * *
Variables
Variables
Variable W: Problem Code used for successful FM Audit installation. The default value is FMInstall
* * *
Alert Functionality
Alert Functionality
The alert is dependent on the setup of your problem codes in eAutomate. Problem codes are found under Tools - Lists and Codes - Problem Codes:
The problem code that is specified in Variable W on the alert should be used on all service calls for successful FM Audit installs:
The alert output will send a list of completed calls where this problem code was used, to indicate that FM Audit was successfully installed.
* * *
Best Practices & Tips
Best Practices & Tips
In order for the contra alert to work, how you setup the problem codes for call resolution are critical. For example, they should all start with FM and you should have only one that is used to indicate a successful Install (FMInstall) for example. You might have multiple to indicate problems that prevented the successful install (FMPCProb, FMCustDecline, so on and so on for the level of detail you want to track ).
* * *
Related Alerts
Related Alerts
ID123 - FM Audit Calls where the installation was not successful
* * *
0 Comments