ID310
Call OnHold status = BadSync for longer than VariableW minutes
Output Type: Email
If you are using RemoteTech and a technician requests parts in RemoteTech that cannot be matched to any item in your e-automate inventory, then those calls come into e-automate dispatch with an OnHold code BADSYNC and show up as BadSync data received from remote client. These calls should normally be addressed by your inventory person quickly (we have alert ID56 that sends an alert to your inventory team anytime a new call is created with BadSync data). This alert is to watch and report calls that are still OnHold status BadSync for longer than W minutes (set in VariableW). This alert normally would run every 30 minutes and continue to list all calls BadSync that are still in that status. As your team processes a BadSync call they typically would change the OnHold status to reflect the real status of the call (parts ordered / parts available / etc.).
Related Alerts
| ID # | Description | Notes | Required |
|---|---|---|---|
| ID56 | New OnHold for Parts (WP/BadSync ) call just created | ID56 sends an alert to your inventory team anytime a new call is created with badsync data, ID310 will watch and report calls that are still onhold status badsync for longer than W minutes and continue to list all calls badsync that are still in that status. As your team processes a badsync call they typically would changed the onhold status to reflect the real status of the call (parts ordered / parts available / etc). | No |