ID219
Service Call Closed with potential bad data entered
Output Type: Email
95% of the new clients we take on have inaccurate data in contract profit reports, mostly due to things like a technician entering a kilometer reading instead of miles. Then you have 97,000 miles showing as a cost on a contract! This alert is meant to catch where either users ignored the automated popup warnings OR you do not have any values setup for the popup warnings. This alert will also report calls closed with a date in the future. This is usually just a mistake but will affect your service statistics and should be fixed. Alert will fire at time call is closed and again at time of invoicing if not corrected.
Related Alerts
| ID # | Description | Notes | Required |
|---|---|---|---|
| ID18 | Guaranteed response time could be missed | No | |
| ID93 | Pending 'CM' calls that are within (W) minutes of due time with EscalationAlert within X (customer down) | No | |
| ID223 | CM Category Calls for Today where arrival time was after DueTime (ignores Reschedule Calls) | No | |
| ID1 | Call Dispatched (not arrived) between W & X hours | No | |
| ID17 | Technician On-Site too long | No | |
| ID2 | Dispatched/OnSite After Hours | No | |
| ID150 | Contract Profitability by Rolling Month | In order to insure the accuracy of ID150 contract profit alert, please install ID219. | No |
| ID768 | Biggest problem contracts without a plan | Bad Data entries on service calls | No |
| ID771 | Power BI Profit & MIF Analysis | ID771 Power BI Dashboard uses your ID219 settings to show potential bad data | No |