37 results found
-
Intraday Template Second Workload Column Should Be AFSHT
Intraday historical template, the second workload column should be AFSHT, not AFAHT. I tried importing it for the first time using data in both columns today, and it simply overrode the AFAHT when I kept the column titles unchanged. It ended up giving me just one column. When I changed the column title to AFSHT, it took the second column as solved handle time as I expected to see. Adding an attachment for reference.
1 voteThank you for taking the time to bring this feature request to Playvox.
A Product Owner will review the request for potential inclusion within the backlog / roadmap. Updates will be provided as the feature progresses.
Regards,
The Playvox Team
-
Show weekends on Forecast export, even if value is '0'.
When using Seasonality forecasts and the option to forecast for weekends separately - include weekends as entries on the forecast export CSV, even if the value for that day/weekend is 0. Currently, these do not show if the value is '0'.
1 vote -
Ability to export the forecast in different intervals
Clear review of over/understaffing forecasted / The ability to export Forecasted HC vs Required HC at different intervals instead of just 15 mins (i.e. 30 min, hourly, daily, etc)
0 votes -
Import fixed FTE forecasts for multiple weeks
Currently, the CSV import of a fixed interval FTE forecast only takes in up to a seven day Monday-Sunday period. It would be helpful in our use case (forecasting for work outside of Playvox that does not have a workstream integration) to mass import for multiple weeks at a time.
1 vote -
Ability to add a minimum FTE requirement & Shrinkage for a workstream as a scenario
Extend the current scenario functionality to allow you to select a minimum FTE requirements either for all coverage hours or between specific business hours. In addition, the ability to program shrinkage % in the workstream scenario to ensure that coverage is always x% over the minimum requirement - currently this is programmed at the workplan level
1 vote -
Use Backlog in forecast
The ability to manage backlog of email/tickets within the tool and then distribute this as part of the forecast/roster.
2 votes -
Configure the historical data to use for Forecast Arrival Patterns
Allow you to configure which historical days, weeks, months you want to use for forecasting the arrival patterns rather than the last 6 weeks. Also allowing a combination of these options to be used. ie. Thanksgiving week 2022 can be used for Thanksgiving week 2023. Or rather than a week since the day can move, Christmas Eve 2022 (Saturday) can be pulled in for just this coming Christmas 2023 (Sunday) arrival pattern. This would reduce the need to create custom intraday profiles via csv import.
1 vote -
Expose Recent Volume Trends in Forecast Configuration
Display volume trends as a percent in the Forecast configuration that can be edited if preferred. For instance, it's showing ^5% as the recent trend it's using to calculate the upcoming forecasts, the client can choose to keep that or can edit it to something else they would like to use for the upcoming forecast.
3 votes -
Zendesk allow only one ticket open to accurately capture AHT
Would like the Playvox widget in Zendesk to restrict ticket tabs to allow only one ticket at a time to be open. Also would like the widget to continually track AHT and not allow agents to be in a ticket status without a ticket open.
2 votes -
Add weights as adjustments to forecasts
Our inbound #s are impacted by changes in the overall business that we are aware of ahead of time. Right now we manually generate our forecast based on projected business changes, which is a very time-consuming process.
We'd like to be able to apply changes using our business forecast info to the base Playvox forecast.
1 vote -
Historical Pattern Summary - Ability to select day of week when looking at multiple weeks
When I'm looking at multiple weeks at a time I'd like to be able to filter down to day of week. For example if I'm analyzing the last four weeks but only want to see the last four Mondays side by side. A day of week filter option would allow me to do this.
2 votes -
Historical Pattern Summary - Variance Change the Calculation
This variance in the above page needs to be adjusted always to the forecast.
Currently it picks whatever the variance is, high or low and is not a consistent calculation to be used for analysis. Example is that if the forecast exceeds actual, positive. If forecast less than actual, negative.1 vote -
Clone Scenarios on Manage Forecast page
We spend a ton of time creating overrides for different workstreams or sets of workstreams. Sometimes we'll be creating overrides different overrides for 12 months, each of which covers 16 workstreams that we have to create over different scenarios, which leads to hundreds of clicks and hours of time. So much time would be saved if we could duplicate scenarios and overrides and then just make the small edits to dates/percentages.
0 votes -
Downloadable Mean % Error by workstream
We would like for mean % error to be included in the CSV download on Historical Patterns Summary by Workstream. As it is now, forecasted and actual data are given by Workstream but mean % error is only given in aggregate. We want to be able to see Workstream by Workstream trends in performance by day without having to search and download each Workstream separately.
1 vote -
See Historical Patterns Summary graphs for all selected workstreams
Currently, you can only see the graphs on Historical Patterns Summary page (Such as Daily Historical Volume Patterns graph) for one workstream at a time. It would be very useful to be able to have these graphs show multiple workstreams at a time/all workstreams at once. If, instead of a dropdown where you can select one workstream, there were a dropdown where you could select multiple workstreams at a time, like the option you have when filtering, that would be very useful.
1 vote -
Historical Patterns Summary | Ability to Export Intraday AFAHT Data
We are able to export the intraday volume graph, the daily historical volume pattern graph, and the intraday historical volume pattern as .csv or .xls. However, the last graph for AFAHT, you cannot export as .csv or .xls. Could we make it possible to do so? Reason being twofold; the other three graphs are exportable, and then this is the only place AFAHT is all encompassing by day and interval.
3 votes -
Add option to combine / not combine SLA on Forecast Configuration UI.
We need an option on the Forecast Configuration UI for users to choose if they want to COMBINE (default) SLA when calculating forecast workstream by workstream, or to not combine.
The reason we need this is because workstreams can have different SLAs so if you combine / don't combine it changes the staffing requirement noticeably.
0 votes -
Forecast-->Manage Forecast
Rounding enabled functionality on this screen, needs to be at organization level or forecasting config to turn on or off for all of forecasting views (i.e. Manage Forecast, in Performance Summary, etc); Use Case: If I edit forecast, default in the site is rounding enabled and won't reflect the correct forecast volume. Needs to be a global setting to touch every place the forecast is visible based on the edit forecast adjustment.
1 vote -
Make it easier to re-run the forecast
Currently, to re-run the forecast after a change is made you have to click Edit > Set Last Run Timestamp, then save workstream configuration, then fully leave the Forecast section and come back after 5-10 minutes. It would be nice if there was a straightforward way to re-run it.
3 votes -
Forecast Phones/Chat Workload Based on Historical w/ Fixed Minimum Requirement
The ability to allow the system to generate the FTE requirement for the workloads for Chat and Phone based on historical arrival patterns, but to also have a fixed minimum requirement (ie. 1 or 2) to protect the workstream in the event that there's no requirement to guarantee that the workstream will still have some coverage. It would be helpful to not have the min requirement to be added to the historical forecast when the historical exceeds the min requirement, but only utilize the min when the requirement based on the forecast would fall below the min. required set.
9 votes
- Don't see your idea?