This alert tracks service calls where techs have rescheduled a call, ordered parts, received and installed the parts, and then have had to reschedule the call again.
Jump to a specific section by clicking a link
Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts
Click to Subscribe
Overview
Overview
Are your techs just throwing parts at the problem? This alert tracks service calls where techs have rescheduled a call and ordered parts, received and installed the parts, and then have had to reschedule the call again. In other words, the first set of parts put into the machine did not fix the problem. The purpose of this alert is to try and identify when the tech is putting in high-dollar parts that do not rectify the problem; should those parts be uninstalled and put back to inventory? Does the tech need additional training on the machine that he is servicing so that this doesn't happen again?
Run Schedule: Daily in the evening
Type of Output: Email
* * *
Sample
Sample
* * *
Variables
Variables
Variable Y: Branch Numbers - List the branch numbers for the alert to trigger on, separate multiple branches with commas. Leave blank for all branches.
* * *
Alert Functionality
Alert Functionality
1. The parts used on the initial reschedule must be linked to the purchase order for this alert to work correctly.
2. If branch filters are in use, the alert checks the branch on the service call:
* * *
Best Practices & Tips
Best Practices & Tips
1. We recommend sending this alert to the service manager for review.
* * *
Related Alerts
Related Alerts
* * *
0 Comments