Alert to trigger when an incomplete call is set with the incomplete code in variable W.
Jump to a specific section by clicking a link
Overview | Samples | Variables | Alert Functionality | Best Practices & Tips | Related Alerts
Overview
Overview
It's important to know when a call has been rescheduled and the reason why. If you are using the Inventory Logistics Console (ILC) for hold for parts calls, it keeps a full circle account on the order data trail from open to close. Other calls you might want to track will let you know if your techs are putting calls on hold because they aren't carrying the correct parts, not verifying office hours with customer (hold for time), or taking too long for lunch.
This alert will trigger every fifteen minutes on calls incompleted with the incomplete code you specify in Variable W. You can specify multiple incomplete codes with a comma in Variable W.
Run Schedule: Every 15 minutes
Type of Output: Email
* * *
Sample
Sample
* * *
Variables
Variables
Variable W: Incomplete Codes for alert to trigger on. This variable is required for the alert to run.
* * *
Alert Functionality
Alert Functionality
The incomplete codes to enter into Variable W are found in e-automate in Lists and Codes:
Enter the Incomplete Code into the variable, not the Description.
The alert will trigger on calls with one of the incomplete codes set in Variable and the close date on the service call is within the past seven days. The alert will only trigger once per incomplete code.
* * *
Best Practices & Tips
Best Practices & Tips
Click here for more best practices on rescheduling calls.
Click here to see best practices for incompleting a call.
Click here to see best practices on linking a call.
* * *
Related Alerts
Related Alerts
ID148 - New Incompleted/Rescheduled Call created with Parts Costing > Var W
ID372 - Tech Productivity Incompletes Report
ID628 - Call Incompleted for Parts, but tech has parts needed
ID629 - Parts Required on Incomplete Call
* * *
0 Comments