WFM guidePeople operations

Contact centre agent communication

Q: How do you communicate with agents in a 24/7 contact centre?

Communication in a 24/7 contact centre requires a written-first architecture, since no meeting can reach every shift. The core components are: (1) a daily briefing document published at a fixed time each day, accessible on the intranet or team channel, covering today's priorities, known issues, SL targets, and any process changes effective today; (2) a shift handover note passed between shift controllers at each shift boundary — covering live queue state, any active incidents, and agents flagged for follow-up; (3) a read-and-sign acknowledgement process for policy changes that require evidence of receipt — completed individually per agent regardless of which shift they worked when the communication was issued; (4) a weekly team meeting per team, which can be held at different times across shifts — but the minutes must be shared with agents who missed it. For urgent communications (process change effective immediately, system outage, regulatory announcement), the Team Leader cascade is the fastest channel: brief TLs within 30 minutes and require them to brief their teams on-shift within 15 minutes of being briefed.

A process change communicated in a team meeting to 20 agents out of 200 has, in practice, not been communicated at all. Effective contact centre communication is written-first, shift-aware, and measurably received — not just sent.

Why contact centre communication is structurally harder

Agents are on calls

Unlike office workers, agents cannot be interrupted for a briefing during contact handling. Communication must happen in breaks, before shifts, or in written form accessible when they are not on a call.

Simultaneous shift operation

A large contact centre operates across multiple overlapping shifts. A message sent at 2pm reaches agents starting at 6am, 8am, 10am, 12pm, and 2pm differently — unless the communication architecture accounts for all of them.

No natural all-hands moment

Unlike an office, there is rarely a moment when all agents are available simultaneously. A 7am briefing meeting catches the early shift but misses lates. A Friday afternoon message misses weekend-only staff.

High agent-to-manager ratio

Team leaders typically manage 12–20 agents each. A message that relies on verbal cascade from the operations manager through team leaders to agents requires a reliable chain at every link — and most chains have gaps.

Written-first principle: Every piece of operational information that agents need to know should exist in writing before being communicated verbally. Verbal communication is faster but unverifiable and subject to distortion across the cascade. Written communication is slower to produce but measurably received, consistently worded, and accessible to agents who were not present when the verbal communication happened.

Communication types and the channel for each

Communication type	Urgency	Primary channel	Acknowledgement required?
System outage / live incident	Immediate	TL verbal cascade (TL briefed within 30min, briefs team within 15min); follow-up written note within 60min	No — speed over completeness
Process change effective today	High	Daily briefing document + TL verbal briefing at shift start; written note pinned in team channel	Yes — read-and-sign within 48h
Policy change with future effective date	Planned	Briefing document + team meeting + read-and-sign acknowledgement	Yes — must be 100% before effective date
Today's service level targets and known issues	Routine	Daily briefing document	No
Individual performance feedback	Routine	1:1 between TL and agent — never broadcast	No — TL records in coaching log
Team news and engagement updates	Low	Weekly team meeting + team notice board	No
Regulatory or compliance communication	High	Written formal communication + read-and-sign; TL verbal follow-up	Yes — 100% compliance required

The daily briefing: structure and discipline

A daily briefing document is the single most important communication mechanism in a contact centre. Published at a fixed time each morning (typically 7–8am), it is the first thing team leaders read before briefing their teams at shift start.

Daily briefing — standard sections

Today at a glance

Forecast volume vs. yesterday, any scheduled events, staffing summary (planned vs. actual for today)

Sets the operational context for every team leader before they receive their first contact

Service level and KPI targets

Today's SL target (if different from standard), CSAT target, AHT guidance, any queue-specific priorities

Team leaders can brief agents on what the operation is optimising for today

Process changes effective today

Any change that takes effect from today — new script, updated policy, system change, new product, fee change

The most operationally critical section — changes not in this section risk inconsistent application

Known issues and workarounds

Current system issues, known product problems generating contacts, workarounds agents should use

Prevents agents from spending handle time troubleshooting issues that already have a known workaround

Focus of the day

One specific behaviour or process that operations is focused on improving today

Concentrates coaching attention — one specific focus is more effective than five

Staffing and schedule notes

Any same-day cover changes, known absences affecting the plan, overtime authorisation, cross-skill activation

Resource awareness across team leaders — reduces duplicated calls to the planning team

Discipline rule: The daily briefing must be published at the same time every day, regardless of whether there is anything significant to communicate. A briefing that only appears when there is news trains team leaders to check it inconsistently. A briefing published at 7:30am every working day is read habitually. A briefing published irregularly is checked unreliably.

Shift handover: maintaining continuity across shift boundaries

A shift handover note is a written document passed from the outgoing shift controller to the incoming shift controller at each shift boundary. In operations that run 24 hours, this is one of the most critical communications in the day: the incoming team begins blind to queue state, incident status, and agent issues if the handover does not capture them.

Shift handover note — required fields

Completed by outgoing controller; received and acknowledged by incoming controller

→

Queue state at handover

Current queue length and wait time on each channel; SL status vs. target at this point in the day

→

Active incidents

