Reporting best practices
Scheduled reports that run frequently or cover large data sets affect system responsiveness for your entire team. Therefore, create a report schedule that gives you the reports that you need to run your business effectively, but disable or modify scheduled reports that you do not download.
Genesys Cloud does not have rules for when you can run reports because factors vary by organization: report responsiveness is a combination of report parameters and time of day, as well as how busy the system is when reports run. To minimize report run time and failures, ask yourself the following questions:
- Are my report parameters overly broad? For example, am I running a “year to date” report every day?
Best practice: Adjust report parameters so that the report includes fewer agents, queues, interactions, or days.
- Am I scheduling my reports to run at the same time every other user schedules theirs to run?
Best practice: If possible, run reports during non-peak hours. For example, run daily, weekly, and monthly reports late at night or early in the morning. For hourly reports, choose non-peak times of day: 10 or 15 minutes before or after the hours.
- Do all my colleagues run this exact same report at the exact same time?
Best practice: Ask one user to run and distribute reports that the entire team uses.
- Have we recently checked our scheduled reports to see if there are any that we do not download?
Best practice: Review your scheduled reports frequently to ensure that you are not using resources unnecessarily.