Role
Customer service team lead
When do you decide how many people will be on service tomorrow? If it is the day before and by feel, then every few days you have either a queue or people with nothing to do - and both cost money.
Intro call
Four questions we would start with
When is the decision about tomorrow's staffing made?
If it is from one day to the next, people have no predictable rota and you have no margin to react. The same change improves both.
Who notices first that the queue is starting to grow?
If you find out from a report after the fact, the response comes a day late - and the client remembers that day, not the monthly average.
What do you put off first when volume rises?
Usually development conversations and feedback - exactly what reduces turnover, and turnover is the main reason volume stops being handled.
How do you know the team will cope with today's volume?
If it is from experience, that works until the first unusual day. The history of volume usually says more than the team assumes.
We take over the planning and the counting, you keep leading the people
Forecasting volume, building the rota, steering the queue and reporting can be taken off the desk. Conversations with the team, decisions about staffing and developing people stay with the team lead.
- We measure the queue, not people. - Response time, volume, the spread through the day. Rankings of individual agents are a different project and a different conversation.
- The forecast is a proposal, not a rota. - The staffing is approved by a person, because they know the holidays, the competences and that somebody is back after an illness.
- The signal comes during the day. - A growing queue has to be visible while people can still be moved, not in the morning report the next day.
Scope
What can be taken off running a service team
Eighteen example tasks. Each one has a human approval point. Below is a selection, and the scope we fit to your process.
Volume forecasting
- A forecast of volume from history, seasonality and events
- Pointing out the days and hours at raised risk of a queue
- Linking a rise in volume to other departments' campaigns
- Comparing the forecast with what happened in previous periods
The rota and staffing
- A proposed staffing against the forecast (approved by: the team lead)
- Accounting for absences and the qualifications required at positions
- Pointing out gaps in staffing over the coming weeks
- Handling changes and swaps in the rota
- Workload summarised by queue and by hour
- A signal when the staffing does not cover the required qualifications
Steering during the day
- A signal when the queue is growing, in advance (decision on how to react: the team lead)
- Pointing out queues being handled more slowly than usual
- The spread of waiting cases by topic
- Information about cases exceeding the agreed time
Topics and reporting
- A summary of the topics where cases take longest
- Pointing out topics with no competence cover in the team (assessment: the team lead)
- An onboarding plan for a new person in a position
- A periodic report for the board (conclusions: the team lead)
A day's work
Today
- You build the rota in a spreadsheet, starting from zero every week
- You learn about a queue when somebody on the team says they cannot cope
- At an absence you move people ad hoc
- You assemble the board report by hand from several views
- In weeks with a peak there is no time for development conversations
- You do not know whether tomorrow's volume will be high
With AI assistance
- The proposed staffing is waiting, you correct it
- A growing queue reports itself while you can still react
- You see gaps in the staffing in advance, not on the day
- The report is ready, you write the conclusions
- Development conversations have a fixed place, because planning stopped crowding them out
- The volume forecast rests on history, not on a hunch
- Meeting response times
fewer days on which the queue gets away from you
the signal comes during the queue, not from its summary
- Use of staffing
fewer idle hours and less overtime
staffing is planned against the forecast, not against the average
- A predictable rota
the team knows its rota in advance
building it stops being last-minute work
- Workload at peak
a peak stops being a surprise
the risky days are pointed out earlier
We start with visibility of volume, not with the rota.
- Step 1
The history of volume
How volume is spread over time, by channel and by topic. It usually turns out more predictable than the team assumes.
- Step 2
Signals during the day
A growing queue and cases exceeding the time. It works straight away and needs no change to the rota.
- Step 3
The forecast and the proposed staffing
With the decision entirely on the team lead's side. We measure its accuracy for several weeks before anyone starts trusting it.
- Step 4
Reporting and development
Summaries for the board and material for conversations with the team.
Common questions
Questions that come up at the first meeting
Is better staffing planning not simply a way to shrink the team?
It can be used that way and we will not pretend otherwise - but it is not what we propose. Forecasting volume is above all there so that staffing is not planned by feel, because then you pay twice: once in overtime, once in the queue. A team matched to the volume works more calmly, and with the turnover in customer service that is often worth more than saving a post.
Does this fall under the AI Act?
The AI Act names as high risk not only assessing employees but also allocating tasks on the basis of individual behaviour or characteristics. That line is closer than it seems - and that is why the scope stops before it. We work on volume, the queue and the competences available at positions, not on data about how particular people work. The proposed staffing says how many people with which qualifications are needed at a given hour; who actually takes the position is set by the team lead, and the arrangement of working time stays where it was - in the labour code, not in a tool.
Still have a question that is not here? Book a call
Next step
How many days last month did your queue get away from you?
We will show you what running a service team looks like when staffing is planned against a forecast and the queue reports itself during the day.