Any live system issues, outages, or known product problems and their current status — include the incident ticket reference if using an ITSM system

→

Staffing exceptions

Agents who departed early, arrived late, or are on overtime into the next shift; any cover gaps the incoming controller needs to manage

→

Agent flag notes

Any agent who requires a follow-up from the incoming shift — performance, wellbeing, conduct — with brief context

→

Decisions and escalations outstanding

Anything the outgoing controller escalated or made a decision on that the incoming controller should be aware of

→

Priority for next shift

The one or two things the incoming controller should focus on in their first 30 minutes

Verbal handover is not enough: A verbal handover between shift controllers has a failure rate that increases with shift boundary frequency. The incoming controller is absorbing a large amount of information quickly, while also beginning to observe the live operation. A written handover note that the incoming controller signs off on creates a clear point of knowledge transfer and means the outgoing controller cannot be held responsible for information they documented and passed over.

Communication in 24/7 environments

A 24/7 contact centre has agents on shift at 3am who may not see a message sent at 9am until their next shift or until someone actively sends it to them. The communication architecture must account for all shifts, not just core hours.

What works in 24/7 environments

✓Persistent written notice board accessible from any device at any time — agents check it at shift start regardless of when they start

✓Read-and-sign acknowledgement tied to individual login — system tracks which agents have read and signed regardless of their shift pattern

✓Shift-specific TL briefings — each shift team leader briefs their team at shift start using the same briefing document

✓Flagging changes with an effective date, not just a send date — agents arriving on night shift 3 days after the message was sent still need to apply the change

What fails in 24/7 environments

✗Email-only communication — night shift agents may not check email until they are home, which is after their next shift has already started

✗Team meetings as the primary communication channel — a single team meeting will miss all agents on the opposite shift unless meetings are duplicated

✗"Sent at 9am" treated as received — message was sent during day shift; night shift agents received nothing until someone told them

✗Verbal cascade across shift boundaries — the outgoing TL tells the incoming TL, who may not have briefed their agents before a process change took effect

Team meetings: making them operationally safe

A team meeting removes agents from the available resource pool for its duration. In a contact centre running at 80–85% occupancy, removing a team of 15 agents for 30 minutes creates a measurable service level impact — typically a 5–10 minute period of degraded SL during the meeting window.

Schedule meetings during natural low-volume periods

Typically mid-morning (10:30–11:30am) or early afternoon (2:00–3:00pm) for most contact centres. Avoid Monday mornings and Friday afternoons, which carry higher-than-average contact volumes. Use the interval-level WFM forecast to confirm.

Stagger meeting times across teams

Never run all team meetings simultaneously — the collective resource removal creates a centre-wide SL dip. Stagger by 30–45 minutes so teams rotate through the meeting slot while others remain available.

Keep meetings to 30–45 minutes maximum

A 60-minute team meeting in a contact centre is a significant resource impact and a significant ask of agents who are standing for or sitting through the session after a full shift on calls. Discipline the agenda to 30 minutes.

Publish meeting minutes for agents who could not attend

In shift operations, a percentage of the team will always be absent from any given meeting — they were on a different shift, on annual leave, or absent. Minutes should be published the same day and included in the next daily briefing.

Separate operational briefings from development conversations

Team meetings should not be used to communicate urgent operational changes — those go through the daily briefing and TL cascade. Team meetings are for development, engagement, and two-way dialogue. Mixing the channels reduces both.

Common communication failures and their operational impact

Inconsistent process application after a change

Root cause

Process change communicated verbally to some team leaders but not confirmed in writing; agents on different shifts received different information

Fix

All process changes go into the daily briefing on the effective date; TL verbal briefing supplements but does not replace the written record

Agents applying the old process weeks after a change

Root cause

Read-and-sign acknowledgement not enforced; agent was absent when the change was announced and no follow-up mechanism ensured they received it before returning to work

Fix

Read-and-sign tied to agent login — system prevents access until acknowledgement is completed; completion tracked and chased by TLs for outstanding agents

Incoming shift unaware of a live incident

Root cause

Shift handover was verbal only; outgoing controller summarised broadly without specifics; incoming controller did not know to ask the right questions

Fix

Written handover note signed off by both controllers at every shift boundary — incident status is a mandatory field

TL verbal briefing distortion

Root cause

Operations manager briefed team leaders; each TL interpreted and relayed the message differently; agents on the same floor received materially different versions of the same policy change

Fix

Brief TLs from the written document, not from a verbal summary — TLs read from the document rather than paraphrase; agents can read the source document themselves

Agent communication questions

How do you communicate with agents in a 24/7 contact centre?

Use a written-first architecture: a daily briefing document published at a fixed time every day, accessible to all agents regardless of shift; a shift handover note at each shift boundary covering queue state, incidents, and agent flags; read-and-sign acknowledgement per agent for policy changes (tied to individual login so it cannot be bypassed); and a TL briefing cascade for urgent changes (TL briefed within 30 minutes, briefs team within 15 minutes). Never rely on a single team meeting or email to reach all agents in a 24/7 operation — some agents will always be on a different shift when the meeting occurs or the email is sent.