" /> Login/Logout Time Reporting - Genesys CTI User Forum

Author Topic: Login/Logout Time Reporting  (Read 5090 times)

Dave B.

  • Guest
Login/Logout Time Reporting
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hi All,
Is there anyone able to report on actual agent login/logout times per day and per hour? I have been to 2 classes and asked the instructor and was told there is a login/logout table. I can't find it anywhere. We are using Genesys Express. I have no problem using the brio canned reports for total hours and how many minutes in an hour and agent is logged in. Managers here are trying to do payroll reporting on when an agent logs in and out.

Marked as best answer by on April 19, 2025, 09:30:01 AM

Superglide

  • Guest
Login/Logout Time Reporting
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • We do this for eWFM reporting and use one of the Call Concentrator tables for the task. There is in fact a login/logout table and along with some settings in StatServer Option Tab to turn this feature on. I do not know for sure if you actually need Call Con (the product) as our only instance in CME is disabled so perhaps just the database tables existing may be enough, as Statserver might write directly to them.

    ecki

    • Guest
    Login/Logout Time Reporting
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
    Yes, you are right. You don't need CCON to activate this logininfo table.

    Kevin

    • Guest
    Login/Logout Time Reporting
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
    Stat Server will write directly to them.
    What you can do is to work with your DBAs to create a view in Datamart what will permit you to extract the data, after tying it to the user objects, of course. Note that the time is stored in UTC, so you may have to do some conversions in the report.

    Note that there is also a status table, also configurable within Stat Server. Information on both these tables is in the rear of the Stat Server Reference, including table structure and descriptions.

    Superglide

    • Guest
    Login/Logout Time Reporting
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
    Just be careful about the databse sizing. Our experiance shows that it gets very big very quickly, so you need to have a plan in place to manage it from day one. Try something along the the lines of a rolling 30 days worth of data. You may also have to create some indexes on the tables to aid in purging.