Team

Agent scorecard, occupancy and floor standings: how to read your team fairly

The SautiDesk team
11 November 2026 · 9 min read

The short answer

An agent performance report should show each person against the floor, not against each other. SautiDesk Pro's People reports give an Agent scorecard, Occupancy, Floor standings, Availability and breaks, and Transfers. Occupancy is talk plus wrap time over the time an agent could have taken calls, and it excludes breaks and non-phone work.

An agent scorecard is one row per person showing calls answered, call length, tickets closed and time signed in, set against the floor average. SautiDesk's People group has five reports for reading a team: the Agent scorecard, Occupancy, Floor standings, Availability and breaks, and Transfers. This guide gives the formula behind each figure, what to say in a one-to-one, and what not to conclude.

All five need SautiDesk Pro at KES 3,000 per person a month and the Reports access, and they open on a computer. Each takes a date range and compares it with the period before. Today is partial, because it is counted up to now.

The Agent scorecard

The scorecard has no headline strip. It is one table, "By agent", with a Floor row of totals. The page asks you to read each row against the floor, not against each other.

The Agent scorecard, column by column
ColumnHow SautiDesk calculates it
AnsweredInbound calls the agent answered in the range
OutboundOutbound calls the agent made in the range
Average call vs floorAnswer to hang-up over the agent's answered calls, holds included, drawn as a bar with the floor average as a line
First contactClosed tickets that needed one touch and had no follow-up ticket inside the repeat window, divided by tickets closed
Missed while freeCalls that rang this agent as no answer or busy while their status was Available
Signed inTime in any state except offline, within the range and up to now

The CSV also carries the average wrap time, hang-up to the wrap-up being submitted, and Tickets closed. Tickets are credited to the ticket's current owner. Sort the table by Most calls, First contact or A to Z. An average call that runs more than 35% above the floor, once an agent has three or more answered calls, is flagged amber.

What not to read into the scorecard

  • A long average call is not a slow agent by default. Hard calls often go to the best agent, and holds are inside the average.
  • Missed while free counts only calls that rang an agent who was Available. It does not count calls that rang while the agent was busy or away.
  • Only agents with a call, a closed ticket or status history appear. A person who did none of these in the range has no row.
  • The chart "Do longer calls close more on first contact?" is a hint. It appears when at least three agents have both figures, and it plots one dot per agent.

Occupancy

Occupancy is the share of the time an agent could have taken calls that they spent talking or wrapping up. SautiDesk calculates it as (talk + wrap) ÷ (signed in − away − non-phone). It also shows utilisation, which divides the same talk and wrap time by all signed-in time. Both read the agent status history, kept since 8 September 2026.

Occupancy and utilisation with an example: one agent signed in for 480 minutes
FigureFormulaExample
Signed inTime in any state except offline480 min
Away and non-phoneBreaks and work off the phones, left out of occupancy60 + 30 = 90 min
Time available for callsSigned in − away − non-phone390 min
Talk + wrapTime on calls plus time wrapping up200 + 40 = 240 min
Occupancy(Talk + wrap) ÷ time available240 ÷ 390 = 61.5%
Utilisation(Talk + wrap) ÷ signed in240 ÷ 480 = 50.0%

The report's strip has Floor occupancy, Utilisation, Running hot and Waiting for calls. Running hot counts agents at 85% occupancy or more, and their rows are tinted. The table has Agent, Signed in, Talk, Wrap, Waiting, Away, Occupancy and Utilisation, and a chart shows where each person's time went.

  • Occupancy leaves out breaks and non-phone work. An agent on a long lunch does not lower their own occupancy, and the Away column shows the time instead.
  • Above about 85% for a long stretch means the team is running hot. That is the report's own marker, and a supervisor decides what to do about it.
  • On a one-day range, treat the numbers as a hint. The report says so itself: one day of a few people is not a pattern, so check a month before acting.
  • A low figure means the agent was Available while few calls rang. Read the Waiting column beside it.

Pair "occupancy rate" with the phone, because the same words describe hotel rooms. For the staffing side, see how many agents you need.

Floor standings

Floor standings ranks agents on tickets that stay closed, not on how many calls they took. The strip shows Top of the board, Biggest climb, First contact and Stayed closed, and the table has Rank, Agent, Points, Stayed closed, First contact, Answered and Move. Move compares the rank with the period before of the same length.

