Adding the rejected positive response reason to the Rejected Contract Locator Response emails would be extremely helpful in keeping our contract locators immediately informed when our one call center rejects positive response. This would be a significant improvement over using the end-of-day report due to the short time to respond to emergency notices from the one call center. Because emergency requests require a response in 2 hours or less a failed response for an emergency would likely result in a no-show code being issued prior to the end of day report being issued. These no-shows would negatively affect us in state regulatory space because we would be out of compliance with our response to the one call center.
To prevent this, we have resorted to issuing profiles for our contract locators in our instance of Utilisphere to allow them to view the ticket information in the hyperlink imbedded in the Rejected Contract Locator Response emails. I had to create a new group profile for these users with virtually no permissions to prevent them from accessing more of our data than we would like them to have access to but there isn’t a surefire method from preventing them from accessing more than just pertinent ticket information.
This enhancement would give us better control over what information we need to share with our contract locators and still allow us to immediately provide them with the root cause of the Rejected Contract Locator Response.
Adding the rejected positive response reason to the Rejected Contract Locator Response emails would be extremely helpful in keeping our contract locators immediately informed when our one call center rejects positive response. This would be a significant improvement over using the end-of-day report due to the short time to respond to emergency notices from the one call center. Because emergency requests require a response in 2 hours or less a failed response for an emergency would likely result in a no-show code being issued prior to the end of day report being issued. These no-shows would negatively affect us in state regulatory space because we would be out of compliance with our response to the one call center.
To prevent this, we have resorted to issuing profiles for our contract locators in our instance of Utilisphere to allow them to view the ticket information in the hyperlink imbedded in the Rejected Contract Locator Response emails. I had to create a new group profile for these users with virtually no permissions to prevent them from accessing more of our data than we would like them to have access to but there isn’t a surefire method from preventing them from accessing more than just pertinent ticket information.
This enhancement would give us better control over what information we need to share with our contract locators and still allow us to immediately provide them with the root cause of the Rejected Contract Locator Response.
0 Votes
0 Comments
Login or Sign up to post a comment