Pull up a chair. You have just been made a team leader, you have twelve to fifteen agents, and someone has told you to “start running huddles”. Nobody has told you what a huddle is for. So let us work that out together, because a huddle done badly is the most reliably wasted ten minutes in a contact centre, and done well it quietly fixes half your problems before the first call lands.

Start with what a huddle is. It is a short briefing, usually five to ten minutes, held with the whole team just before the shift begins or at a fixed point early in it. Agents are standing or sitting together, the headsets are around their necks, the queue has not yet started pushing calls. That timing is the whole point. You have everyone’s attention, and what you say can be used within minutes.

What the ten minutes are actually for

Think of a huddle as doing four jobs. You do not need to do all four every day, but if a huddle is doing none of them, cancel it.

  • Pass on information that changes what agents say or do today: a billing cycle date, a system outage, a new offer, a policy correction.
  • Close the loop on yesterday: one number, one example, one thing the team did well.
  • Teach one small thing, a single call-handling habit or a knowledge-base article, not a lecture.
  • Take the temperature of the room. You learn more from who is quiet than from the slide.

Notice what is missing: reading out the full MIS, scolding the team for a bad week, announcing individual poor scores in front of everyone. Those belong somewhere else. A huddle that opens with a telling-off teaches agents to arrive late.

Information that changes behaviour

Here is a test you can apply to every item you plan to mention: “What will an agent do differently in the next hour because of this?” If the answer is nothing, it is an email, not a huddle item.

Suppose a telecom process has a bill-generation run tonight, so customers will start calling tomorrow about charges. A good huddle line is: “Bills drop after 9 pm today. From tomorrow expect questions on the late fee line. The explanation is in the knowledge base under that heading; the fee is waived only if the customer has not had a late payment in the last six months.” Four sentences, and every agent can act on them. Compare that with “please be updated on all the latest process changes”, which tells nobody anything.

Write the points down before you walk in. Three items is a good number, five is too many. People remember the first and the last thing you say and blur the middle, so put the item that matters most first.

Feedback on yesterday, without humiliation

Yesterday’s numbers are useful only if they point at something the team can control. Share team-level figures, such as service level or repeat calls, and then give one concrete observation: “We had a spike of calls asking about the same refund status between 11 and 12; the status page was down.” That is information, and it removes blame.

Praise works best when it is specific and tied to a behaviour you want repeated. “Good job, team” evaporates. “Meena checked the previous ticket before asking the customer to repeat the issue, and the call closed in one go” gives the others something to copy. Do it by name only when you are sure the person is comfortable with it; some freshers freeze when singled out, and that is worth knowing about them.

Individual poor performance goes into a one-to-one conversation. Public correction is the fastest way to make a huddle something agents survive instead of use.

The micro-lesson

One habit, one example, two minutes. It might be how to confirm a customer’s identity before discussing a balance, or how to avoid saying “I don’t know” without a next step. Play a thirty-second clip of a good call if your process permits recordings to be used for training, or role-play it quickly with a volunteer. Repeat the same micro-lesson for three or four days if the audit data says it has not landed. Repetition is not boredom here; it is how a habit forms.

Rotating the delivery helps too. Let an agent who handles a tricky call type well explain it for two minutes. It builds confidence in that agent, and the team often listens to a peer more closely than to a leader.

The cost, and why it is still worth paying

A huddle is not free. If fifteen agents spend ten minutes each, that is 150 agent-minutes, or 2.5 hours, out of 120 working hours that shift. That is about 2.1 per cent of the team’s capacity. In a process running tight on service level, that matters, and the workforce planning team will have booked the huddle as scheduled time, often under a specific aux or meeting code, so that adherence is not marked down. If your huddle regularly runs to fifteen minutes, the planning team is being quietly short-changed and the queue will show it. Keep time ruthlessly.

Against that cost, set what a good huddle prevents: dozens of calls handled with outdated information, repeat contacts from wrong answers, and the escalations that follow. One missed policy change can cost far more than 2.5 hours.

When huddles stop working

They fail in predictable ways. The leader talks for the full time and nobody speaks. The content is the same every day, so agents tune out. Attendance is optional and only the keen ones come. Or the huddle becomes a stage for reading targets. If you see any of these, shorten the huddle, cut the agenda to one thing, and ask the team directly what they would like covered. They will tell you, usually within a week.

Split shifts and work-from-home teams need a little adjusting. A call-based huddle with cameras optional, or a written “start of shift” note with one question to answer, works for people who cannot be in one room. The principle stays the same: short, specific, and useful within the hour.

Next time, before you walk in, write three lines on a card: what changed today, what we learnt yesterday, what one habit we are practising. If you cannot fill the card, you do not yet have a huddle, you have a meeting looking for a purpose. Come back with a better card tomorrow.

Figures and names in the examples are illustrative.

Leave a Reply

Trending