Contact centre Forecasting & staffing Custom

Custom contact centre workforce management software

Appfront builds custom workforce management for contact centres. Historical contact volume is translated into a forecast per interval, which gives the staffing required per channel and skill, which in turn gives a schedule that meets the agreed service level. During the day you can see whether the plan still holds. Get in touch to go through your situation.

What is contact centre workforce management?

Workforce management for a contact centre is the chain of forecasting, calculating, scheduling and adjusting. First you forecast how many contacts arrive per half hour, per channel. Then you calculate how many people you need to achieve an agreed waiting time — which is not a linear sum, because queues do not behave linearly. Next you create a schedule that fits, and during the day you check whether reality follows the plan.

That is fundamentally different from ordinary staff scheduling, where the number of people needed is known and the puzzle is who works when. In a contact centre, that required number is the hardest question, and it changes every half hour.

Appfront builds this as custom software with an integration to your telephony or contact centre platform, so the forecast runs on your own history and actuals flow in automatically during the day.

Forecast per interval and channel

Volume per half hour based on history, seasonal patterns, weekdays and known events such as a campaign or an invoice run.

Staffing that respects the queue

Calculation of the required staffing based on queueing behaviour rather than an average, including allowances for breaks, meetings, training and absence.

Adjusting during the day

A comparison of forecast and actual volume per interval, with alerts when the service level is at risk and there is still time to act.

WFM or workforce scheduling? Where the line falls

Appfront builds both, and the difference is bigger than it looks. It comes down to what is unknown.

This page

The staffing requirement is unknown

The number of people you need follows from a forecast workload and an agreed service level, and it changes every half hour. Forecasting, staffing calculation and intraday management are the core; the schedule is a result.

Other pages

The staffing requirement is known

You know how many people are needed and want to build schedules around skills, contracts and preferences. In that case, look at workforce scheduling software or, for visual planning of people and resources, planning board software.

Our development process for your WFM system

WFM stands or falls with the quality of the historical data. We therefore start with your own data and test whether the forecast holds up before any schedule comes out of it.

1
Discovery & analysis

We pull historical contact volume from your telephony or contact centre platform and check whether it is usable: does it include channels, skills and handling times, and are exceptional periods recognisable? We also record which service level applies per channel.

2
Design

We design the forecasting model, the staffing calculation, the scheduling rules within your collective labour agreement and contract types, and the intraday screens for the traffic manager.

3
Build and iteration

We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.

4
Go-live & maintenance

A controlled go-live with validation and a safety net, followed by ongoing maintenance, monitoring and further development as your channel mix or service agreement changes.

What custom WFM delivers in practice

What you need differs per contact centre. These are the components that come up most often.

Forecast per channel and skill

Half-hourly forecasting for telephony, chat, email and messaging, with different handling characteristics per channel and the option to adjust manually for known events.

Staffing calculation

Translation of volume and handling time into the required staffing at a given service level, with configurable allowances for breaks, meetings, training and absence.

Skills-based scheduling

Schedules that take into account who is proficient in which channel and skill, with contract types, collective agreement rules and employee preferences.

Intraday monitoring

A comparison of plan and reality per interval, showing who is logged in, how much deviation there is and which measure can still make a difference.

Adherence and quality

Insight into how far actual behaviour deviates from the schedule, intended to improve the plan, not to hold employees to account over minutes.

What-if scenarios

Calculating what happens with higher volume, a shorter handling time or extra staffing, so you can make well-founded decisions on recruitment or outsourcing.

Typical use cases in practice

WFM pays off as soon as contact volume fluctuates and staffing is a substantial cost item.

Customer service at service providers

Energy, telecom and insurance companies, including health insurers, with sharp peaks around invoicing, policy renewals and outages.

Outsourced contact centres

Providers that work for multiple clients and must serve a different service level and skills mix for each one.

Public services

Municipalities and public-sector agencies with predictable peaks around benefit schemes, tax assessments and seasonal applications.

