Skip to content

Adherence: Data, Retention and Privacy

Adherence works with data about individual employees β€” when they were logged in, on which queues, which pauses they took and what they handled. This page says what WFM collects, where it comes from, how long it is kept and who can see it, so that you can inform your employees and your data protection officer.

Warning

This page is a technical description, not legal advice. Monitoring how employees spend their working time is processing of personal data and, in most countries, requires that employees are informed in advance; in some it requires the agreement of employee representatives. Have your own legal counsel review your obligations before you switch adherence on for a workplace.


What is collected

WFM reads these records from the Daktela contact centre for every WFM user who has a Daktela username and a call centre set, and for nobody else:

Record What it holds
Login sessions When the agent logged into the contact centre and logged out.
Ready sessions When the agent was ready to take work and when not.
Queue sessions Which queues the agent was logged into, and when.
Pause sessions Which pause the agent set (its name and type, whether it is paid) and for how long.
Activities That the agent handled a call, e-mail, chat or other activity, on which queue and from when to when.

For activities WFM stores the time, type and queue only β€” never the customer, the phone number, the subject or the content of the conversation.

From these records and the published schedule WFM computes, for every agent and day, the segments in and out of adherence, the reasons, the counted and raw minutes, and the two numbers (adherence and conformance). A supervisor's reminder is recorded too: who sent it, to whom, when, what the agent's state was and the text delivered.


Where it comes from

The records come from the Daktela contact centre's API, through the same call-centre connection and service token WFM uses for the forecast. WFM reads them about once a minute, taking only what changed since the previous run. Nothing is written back to the contact centre except the reminders a supervisor sends.


How long it is kept

Data Default retention Note
Raw session and activity records 14 days Needed only to compute the days that are still open. Deleted by the import's retention step.
Frozen days (per agent and day: the lanes, the segments, the numbers, the rules of the day) 13 months What the History shows. Deleted by the hourly freeze's retention step.
Reminders sent kept A record of who wrote to whom. Deleted together with the agent's user account.
Workplace rules kept Configuration, not personal data.

Both retention periods are command options of the respective job and can be shortened by your administrator (adherence_import --retention-days, adherence_rollup --retention-months). Deleting a WFM user deletes their adherence records with them.

When a day is frozen

A day is frozen three hours after its last shift ends and is then stored as it was. Until then it is provisional: the live and day views compute it from the raw records on request and the numbers may still change. A frozen day is never recomputed by itself β€” not when the schedule changes afterwards, not when the rules change, not when WFM is updated. An administrator can rebuild a single day deliberately, and that action is logged.


Who can see what

Role Sees
Administrator, System administrator, HR Every workplace; edit the rules.
Planner for a workplace The workplaces they belong to (and their subordinates' workplaces); edits their rules.
Team leader The workplaces they belong to (and their subordinates' workplaces); reads the rules; may send reminders.
Agent Only their own day and history (My day, My history). Nothing about anyone else.

Each workplace narrows this further with two settings on the Rules tab, section Who sees what:

  • Who sees individual agents. With Everyone who manages the workplace (the default), everyone above sees every agent of the workplaces they see. With Only admins and the agent's own team leader; planners and HR see team totals, an agent's own figures are seen only by administrators and system administrators and by the team leader who is the agent's superior in WFM; planners, HR and other team leaders see the team's numbers, without the list of agents. A team leader with no subordinates set in WFM then sees team totals only.
  • How far back others can look β€” 7 to 365 days, 90 by default. Older days in Day, History and the agent's page are closed to everyone except the agent; a History range is cut at the limit.

Agents always see their own adherence: neither setting limits what an agent sees about themselves.

A request outside the role's scope, an agent you may not see individually or a day beyond the limit is refused, never answered with an empty list; team totals are always computed over all agents. There is no export of raw session records; the History export contains per-day numbers only, and with individual agents hidden only one row per day for the whole team.


Informing your employees

Most jurisdictions require that employees know that their working time is monitored, what is recorded and why, before it starts. For example:

  • In the Czech Republic, section 316 of the Labour Code requires the employer to inform employees about the scope and the manner of monitoring, and limits monitoring to what a serious reason in the nature of the employer's activity justifies.
  • In Germany, the introduction of a system that can monitor employees' behaviour or performance is subject to the works council's co-determination (section 87 (1) no. 6 of the Works Constitution Act, BetrVG); a works agreement is the usual form.
  • Under the GDPR, this is processing of personal data: it needs a legal basis (typically the employer's legitimate interest in running the contact centre, or the employment contract), a purpose stated in your records of processing, and information to the data subjects (Articles 13 and 14).

A short notice that covers what this page describes is usually enough. The text below is a starting point for your own; adapt it to your situation and have it reviewed:

Template notice for employees

Our workforce management system compares your published shift with your activity in the Daktela contact centre β€” when you are logged in, ready, on a queue, on a pause or handling a contact β€” to measure how closely the team follows the schedule. The content of your calls and messages is not part of this. The records are kept for 14 days and the per-day results for 13 months. Your team leader and [the planners of your workplace] can see your results for the last [90] days; you can see your own under My day and My history. The system does not act on its own; your team leader may send you a reminder through the Daktela agent interface when you are out of plan. The processing is based on [legal basis] for the purpose of [purpose]. Questions and requests regarding your data: [contact].


Switching it off

Adherence is available for every workplace of an instance that has the contact-centre integration. To stop measuring a workplace, remove the Daktela username from its agents' WFM users, or revoke the service token of the call centre; the raw records then expire with their retention and the frozen days with theirs. Deleting a user deletes their records immediately.