Follow

ID310 Explanation Overview & Sample;

An alert to trigger when a service call has been on-hold for 'Bad Sync' for longer than variable W minutes.

Jump to a specific section by clicking a link

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

 

Click to Subscribe

 

Overview

Overview

When the part number on a service call entered through Remote Tech does not match any part number in e-automate, the call is put on hold for 'Bad  Sync Data'. To resolve the issue, the part number on the service call will need to be corrected, and the on-hold code removed from the call. This alert will trigger for calls that have been in the 'Bad Sync Data' on-hold status for longer than a specified number of minutes, so that the calls can be reviewed and updated.

 

Run Schedule:  Every 30 Minutes

Type of Output: Email

 

*  *  *

Sample

Sample

310_sample.png

 

*  *  *

Variables

Variables

310_variable.png

Variable W: Minutes - The number of minutes the call has been on hold before it will trigger this alert.

 

*  *  *

Alert Functionality

Alert Functionality

1. The call in e-automate must be on the 'Bad Sync Data' on-hold code; this is the only on-hold code the alert triggers on.

310_badsync.png

2. The alert calculates the time from when the call was set on hold to the time the alert is running. When the minutes between those two times exceed the value in variable W, the alert will trigger.

310_settime.png

*  *  *

 

Best Practices & Tips

Best Practices & Tips

None at this time.

*  *  *

Related Alerts

Related Alerts

ID56 - New Call Created On-Hold for Parts (Bad Sync or WP)

*  *  * 

 

 

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