How Floor standings points are built, with an example of one agent
PartFormulaExample
First contact30 × first-contact closes ÷ tickets closed30 × 16 ÷ 20 = 24
Stayed closed20 × (1 − tickets that came back ÷ tickets closed)20 × (1 − 2 ÷ 20) = 18
Volume10 × answered calls ÷ the most answered on the floor10 × 40 ÷ 80 = 5
PointsSum of the parts ÷ the most they could score (60) × 100, rounded47 ÷ 60 × 100 = 78

"Stayed closed" means the ticket was not followed by a new ticket inside the repeat window. Volume is deliberately worth the least. An agent who closed no tickets in the range is scored on call volume alone, so read a high score next to the Stayed closed and First contact columns. Ties go to the higher points, then by name. A chart, "How each score is made", splits each bar into the three parts.

Availability and breaks

Availability and breaks answers why nobody was on the phones at a given time. It has two views: Timeline, with each agent's day drawn out, and "At a moment", which shows each agent's state at a time you pick or at the moment of a call from the call log. Neither is a stopwatch on people.

Headline figures and the break log in Availability and breaks
PartWhat it shows
Signed inAll agents' signed-in hours; offline time is excluded
On a call, Available, AwayEach state as a share of signed-in time; Away counts breaks
Break overrunsBreaks that ran past their usual length
Thin coverStretches of five minutes or more with someone signed in and two or fewer Available
Break logAgent, Started, Length, Usual, Overran and Others on the phones

A break is an Away or off-the-phones span, counted on the day it started. The report holds usual lengths for three reasons: Lunch is 45 minutes, Tea 15 and Bathroom 5. A break with any other reason has no usual length, so it cannot overrun. An agent counts as offline when the console closes or stops checking in for 90 seconds. The "At a moment" view has no CSV or comparison.

Transfers

Transfers shows who hands calls to whom and what each hand-over costs the customer. The strip has Transfers (as a share of answered calls), Passed on twice, Extra wait added and Solved the same day. The table "Who hands to whom" has From, To, Transfers, Usual reason, Extra wait, Solved same day and Went round again.

Extra wait is the median time from the transfer starting to the second agent answering. Went round again counts transfers on tickets passed on two or more times. A route with a long extra wait or many passed-on-twice tickets is a routing problem to fix at the menu or the queue, not an agent problem. See call queues and ACD.

How to use these in a one-to-one

Open the reports for the last 30 days before the meeting, so one bad day does not set the conversation. Start from a question, then use the figure to answer it together.

A one-to-one plan from the People reports
AskOpenLook at
How did the calls go?Agent scorecardAverage call vs floor and First contact, against the Floor row
Do their fixes stick?Floor standingsStayed closed and First contact
Were they free when it rang?Agent scorecard, Availability and breaksMissed while free, and the Break log for the days it happened
Are they stretched or waiting?OccupancyOccupancy against 85%, and the Waiting column
Where do their hand-overs go?TransfersRoutes from this agent, Extra wait and Went round again
  1. Choose one figure that stands out from the floor and ask the agent what is behind it.
  2. Open one recorded call or ticket from the day it happened, and listen together.
  3. Agree one change and send it as a short note, as the morning check does for coaching.
  4. Next month, open the same report and look at the same figure.

Start on SautiDesk

  1. Pick Pro at KES 3,000 per person a month. The People reports are Pro; see pricing.
  2. Choose a Kenyan number for KES 500 a month and add your agents.
  3. Ask agents to sign in and keep their status current, because Occupancy and Availability read the status history.
  4. Give your supervisor the Reports access and open Agent scorecard after a week of calls.
  5. Read the rest of the set in the call centre reports guide, and keep an eye on service level.

Every report is listed on the monitoring and reports page, and the calls themselves are answered in the call centre software.

Keep reading

MetricsCustomer service KPIs: the 12 numbers worth tracking10 min readTeamThe ten-minute morning check every supervisor should do6 min readTeamHow many agents do you need? The Erlang method in plain language9 min readCallsCall queues and ACD explained: how calls reach the right agent7 min read

Frequently asked questions

An agent scorecard is a table with one row per agent showing figures such as calls answered, average call length, first-contact closes and time signed in, set against the floor average. SautiDesk's Agent scorecard is on Pro.

Put calls, WhatsApp, SMS, email and web chat on one screen.

Incoming calls are free. Outgoing calls are KES 0.05 a second, paid from a balance you top up by M-Pesa or card.