Ask and you shall receive in the form of forecast flexibility! You can now show staffing forecasts based on operational hours right inside Tymeshift. I know I know... #lifechanging, but if you're thinking "why would we need that?" we've got the details to share.
When working to support customers we're usually looking at two request scenarios - live channels such as chat and voice in which we are helping our customers in real-time, and non-live channels such as emails and web forms in which we set expectations with our customers that we will get back to them within a specified amount of time (thanks SLAs 🙏).
Naturally, live channels have designated hours of operation - times you'll have chat turned on, and times you'll have it turned off. Non-live channels, however, can have requests flowing in at any time of the day or night, regardless of if you have someone at their computer to help out. If no one is on staff in the evening, and you have non-live customer requests pouring in, you'll probably have some sort of backlog in the mornings when your team starts their work day. This is why having designated hours of operation built into the forecast is a necessary element to disperse the backlog across the team, and include it in the workload you're forecasting for your agents - and thus the number of agents you schedule each day. This means more accurate forecasting, and staffing, while creating a better work environment by having accurate goals and expectations for your support teams.
How can you set this up in your forecast today? Easy! Just head into your forecast and...
- Click to select a workstream
- On the right information panel, click to expand Staffing Parameters
- Check the box under Availability at the bottom and enter your hours of operation for that workstream
- Click Save and watch your staffing needs automagically adjust!
Let me show you what I mean...
Though we wish backlog was not a word in our vocabulary, let's be honest it's unavoidable, so let's at least predict our needs to include that inevitable backlog and not drown the agents that jump on the first shift of the day, shall we?