T Telefónica Approved
Number of calls40
Adjusted
Customer service planning at Telefónica Germany means building forecasts, aligning capacity, distributing volume, working in corrections and coordinating approvals. That work spans many planning units, external service partners and operational time slots. Unetiq built Callmart for this job together with Telefónica's planning experts. The custom planning platform brings forecasting, capacity reports, volume distribution, partner corrections, approvals and budget control into one system. Callmart turns a chain of handovers into a planning process that is easier to check, steer and develop further.
Telefónica Germany is one of the major telecoms companies in Germany. Its customer service operation coordinates large planning volumes, internal planning teams and external service partners.
Planning runs from monthly figures down to operational time slots, in some cases in 30-minute intervals. Later corrections, approvals and budget effects have to match the planning version they belong to.
Illustrative example. One planning question: how many calls about contract changes will call center B get on Tuesday the 14th between 10:30 and 11:00? That is one square. Asked for every half hour of the day it becomes 48 questions, for every day of the month 1,488, at all 4 call centers 5,952, and for all 6 topics 35,712 questions a month. The final picture shows them as 24 heatmaps, 4 call centers by 6 topics, each a month of half hours, with the first question as one outlined square among them.
Much of the coordination ran through Excel files, emails and manual handovers between teams, service partners and systems. That worked for individual steps. For end-to-end planning it cost time and care.
Excel still makes sense in places as an import and working format. The trouble came from checks, corrections, versions and approvals being scattered across files and messages.
Teams had to transfer, check, reconcile and redistribute data again and again. Changes were hard to trace, coordinating with external service partners took effort, and forecasts did not feed straight into operational decisions.
Most standard tools cover one slice: forecasting, workforce management, reporting or budgeting. Callmart had to cover the handovers between them, linking forecasts, capacity planning, volume distribution, coordination with service partners and budget planning. Otherwise the same exports, alignment rounds and checks would have resurfaced somewhere else.
The platform also had to fit how Telefónica actually plans, with its own work units, external service partners, correction loops, approvals, roles and budget control.
The scope is deliberately tight. Callmart covers the planning and control process that used to be split across forecasts, partner coordination, corrections and budget planning. It does not try to replace a full shift-planning system.
Internal planning teams and external service partners work in Callmart with different roles and permissions. Based on forecasts and reported capacity, Callmart distributes service volume across internal and external units. Planners compare scenarios, factor in capacity and see early how a decision affects service levels, targets and budget.
Partners submit feedback and corrections in a structured format. Telefónica reviews, adjusts and approves. Every version stays traceable in the system.
Illustrative example: one figure, calls for call center B, in three versions kept side by side as tabs. Version 1, the plan by Telefónica: 42 calls. Version 2, the service partner's correction: 36 calls. Version 3, adjusted and approved by Telefónica: 40 calls.
Familiar ways of working stay where they help, and Excel can still be used as a format. Data, checks, versions and approvals now run through one shared process, so files and emails are no longer the main handover point.
Callmart consists of a web platform and a connected forecasting service. The web platform controls who can view, change, comment on or approve which data. Corrections and approvals are versioned, so every planning state can be traced.
Machine-learning models produce the forecasts inside the planning process. Nobody has to export forecasts and process them by hand. The system distributes, checks and corrects them, and teams use them for operational and budget control.
Chart with synthetic data for one week at 30-minute resolution. The forecast line follows the actual contacts closely: higher on weekdays, peaks in the morning and afternoon, closed at night, a drop on a Thursday public holiday, a bump during a Tuesday campaign and a slight upward trend from customer development. In the animation, a cursor sweeps the week and actual contacts are drawn in half hour by half hour along the forecast; the public holiday lights up as the week reaches it.
For strategic planning, Callmart brings forecasts, capacity, targets and budget figures together in shared overviews. Planners base their decisions on resources, service targets and financial impact on these views.
Diagram of six planning steps, stacked top to bottom and connected by arrows: machine-learning forecast, capacity, service volume distribution, partner feedback and corrections, review and approval, and budget control. A correction loop on the right leads from partner feedback and corrections back to distribution. In the animation, planning values flow continuously along the arrows, go around the correction loop twice, then continue to approval and budget control.
The hardest part was fitting many small planning rules into one system without overwhelming users with that complexity.
Every change had to stay traceable. Who supplied which figures? What was corrected? Which version is approved? Which version does the next step build on?
The first trade-off was familiarity versus control. Teams knew their Excel-based ways of working, and some of them remained useful. Checks, versioning, roles, approvals and traceability still had to come together in one place.
The second trade-off was scope. Callmart focuses on the part of the process where Telefónica most needed integration, and leaves out the feature set of a full workforce-management or shift-planning system.
The results validated so far show three effects:
The planning teams' work has changed too. They spend less time on manual coordination and data reconciliation and more on scenarios, risks and operational decisions. Forecasts now actively drive planning decisions.
Day to day, teams copy less between files and systems, coordinate more clearly with external service partners, can trace changes, and have more time for analysis and control.
For us, the biggest value is that we no longer manage individual forecasts, files or budgets, but the connections between them. Callmart helps us keep a high level of planning complexity under control and turn data into concrete decisions.
Michael Lang
Project Lead at Telefónica
Unetiq has been developing Callmart as an operational platform for several years, following Telefónica's planning requirements. New control needs are added as they come up. Over time, the planning platform has become a decision platform for forecasts, capacity, volume distribution and budget control.
When business processes are spread across many tools and handovers, custom software often achieves more than standard tools alone. That takes a development team that understands the process, the decisions and the handovers in detail. The result is software people actually use every day.
We'll tell you straight if we're the right fit, what it'll take, and what it'll cost.
You ate the whole website.
We honestly didn't think anyone would get this far.
You're probably bored.