Communicating real-time to the rest of the operation
Intelligence nobody else sees is wasted
The real-time function sees the operation in detail no other function does. Marketing knows about its campaign in the abstract; real-time sees the volume impact in the first hour. IT knows about its release in advance; real-time sees the AHT drift the minute it lands. Operations leadership knows about the day in aggregate; real-time knows about it interval by interval. Most of that detail never reaches anyone outside the real-time team, and the information advantage is wasted. Operations that build standing communication channels turn real-time from a function that watches into a function that informs.
The TL early warning
The single highest-leverage real-time communication. When the real-time analyst sees something building — AHT drifting up, a queue forming on a niche skill, an abandonment trend — a short structured message to the relevant TLs catches the problem earlier than the dashboard will.
The format matters. “Heads up — we’re seeing AHT on the billing queue creep up over the last 40 minutes, looking at a system slowness on the billing screen. SL is still on target but trending down. Letting you know in case you’re hearing the same from your team.” Specific, time-stamped, actionable, doesn’t demand a response. The TL reads it, glances at their team, and now has 30–45 minutes of leading time before the operation as a whole notices.
Operations that establish this rhythm find SL recovery times shorten materially, because the TLs are pre-warned and able to position their team rather than scrambling to catch up. The TLs also start surfacing things back to real-time earlier — the relationship becomes bidirectional.
The planning daily handover
Fifteen minutes at end of each day, between the real-time team and the planning team. What was forecast, what actually happened, what was driven by which lever, what we’d do differently. Most of this content already exists in the post-event review (the next piece in this series), but the handover takes the lessons specifically relevant to the forecast and feeds them into the next forecast cycle.
Operations that run this handover find their forecasts adjust faster to operational changes — the planning team isn’t guessing whether a recent variance is real because the real-time team can tell them whether it was driven by a known cause or by unexplained drift. Operations that don’t run it find planning and real-time slowly drift into different views of the operation.
The standing marketing and IT relationship
The single biggest cause of real-time problems is something another function did without telling real-time. Marketing launched a campaign a week early; IT released a system change on Saturday morning; the product team changed a price overnight. Each of these is preventable with a thirty-minute weekly conversation with the relevant function.
The structure of the conversation is straightforward: what’s coming in the next 1–2 weeks that might affect contact volume, AHT, or routing? The real-time team is rarely the first audience for this information, but the team that’s in the room asking the question gets answered. The team that isn’t in the room finds out from the dashboard. This is covered more fully in the forecasting BI-layer piece and applies equally to real-time.
The monthly operations-leadership brief
One page, once a month. Top three real-time events of the month. The cost and the recovery. The cumulative impact of the lever menu. Two or three named risks for the coming month. This brief protects the function in the conversations that real-time leaders aren’t in — budget conversations, organisational design conversations, the “do we need this function?” conversation that happens periodically.
Most real-time teams don’t produce this brief because they’re busy with the operation. The teams that do produce it find their function is taken seriously when leadership conversations happen, and that the protection is invisible until it isn’t needed — at which point it’s too late to start producing it.
The four phrases to retire in real-time communication
“Heads will roll.” The escalation that sounds dramatic and produces no useful response. Replace with the specific ask.
“The system is wrong.” Even when true, this lands as the real-time team blaming the dashboard. Own the call.
“We need everyone on the floor.” The panic comms that produces a chaotic response. Replace with the specific lever you’re asking to be pulled, by whom, by when.
“It’s under control.” The reassurance that doesn’t describe what’s being done. Replace with three sentences: what we’re seeing, what we’re doing about it, what we need from you.
Conclusion
Real-time communication is what turns the real-time function from a metric-watcher into an operational nerve centre. The four standing channels — TL early warning, planning daily handover, upstream marketing/IT relationship, monthly leadership brief — each take small amounts of time and produce disproportionate value. Operations that build them find their real-time function is influential beyond its size; operations that don’t find the function is fully occupied and not particularly valued. The work is unglamorous and the payoff is cumulative.
Next in the series: The post-event review that nobody runs.
Pair this with the team-leader handoff, the business-intelligence layer, and the executive briefing.