How Adherence Works¶
Schedule adherence compares what the published schedule says an agent should be doing with what the Daktela contact centre says they actually did β minute by minute, for every agent of a workplace. It answers two questions a supervisor asks every day: who is out of plan right now, and for how long? and how closely did the team follow the schedule yesterday, this week, this month?
Adherence is read-only. It does not change the schedule, it does not punish anyone, and it does not act on its own. It shows the numbers, explains every deviation, and lets a supervisor send a reminder.
Open it from Adherence in the left sidebar; an agent finds their own figures under My adherence. See Adherence screens for the views and Data, retention and privacy for what is collected and who can see it.
What is measured¶
Every published shift is a plan: blocks of queue work on a skill, breaks, training, and planned absences. The contact centre gives the actual: when the agent logged in, when they were ready and on which queues, which pauses they took, and which activities (calls, e-mails, chats) they handled.
WFM lays the two over each other and splits the shift into segments. Each segment is in adherence or out of adherence with a reason (see below). From the minutes out of adherence come two numbers:
| Number | Formula | Reads as |
|---|---|---|
| Adherence | 1 β counted time out of adherence Γ· scheduled time | "How much of the shift was spent as planned." |
| Time on queues vs. plan (conformance) | time actually spent on the queues Γ· queue time planned | "How much of the planned queue work actually happened." Over 100 % means more than planned. |
What is in the denominator. Scheduled time is the whole shift as published β queue blocks and breaks alike. A planned absence (an approved request) is not a shift and counts against nobody. A day without a shift is not measured. Minutes for which the contact centre delivered no data (an import outage) are marked No data and are never counted as out of adherence.
What is counted. Only stretches out of adherence after the tolerance (see rules below) are counted. The raw length of every deviation is still shown, so nothing is hidden; the tolerance only decides what goes into the number.
Short tasks inside a shift. A short task (for example packing 08:00β10:00) takes its own time out of the host shift: while it runs, the agent is measured against the task, not against the shift's own skill. The task adds no time β the scheduled time is still the host shift.
- A task whose skill has Daktela queues is queue work on those queues, like any other block of the plan.
- A task whose skill has no Daktela queue (work outside the contact centre) gets the benefit of the doubt: the contact centre cannot see that work, so the agent is in adherence for the whole task, whatever they do in Daktela. The time counts as scheduled time, but not as queue time planned.
- If the agent stays on the queues during such a task, Time on queues vs. plan goes over 100 % β they were on the queues for longer than the plan asked.
In the timelines, a task is a block of its own; hover over it to see Short task Β· Packing.
Info
Adherence is computed from the published schedule only. A draft schedule, or a change made to a day after it has been frozen, does not change the numbers. See Data, retention and privacy.
The four rules of a workplace¶
Each workplace has four rules, set on the Rules tab of the Adherence section (see Adherence screens). They decide how strictly the numbers are counted:
| Rule | Default | What it does |
|---|---|---|
| Tolerance of short deviations | 1 min | A deviation shorter than the tolerance is not counted at all. From a longer one, the tolerance is taken off. Set in minutes, 0β10 (0.5 = 30 seconds). |
| Move the break when a call runs into it | on | When a call runs over into a planned break and the agent then takes the whole break afterwards, the break moves with it and nothing is counted. |
| Mark as "Out of adherence, long" after | 5 min | After this long out of adherence, the agent is marked Out of adherence, long in the live view. It only marks β nothing is sent. |
| Adherence target | 94 % | Drawn as a line in the charts; team numbers below it are highlighted. |
The same tab has two more settings under Who sees what β Who sees individual agents and How far back others can look. They do not change how anything is counted; they limit who may read the figures. See Data, retention and privacy.
To see what a rule does before you save it, use Try the rules on an example day on the Rules tab: a made-up agent's day with five typical deviations, recomputed as you type.
Note
A change of rules applies from that moment on. Days already frozen in the history keep the rules they were computed with, so the history never changes under your feet.
States¶
In the live view every agent on shift has exactly one state right now:
| State | Meaning |
|---|---|
| In adherence | Doing what the plan says. |
| Within tolerance | Out of adherence, but for less than the tolerance β not counted yet. |
| Out of adherence | Out of adherence for longer than the tolerance. |
| Out of adherence, long | Out of adherence for longer than the "long" threshold. |
| No plan | Working (ready or on an activity) with no shift today, or during a planned absence. Shown, not measured. |
| Off shift | Outside the shift's hours, or not working on a day without a shift. |
| Time off | A planned absence. |
| No data | The contact centre delivered no data for this time. Never counted as out of adherence. |
Work done outside the shift's hours is not counted either way: it does not improve adherence and it does not count against it.
Reasons¶
Every stretch out of adherence carries one reason, and the reason says what the deviation did to the queue:
| Reason | What happened | Effect on the queue |
|---|---|---|
| Not logged in | Logged out while the plan has them on queue work. | β missing on the queue |
| Not ready | Logged in but not ready, with no pause set. | β missing on the queue |
| Pause instead of work | On a pause (or "do not disturb") while the plan says queue work. | β missing on the queue |
| Inactive (automatic pause) | The contact centre set the automatic pause after a missed call. | β missing on the queue |
| Wrong queue | Working or ready, but not logged into any queue of the planned skill. | 0 neutral |
The screens colour the reasons by whose doing they were: red for the agent's own (the four "missing on the queue" reasons), grey for Wrong queue, which comes from routing or the setup rather than from the agent.
Work during a planned break is not a deviation. It is kept as a note β Working instead of break, drawn blue β and counts as working extra in the Effect on the queue on the agent's page (worked extra / missing from the queue), so a day with a lot of extra work reads differently from a day with the same amount missing.
How contact centre states are read¶
The mapping between what the contact centre reports and what the plan expects is fixed. It cannot be configured, so every customer's numbers mean the same thing:
| The agent isβ¦ | β¦while the plan says queue work on skill X | β¦while the plan says break |
|---|---|---|
| On an activity (call, e-mail, chat) of a queue of X | In adherence | In adherence (noted as working extra) |
| On an activity of another queue, while logged into a queue of X | In adherence | In adherence (noted as working extra) |
| On an activity of another queue, not logged into any queue of X | Wrong queue | In adherence (noted as working extra) |
| Wrapping up after an activity | Follows the activity: in adherence after an activity of X or while logged into a queue of X, otherwise Wrong queue | In adherence (noted as working extra) |
| Ready and logged into a queue of X, no activity | In adherence | In adherence (noted as working extra) |
| Ready, but only on other queues | Wrong queue | In adherence (noted as working extra) |
| On a pause of their own (any name) | Pause instead of work | In adherence |
| On the automatic pause after a missed call | Inactive (automatic pause) | In adherence |
| On "do not disturb" (set from the phone) | Pause instead of work | In adherence |
| Logged in, not ready | Not ready | In adherence |
| Logged out | Not logged in | In adherence |
Rules worth knowing:
- A planned break belongs to the agent: whatever they do in it (rest, lunch logged out, or work) never lowers their adherence.
- An agent logged into the planned queue is in adherence, even while the contact centre routes them work from another queue. Only an agent who is not logged into any queue of the planned skill is on the Wrong queue.
- Ready on the right queue counts as working, even with nothing to handle. Adherence measures whether the agent was available as planned, not how busy the queue was.
- The system pauses are not the agent's own pauses. During planned queue work, the automatic pause after a missed call counts as Inactive (automatic pause) and "do not disturb" as Pause instead of work.
- A skill is tied to the contact centre queues of its WFM queues on the workplace. Set the skill's Daktela queue (or merge several queues into one skill) under Queues; a skill with no queue of its own counts every queue of the workplace as the right one.
What adherence does not do¶
- It does not send anything on its own. The only message to an agent is the Remind button a supervisor presses, and it goes once per agent per two minutes at most.
- It does not notify supervisors, escalate, or score people. The "long" threshold only marks a state, and the agent lists are in alphabetical order, not a ranking.
- It does not let anyone edit, excuse or annotate a deviation. What the contact centre reported is what is shown.
- It does not recompute the past. A day is frozen three hours after its last shift ends; later changes to the schedule or the rules do not reach it.
- It does not count work outside the shift, and it does not measure days without a published shift.
Requirements¶
- The Daktela CC integration with a call centre whose purpose includes data, and a valid token.
- Every agent to be measured has their Daktela username and call centre filled in on their WFM user. An agent without them is skipped and shown as No data.
- A published schedule for the workplace. Draft plans are not measured.
- Skills linked to the contact centre queues they answer (Queues), so that "the right queue" is known.
- Roles: administrators and HR see every workplace, planners the workplaces they belong to, and all three edit the rules; a Team leader sees the workplaces they belong to, reads the rules and may send reminders; an Agent sees only their own day and history. The workplace's Who sees what settings can narrow this further (see Data, retention and privacy).
Setup check¶
Adherence is only as good as two pairings: each agent with their contact centre login, and each planned skill with the contact centre queues it stands for. When one of them is missing, the agent's figures are wrong although they are working β shown as No data, or counted as Not logged in or Wrong queue. The setup check finds these cases for the selected workplace and tells you how to fix them. It does not change how adherence is counted.
- When something is wrong, a banner appears above the tabs: red Adherence figures are not reliable for errors, orange Adherence figures may not be accurate for warnings, followed by the names of the findings.
- Click ? in the banner to see each finding: what it means, which agents, skills, queues or call centres it concerns, and how to fix it. Open takes you to the settings screen where the fix is made.
- In Day and Live, a warning icon next to an agent's name marks agents whose figures are affected (red = wrong for sure, orange = may be wrong). On an agent's page, the banner shows only the findings about that agent.
- The check looks at the published shifts of the last and the next 7 days and at the data imported from the contact centre in the last 7 days. Agents themselves do not see it.
| Finding | Severity | What to do |
|---|---|---|
| Skill without Daktela queues | Error | In Queues, add the skill to a queue assigned to the workplace and map that queue to the Daktela queues the agents work on. |
| Agent without a Daktela login | Error | In Users, fill in the agent's Daktela username. |
| Inactive agent with a published shift | Error | Activate the user, or remove their shifts from the published plan. |
| Agent without a call centre | Error | In Users, assign the agent to their call centre. |
| Call centre not set up for data | Error | In Call centres, set the purpose to Data or Both, the URL and the API token. |
| Import from the contact centre is failing | Error | Check the call centre's URL and API token; if they are right, contact Daktela support. |
| Data from the contact centre is out of date | Warning | The last successful import is older than 15 minutes, or there has been none. Check that the adherence import service is running on the server, or contact Daktela support. |
| No data for an agent | Warning | The agent had shifts but the contact centre sent nothing for them β compare their Daktela username with their login in Daktela. |
| Work on a queue that is not mapped | Warning | Map the queue in Queues if the work on it is planned work. |
| Logged in only to unmapped queues | Warning | Map the queues in Queues, or log the agents into the queues of their planned skills in Daktela. |
| Activities without a queue | Warning | Activities that have no Daktela queue (for example tickets or outbound calls) cannot be matched to a skill and count as Wrong queue unless the agent is logged into a queue of the planned skill. No setting fixes this yet; take it into account when reading the figures. |
Note
With Who sees individual agents (Rules, section Who sees what) set to admins and the agent's own team leader only, the four findings that come from what agents did β No data for an agent, Work on a queue that is not mapped, Logged in only to unmapped queues and Activities without a queue β name only the agents you may see individually; the others are only counted.