Adherence Screens¶
The Adherence section in the left sidebar has four tabs β Live, Day, History and Rules β and a page for every agent. An agent sees My adherence in the sidebar instead: their own page, as My day and My history.
At the top of every tab:
- Workplace β shown only when you may see more than one workplace. The choice is kept in the address bar, so a link opens the same workplace, and remembered for next time.
- Agent group β All agent groups plus one option per agent group. Live, Day and History filter by the group chosen; the filter is not shown on Rules, nor when the workplace has no agent groups.
- The banner of the setup check, when it has found something.
Note
Every number is computed from the published schedule only. The subtitle of the section says so.
When the workplace shows individual agents only to admins and their own team leader (see Who can see what), everyone else gets the team's numbers on Live, Day and History, and the note This workplace shows individual agents to their team leaders only. in place of the list of agents.
Live¶
How the team is doing right now. The view reloads after every import run (about once a minute), and at least once a minute on its own. Nothing on it counts up: a state shows the time it began. Above the tiles, Data as of HH:MM says how fresh the data is; it turns orange with older than 3 minutes when the import falls behind.
Tiles
- Adherence today (until HH:MM) β the workplace's adherence so far today, against the target.
- In adherence now β of the agents with a plan now, and how many more are working without one.
- Out of adherence now β of which long (at least the "long" threshold), and how many are still within the tolerance.
- On the queue now β ready or working, of the agents planned on a queue.
Agents now is the distribution of states as a stacked bar. Queue coverage now shows, per skill, how many of the agents planned on it now are doing what the plan says (2 of 3 planned), and how many others, not planned on it, are ready or working on it (+1 more on it).
Agents lists everyone with a shift today or working without one, in alphabetical order β a list to help someone, not a ranking. Red marks the agent's own doing, grey that they are not logged into the planned queue (routing or the setup).
| Column | Meaning |
|---|---|
| Agent | Name and groups. An agent who is Out of adherence, long through their own doing has a red edge. A warning icon is the setup check's. |
| State | The state right now. Within the tolerance, hover it to see until when the tolerance runs. |
| Since | When the current state began. |
| Plan now | The planned block and its hours. |
| Actual now | What the contact centre reports: ready or working on which skill, the pause they took, logged in but not ready⦠|
| Reason | Why the agent is out of adherence; Works without a schedule for an agent with no plan. |
| Today | Today's adherence so far. |
| Next | The next planned block and when it starts. |
| (actions) | The bell sends a reminder; the dots (or a click on the row) open the agent's page. |
Filter by State (Everyone, Out of adherence / within tolerance, In adherence, Off shift / no plan) or Search an agent by name.
Day¶
One day of the workplace. At the top choose the Day, the Range (Whole day, Morning, Afternoon) and Only agents with a deviation.
The team comes first β The team on β¦ (or the group's name): Team adherence, Time out of adherence of the time planned, Time on queues vs. plan and Agents planned. While the day is still running the card says Adherence until HH:MM and carries a Provisional label: the day is not frozen yet and the numbers can still change.
Agents follow in alphabetical order, one row per agent. On the left: the name (click it to open the agent's page with that day), the groups, the day's adherence, the time out of adherence and its biggest reasons with their length, coloured by whose doing they were. Incomplete data on a row means the import had a hole that day.
On the right, three lanes on a shared time axis:
- Plan β the effective plan: queue blocks in the colour of their skill, breaks, time off hatched. A break that was moved because a call ran into it has a dashed outline and is marked β¦.
- Actual β what the agent did: ready or working on a skill's queues, a break or pause, logged in but not ready; empty means logged out. The contacts handled are in the tooltip.
- Adherence β the verdict: green in adherence, Thanks to a rule when a rule forgave the deviation, yellow within the tolerance, red out of adherence through the agent's own doing, grey out of adherence because of routing or the plan, blue when the agent worked through a break (still in adherence), grey without a plan, hatched without data.
The legend above the lanes repeats these colours. Hover any block for the details: the planned hours, the reason of a deviation, its length and the time counted after the tolerance, and the effect on the queue. A βΌ marks a reminder that was sent.
History¶
The workplace or group over the Last 5 working days or Last 10 working days β the days with a published shift β or any range (From β to). Only frozen days are included; today is never in.
- Three tiles β Average adherence against the target (the β shows the rules the days were computed with, and says when they changed inside the period), Time on queues vs. plan, and Time out of adherence with the number of deviations.
- Adherence by day β a line chart with the target line; a day under the target is a red dot. Show as table lists the same days. Click a day to narrow everything below to it; the chip Day: β¦ with its β clears the choice.
- Reasons for deviations β the time out of adherence per reason, as bars. Red: up to the agent Β· blue: worked more than planned Β· grey: routing or other work.
- Agents β the period (or the day chosen) β in alphabetical order, with Adherence, a Trend sparkline, Time on queues vs. plan, Deviations, Time out of adherence and the Most frequent reason. Click a person to open their page with the selected day. A
*after the adherence marks a day with incomplete data. - Export CSV β one row per agent and day: Workplace, Agent, Agent group, Day, Adherence %, Conformance %, Deviations, Out of plan (min), Plan (min). Semicolon-separated, opens in Excel. When individual agents are hidden from you, it has one row per day for the Whole team instead.
A range that reaches further back than How far back others can look allows is cut at that limit.
Rules¶
The workplace's rules, with an example day below them so you can see what a rule does before you save it. Administrators, planners and HR edit; a team leader sees the form read only.
- Adherence rules β Save is in the card's header. Two sentences on top say what always holds: a planned break belongs to the agent, and an agent logged into the planned queue is in adherence even while the contact centre routes them work from another queue (see How adherence works).
- How time out of adherence is counted β Tolerance of short deviations (0β10 min, e.g. 0.5 = 30 seconds), Mark as "Out of adherence, long" after (1β60 min), Adherence target (50β100 %) and Move the break when a call runs into it.
- Who sees what β Who sees individual agents (Everyone who manages the workplace, or Only admins and the agent's own team leader; planners and HR see team totals) and How far back others can look (7β365 days). Agents always see their own adherence. See Data, retention and privacy.
- Try the rules on an example day β a made-up agent and day, recomputed as you type: Adherence, Time on queues vs. plan, Time out of adherence, the lanes, and the deviations AβE with What happened, Length, Counted and Why. Nothing is saved until you press Save.
Validation errors are shown in a message naming the field. A change applies from now on. Frozen days keep the rules they were computed with; the form says so, and so does the confirmation after saving.
The agent's page¶
The same page for the planner and the agent. A planner opens it from a row of the Live, Day or History views, and gets a bar on top: Back (to where they came from), the agent's name and groups, Another agent (the agents of the workplace whose page they may open), and Remind; the setup check shows its findings about this agent. The tabs are Day and History. An agent opens My adherence from the sidebar and sees My day and My history without the bar; the texts speak to them directly.
Day / My day
- Now by the plan β the planned block, the state and since when. When out of adherence: By the plan β¦ should be on: β¦ Now: β¦, the reason (Why: β¦) and, within the tolerance, until when it is not counted.
- Next activity β what comes next and in how long, or End of the shift.
- Adherence today β the number against the target, the time out of adherence and the number of deviations.
- The day β the three lanes, named, over the shift Β± 1 hour.
- Deviations β When, Length, Counted (after the tolerance) (0 s so far (within tolerance) while a deviation is still within the tolerance) and Why.
When nothing came from the contact centre for the shift, a note says whether the agent was not logged in at any time (counted) or there is no data for them (not counted either way).
A day opened from the Day or History view with a date in the past shows that day as frozen, with Adherence, Time on queues vs. plan, Time out of adherence and Effect on the queue (worked extra / missing from the queue), and a Today button.
History / My history
The last 5 or 10 working days of the workplace: four tiles (Average adherence, Time on queues vs. plan, Time out of adherence, Days worked of the working days), the chart, the reasons, and a table of Days β a day without a shift is greyed as no schedule. Click a day (the latest worked day opens by itself) to see it in detail: its numbers, Effect on the queue, the lanes and the deviations.
Reminders¶
The bell in the Live view and Remind on the agent's page send one message to the agent's Daktela agent interface β a toast that also reaches the mobile app. It says what the schedule wants and what the agent is doing instead, in the agent's language, for example: By the schedule you should be on: Support (08:00β16:30). Now: Pause: Lunch.
- Only an agent who is out of adherence or within the tolerance can be reminded; otherwise the button is disabled.
- One reminder per agent per two minutes. A second one is refused with a message.
- WFM confirms Reminder sent β β¦ will see it in the Daktela agent interface. and draws a βΌ at that moment on the agent's lanes, in the Day view and on their page.
- Who sent what to whom and when is recorded. There is no automatic reminder, no repetition and no escalation.