How do you combat the issue of agents not logging out?
What are your enterprise support centers doing to combat the issue when agents forget to log out at the end of their shift?
Best Answer
-
Hi Tishia; I've seen this approached with auto-timeouts to logout employees when they have been inactive for more than 30 minutes, and supervisor dashboards to monitor logins, so they can log them out after their shift if they forget. I know this can mess up productivity reports. I remember one company that had employees click a "working" button on a case to track time, but they would click "working" on multiple cases and never go "off work," so at the end of the week it looked like everyone was working 200 hours that week.
7
Answers
-
I would be really curious about how often teams see this issue, and the products they’re using. Considering some of the larger service management platforms out there, like ServiceNow, Microsoft Dynamics, Salesforce Service Cloud... no matter what you’re using, this is probably a concern for you. On one hand, you can track every “touch” in a case / ticket, even if it’s just a supervisor reviewing an employee’s work, which may overinflate the time spent on a ticket. At the other end of the spectrum, you could ask team members to intentionally go into work / start and stop the timer, which then gives you the issue stated above.
I would love to hear what variations other members are using (manual vs. automated) and how it’s working for you?
Thanks!
1 -
We use ServiceNow as our ticketing platform , we don't track the login/logout times , we instead track the time spent on each incident, whenever a incident is opened by a agent they have to manually start the timer which appears on the incident screen and they can pause and start it again depending on how much time they are spending on a incident. In our reporting, we look for any outliers in the data and review those incidents if required.
1