Webshops and retail

Organisations with a strong seasonal pattern and campaign peaks, where temporary staff need to be deployed at the right moment.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology we use

The calculation engine is the distinctive part; the rest is an ordinary web application with integrations. The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can maintain and develop further, with no dependence on per-user licences.

React / Vue front end Node.js / Python / PHP / .NET PostgreSQL / MySQL REST & webhook APIs OAuth 2.0 / SSO Integration with telephony/contact centre platform Time-series models

Why choose Appfront for your WFM system?

Appfront builds custom software for a wide range of organisations in the Netherlands. With WFM, we start with your own history and test the forecast after the fact against what actually happened. Only when that holds up does a schedule based on it mean anything.

We keep the calculation core explainable. A staffing recommendation that nobody can retrace gets overruled by the team leader who thinks they know better, and then you're back to square one.

On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.

Also see our broader services around custom software, staff scheduling software and helpdesk software. Unsure about the approach? Get in touch.

Security and privacy in your WFM system

A WFM system processes schedules, availability, absence allowances and performance data of individual employees. Appfront builds in line with the OWASP ASVS and with the GDPR as its starting point, using role-based access: a team leader sees their own team, not the whole organisation.

Adherence and performance data are sensitive and affect the rights of the works council. We prefer to show them in aggregated form, only make individuals identifiable where that has been agreed for a functional reason, and document the data flows for your record of processing activities.

More about our approach to security: information security policy and CVD policy.

  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access following least privilege
  • Audit trail of views and changes
  • Secrets in a secure vault, not in code
  • Documented data flows for your processing register
  • Performance data shown in aggregated form by default

Frequently asked questions about contact centre workforce management software

Answers to the questions we get asked most often.

The chain of forecasting, calculating staffing requirements, scheduling and adjusting during the day. What makes it special is that the number of people needed differs for every half hour and follows from a forecast workload and an agreed waiting time. That is a calculation problem that ordinary scheduling software does not solve.

Because queues do not behave linearly. Twice as many calls with twice as many people does not give the same waiting time, and the last few percent of service level cost disproportionately much staffing. An hourly average also hides peaks within that hour. That is why we calculate per interval, using a model that accounts for queue behaviour.

Historical contact volume per interval and channel, average handling time and after-call work time, and the schedules for the period in question. This usually comes from your telephony or contact centre platform. The longer the history, the better the seasonal pattern can be recognised, but we first check whether the data is usable before promising anything.

Yes, but with different calculation rules. Chat involves concurrent conversations per agent, and email is deferred work that must be completed within a deadline, which is a different kind of calculation from a telephone queue. We model per channel and add up the required staffing based on who has which skill.

Yes, and that matters for buy-in. Preferences, availability and swap requests can be built into the model, within the limits of the collective agreement and contract. The system shows what a preference costs in staffing, so the conversation about it is based on facts rather than gut feeling.

With restraint. Adherence is useful for seeing whether the plan was realistic and where something is structurally going wrong, but it becomes harmful as soon as employees are judged on minutes. We design reporting at team level and by pattern, and discuss in advance with you and the works council what is and is not shown in an identifiable way.

Yes, this is one of the most-used features. You can calculate what happens with higher volume, a shorter handling time after a process improvement, or extra staffing in a particular period. That gives a recruitment request or a conversation with a client solid backing.

There are strong WFM packages, especially for large contact centres, and they are often the right choice. Custom software pays off for a mid-sized centre where such a package would be heavy and expensive, for an unusual mix of channels or skills, or when you want to integrate with a contact centre platform that the standard packages do not support.

Ready to build your workforce management software?

Tell us which channels you handle, which service level applies and where staffing is currently going structurally wrong — we are happy to think along on scope, integrations and the first version. A no-obligation first conversation gives you a clear picture of the possibilities and whether custom software pays off in your situation.

Edit content