12 results found
-
Linking new shift IDs to agents after published roster - no adherence/occupancy
When a shift is removed from the roster management page (sometimes in error), the all associated data is wiped out. From what I understand, "actuals and occupancy are tied to the shift ID, which is a unique ID generated by the application during roster generation." Once an agent's scheduled is mistakenly deleted the agent's schedule and shift ID are removed along with all the metric that were attached to it. When we add a schedule back to the agent, the new shift ID is created but does not marry the metrics already in process or recorded.
This affects the agent's…
2 votesThank you for raising this concept to the WFM team.
The Product Owner will review and update accordingly
-
add end dates to roster events
Right now when you add events in the roster config feature, you cannot set an end date. If I have a recurring event that will happen for just a week or a month, I would like to set it for only that week/month. As it is, I have to create the event, set it to start on the start date, and then delete it after all rosters are generated with it (and hope I don't have to regen). Alternatively, I can create separate events for each date, but this is very time consuming and leaves a lot of room for…
1 voteThis item is being prioritised for development.
We are beginning planning and will provide further updates as we understand when this item can be actioned.
-
Roster Generation Queue Feature
We're in the process of pulling together the logistics of being able to generate and publish our rosters for the remainder of the year.
However given the size of our main roster, it does take between 45/55mins to generate one and sometimes results in it timing out.
As a potential future feature, we would love to see a Roster Generation queuing function built in to enable us to stack all the rosters we wish to generate. We'd then have them begin generating at a defined point in time (end of day/working week) so they can effectively generate in the background…
3 votes -
Events: Improve Management and Filtering of Events
Provide an event management screen that allows an overview of existing events, creating events and provide filters.
3 votes -
Events: Ability to Create an Event to Cover a Requirement
e.g. 20 hours of FTE divided up by users X,Y,Z by role. Similar to a fixed forecast but demand based
2 votes -
Events: Allow Rotation of Demand Based Events
When creating a demand based event and selecting one agent per day over a period, system always defaults to the same single user and does not rotate between available users.
1 vote -
Events: Slack Notifications on Event Creation
When creating an event through the manage roster page provide an option to send a slack notification to assigned agents with event information
1 vote -
Events: Time Zone Awareness
When creating events that apply to multiple teams. If teams are spread across time zones allow the choice of what time zone the event will be applied to.
1 vote -
1 vote
-
Add an attribute to the shift to allow the pay period to be displayed,
must be able to set the pay period based on the roster so some kind of config on the roster page is required too
1 vote -
Maintain Consistent Shrinkage During Optimisation
Shrinkage applied at the workplan level should be taken into account when optimising for lunch and breaks. But instead it is ignored and safeguards that have been put in place to reduce impact to SLA are removed which is causing significant manual work.
0 votes -
Improved Minimum Thresholds on Roster Generation
Improve or enforce stricter rules around how long a task can be. Currently the generation will create tasks in the 15-30 minute range surrounded by other tasks. If we can enforce a task should be X amount of time at a minimum this will reduce manual work for adjusting these small tasks.
0 votes
- Don't see your idea?