Team leads see topics, not just numbers

The classic workplace of a contact centre team lead is a wallboard. Contacts waiting, service level, average handling time, attendance. These numbers matter. They tell you that something is happening. They do not tell you what.

When waiting times climb on a Tuesday morning, the team lead sees it at once. Why they are climbing often only emerges at lunchtime, when someone mentions that everyone is calling about the same bill. Topics close exactly that gap.

#What metrics answer and what they do not

Metrics and topics answer different questions. A team lead needs both, but in daily work it helps to know where one ends and the other begins.

#Topics instead of single cases

Conversation analytics transcribes conversations and analyses them by topic, sentiment and compliance. For the team lead this produces a picture that reads differently from a wallboard: not "120 calls" but "questions about the new instalment bill have been piling up since yesterday".

The value lies in aggregation. A single conversation tells a story. A hundred conversations on the same topic tell you that a letter is misleading, a form is missing or a process is stuck. That is a statement about the organisation, not about a person.

Univerx Assist· active

Conversation

AI agent, disclosedHandover from AI agent · context complete

I received the decision letter, but the amount does not match my application.

I have the case in front of me. One moment, I am checking the calculation.

Sentiment: calmVoice

Univerx Assist

Suggested reply

The letter deviates from the application. I will propose a correction and send you the confirmation by message.

InsertAccept

Summary

Request: deviation in the letter. Documents on file. Next step: correction, confirmation by message.

#Assist in the team lead's overview

Univerx Assist supports agents live with suggested answers, relevant knowledge, next steps and summaries. For team leads, Assist gathers the same signals into an overview.

That overview lets you pursue practical questions. Which topics have no matching knowledge article? Where are suggestions regularly set aside because they do not fit? Which summaries often need reworking? Each answer points to a place where the team can improve together.

#From topic to coaching

A topic on its own changes nothing. What matters is the path to an action. A simple sequence has proved useful.

1. Spot the topic. The team lead sees a topic that is growing or that often leads to follow-up questions.
2. Find the cause. Is knowledge missing, is a process unclear, or does the problem sit outside the team, for example in a customer letter?
3. Choose the action. A knowledge article, a short training session, a process change or a note to the responsible department.
4. Watch the effect. Measure it on the topic: is it becoming rarer, are there fewer follow-ups? Not on individuals.

Coaching becomes more concrete as a result. Instead of "your calls are too long", it becomes: "This new article helps with questions about the instalment bill. Let's look at it together." Quality management and performance management in Univerx Workforce give these conversations a fixed place.

#Ready for co-determination from the start

As soon as conversations are analysed, co-determination comes into play. Under Section 87(1) No. 6 of the German Works Constitution Act, the works council has a say in technical systems that can monitor conduct or performance. In practice, conversation analytics is regularly counted among them.

A topic view for team leads can be designed to follow that logic. Univerx can be configured so that recording, analysis and role permissions follow the rules you have agreed.

• Level of analysis: topics are shown for the team or department, not per person, unless agreed otherwise.
• Roles: who may see which view is governed by role permissions, not by habit.
• Recording: conversations are recorded only with consent.
• Purpose: the agreed purpose, such as finding knowledge gaps, is written into the works agreement.

How to prepare the conversation with the works council is covered in Talking to the works council about analytics.

#Three questions before you introduce topics

A topic map is quickly switched on. For it to hold up in daily work, three questions should be answered before the first team lead starts using it.

• Who maintains the topic list? Topics change with products, letters and seasons. Someone has to name new topics and merge old ones.
• Where do findings go that the team cannot solve? A misleading letter belongs with the responsible department, not in a coaching session.
• How does the team find out? People who know what is analysed and why meet the topic map with curiosity rather than suspicion.

#What changes day to day

The morning huddle no longer starts only with yesterday's waiting time but with yesterday's three most frequent topics. The knowledge base editors receive a short list of open gaps every week. And agents see that their hints about missing articles actually lead to new articles.

And the team lead spends less time guessing at causes. The wallboard stays, because capacity is still a matter of minutes. But next to the question "how many?" stands the question "about what?".

The guide Workforce planning in the contact centre: the basics shows how topics feed into planning.