ID55 - Notify of Rescheduled Call Created WP and/or Badsync and PartsCost Exceeds Overview & Sample:

Notification of Service Call requesting next day delivery OR Waiting for Parts/Badsync call created exceeding specified cost.

Overview | Samples | Variables | Alert Functionality | Best Practices & TipsRelated Alerts

Click to Subscribe 



Notifies when new On Hold Service Call is created with following conditions:

1. Next Day Delivery Requested OR,

2. Part ordered exceed specified average cost OR,

3. Total of ALL Parts ordered exceed specified average cost OR,

4. Part(s) ordered showing as Badsync (invalid/non-existent Part #)

This alert typically is for the techs manager to watch for parts cost on rescheduled calls before the parts are ordered or installed.


Run Schedule: every 10-minutes

Type of Output: Email / Task App


*  *  *



Highlighted in RED showing why alert fired

Sample showing Individual Cost exceeded AND Next Day Shipping Requested:


Sample showing all parts when TOTAL of parts exceeded:





*  *  *




Variable W: Trigger when TOTAL of all parts cost exceeds this amount (please include decimal XX.00)

Variable X: Trigger when Individual parts cost exceeds this amount (please include decimal XX.00)

Variable Y: Enter list of OnHold codes to alert (separate by comma ie: Badsync, WP)

Variable Z: Limit to alert firing on specific Branch Number(s)

Variable 1: Indicate if alert should fire if Next Day Required Date indicated from tech (regardless of whether parts cost exceeds minimums set in VariableW or VariableX)


*  *  *

Alert Functionality 

Alert Functionality

-Please note this alert will only look back to calls 15 regulars hours (not business hours) old or younger.

-Alert will only notify of qualifying service call once. 

-Alert does NOT require equipment be linked to service call in order for alert to report on.

-Next day shipping is determined by the required by date on the line item within the service call. It's not a global setting. It's something the techs are setting when adding the item to the call.

-Bad Sync are part number(s) entered by tech that do not exist in your eAuto and are shown in Remarks tab on service call:


-Meters shown on alert are the last reported Valid Meter Reading(s) set with B\W and Color Category Type. The Category assigned to your meter types can be seen via Tools / Lists & Codes / Meter Types:


If you have more than one meter of same category type (i.e. Three Color Meter Readings), then alert will show the highest meter reading. For example, this device has three color meter readings (LV1, LV2, LV3) but also a Virtual Meter set as Color Category Type, so alert will show the Virtual Meter (114,804) as the Color Meter:



-This alert can be cloned which means creating multiple subscriptions of the same ID# (ID55). This function will ONLY work if at least ONE of the variables on each subscription is different. Just select + sign to create multiple subscriptions.

See this link for an overview of cloning features.



*  *  *

Best Practices & Tips

Best Practices & Tips

-Are you finding the alert is not reporting as you'd expect? The premise is that the tech goes onsite, determines part(s) needed, then marks the call as incomplete for parts. A new call is created, flagged as a reschedule, and then the tech would put the call on hold for parts. Alert will only consider calls marked as reschedules.


*  *  *

Related Alerts

Related Alerts

ID44 - Non Billable Part at Cost Exceeding W Used on Call

ID56 - New OnHold for Parts (WP/BadSync ) call just created (doesn't consider average cost for minimum trigger reason)

ID148 - New Incompleted/Rescheduled Call created with part costing > $W (doesn't consider total average cost of all parts on order)

ID393 - Same Part Number Causing OnHold for Parts Twice

ID628 - Call incomplete for Parts but Tech has Parts Needed

ID629 - Monthly List of Parts Required on Incomplete Call


*  *  * 


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk