A day in the life of a real-time analyst

Real-time management · A day in the life · ~7 minute read

The RTA job is the most operationally exposed in the planning function. Every 30 minutes a number lands; every miss has to be explained; every recovery has to be engineered without breaking the rest of the day. Here’s what the role actually is.

7:00am — the open

Floor lights up. RTA opens the WFM, the IVR dashboard, the queue monitor. Check the early-hours overnight: was the night-shift forecast accurate, are we entering today on plan or behind, what’s the staffing position vs the schedule.

A discipline: write the first hour’s outlook as a one-line prediction. "Voice will hit plan by 10:00 unless surge in claims pushes peak forward." At end-of-day, score the prediction. Over weeks, the RTA learns which signals are real and which are noise. Most don’t do this; the ones who do become the trusted voice in the room.

9:30am — the first miss

Voice service level just dropped through 75%. The TL is asking what to do. Three honest paths: tactical (push break-extensions, pull people from training back to live), structural (we’re going to miss the day; let’s set the expectation), diagnostic (what just happened — surge, AHT spike, staffing shortfall?).

The disciplined RTA picks based on cause, not on panic. The TL wants a tactical answer; the disciplined RTA often supplies the diagnostic first. "AHT’s up 18% on claims since 8:30 — we have a coaching or a process problem, not a staffing problem. Don’t move people."

11:00am — the over-the-shoulder move

A small operational re-jig: agent X from chat to voice for the morning, agent Y from claims to retention because retention is short. Not a schedule change; a real-time skill move within the established matrix.

These moves are the highest-leverage real-time decisions. They’re also the ones most likely to get the RTA into trouble. Documentation: who you moved, why, when you moved them back. Without it, you’ll be defending the move three weeks from now to someone who wasn’t there and doesn’t trust your memory.

13:30pm — the conversation about overtime

You’re going to miss the day. Operations leader asks if overtime will recover it. RTA does the math: 12 hours of OT now costs £X, saves Y% of SL miss, vs. accepting the miss costs Z (in customer complaints, vulnerable customer queue depth, regulator visibility).

The honest RTA names the trade-off and lets the leader decide. The one who pushes for OT every time burns the budget; the one who refuses every time accepts misses that should have been prevented. The middle — named explicit trade-off — is the discipline.

17:00 — end-of-day note

Twenty minutes. Write up what happened: numbers, causes, actions taken, results. Hand off to night-shift RTA. This is the most under-done activity in real-time management; the operations that do it well learn faster.

Specifically: name patterns. "Third Thursday in a row that claims volume drifted up at 10:30." If you don’t name them, they don’t make it to the planner who needs to re-base the forecast.

The RTA’s day — signal, decision, documentation Through the day ▸ 7:00 open — first-hour outlook ▸ 9:30 — first miss; diagnose first ▸ 11:00 — over-the-shoulder moves ▸ 13:30 — overtime trade-off named ▸ 17:00 — end-of-day note ▸ Throughout — 30-min interval reviews The disciplines ▸ Predict the next interval; score the prediction ▸ Diagnose before you intervene ▸ Document every move (who, why, when) ▸ Trade-offs named, not buried ▸ Patterns named so the planner can act ▸ Hand off cleanly to the next RTA The RTA who diagnoses earns trust; the RTA who reacts loses it

The disciplined RTA’s value

Diagnose before you intervene. Predict the next interval and score the prediction. Document every move. Name the trade-offs explicitly. Hand off cleanly. The RTA who does these things becomes the operations leader’s most trusted voice in the room; the one who reacts to every signal becomes background noise.

See also