Back-office copy, Version C

Hi {{firstName}},

{{opener}}

The backlog that clears by Friday grows back by Monday, and the week's schedules already hold the idle minutes to absorb it. Nobody can see the windows while they're open.

That's what Intradiem does. It sits on top of the case system and WFM your claims teams already run, shows how much work is piling up against the people you have, and moves the next case to the right person while the window is still open. {{proof_line}}

How much of {{parent_account}}'s claims capacity would you want back before the next headcount ask?

Nathan

{{firstName}}, Nathan Belfield at Intradiem. I sent you a note yesterday about the Monday backlog in claims and the idle windows already inside the week. It's in your inbox under "the monday backlog". I'll try you again next week.

Hi {{firstName}},

One thing I left out. Most claims operations manage turnaround off yesterday's report, so the day's capacity decisions get made after the day is gone. The teams that hold TAT through surge weeks aren't staffed heavier; they've closed the distance between a queue moving and someone acting on it.

{{enterprise_line}}

Twenty minutes before open enrollment on where {{parent_account}}'s idle windows sit. Which week works?

Nathan

Hi {{firstName}}, shot you a note by email about the Monday backlog in {{parent_account}}'s claims operation, thought this might be quicker. Nathan, Intradiem

Thanks for connecting, {{firstName}}. Short version of my email: the Monday backlog is a timing problem, and the capacity to hold TAT through the week is already inside the schedule. Intradiem sits on top of the case system and WFM your teams run and points that capacity at the queue while the window is open. Worth a conversation on how other payer claims teams run the week?

Hi {{firstName}},

Open enrollment puts every idle minute on the table and every open req on the plan. The claims teams that get through it without overtime aren't the ones with the best report; they're the ones acting on it by the hour.

If {{parent_account}}'s claims floor could move the next case into the gaps as they open, on top of what you already run, what would you do with the hours?

Nathan

{{firstName}}, Nathan Belfield at Intradiem again. I sent a second note yesterday on open enrollment and the hours it puts on the table, same inbox, "open enrollment at {{parent_account}}". Twenty minutes before the peak is the ask. I'll try you once more.

{{firstName}}, one number from Optum's back office: more than 14 fewer idle hours per associate every month, found inside the schedule. Is overtime in claims a line you're being asked to take down this year, or holding steady?

Hi {{firstName}},

I'll leave this here. If open enrollment lands the claims backlog back on your desk, or the overtime line comes up in planning, reply to this thread and I'll pick it up.

Good luck with the peak. May it treat {{parent_account}}'s claims teams better than last year's did.

Nathan

Hi {{firstName}},

{{opener}}

Cost per transaction gets reviewed monthly and decided in the minutes between reports: the dispute queue unworked from ten to eleven, the document team idle while onboarding backs up two floors away.

That's what Intradiem does. It sits on top of the case system and WFM your servicing teams already run, shows demand against the people on shift by the hour, and moves the next item to whoever has the minutes. {{proof_line}}

How much of {{parent_account}}'s servicing capacity would you want back before the next staffing buffer goes in?

Nathan

{{firstName}}, Nathan Belfield at Intradiem. I sent you a note yesterday about the minutes between reports and the idle capacity sitting in them. It's in your inbox under "between the reports". I'll try you again next week.

Hi {{firstName}},

One thing I left out. When volume spikes the ask is overtime or headcount, and both get harder to defend every cycle. The found-capacity conversation starts from the idle minutes already on payroll, sitting between queues that can't rebalance themselves mid-day.

{{enterprise_line}}

Twenty minutes before year-end close on where {{parent_account}}'s idle minutes sit. Which week works?

Nathan

Hi {{firstName}}, shot you a note by email about the minutes between reports in {{parent_account}}'s servicing operation, thought this might be quicker. Nathan, Intradiem

Thanks for connecting, {{firstName}}. Short version of my email: cost per transaction is decided in the minutes between reports, and those minutes are already on payroll. Intradiem sits on top of the case system and WFM your teams run and moves the next item into them by the hour. Worth a conversation on how other servicing teams prove utilization to finance?

Hi {{firstName}},

Year-end close puts every idle minute on the table and every open req on the plan. The servicing teams that get through it without overtime aren't forecasting better; they're acting on the queue by the hour instead of the day.

If {{parent_account}}'s servicing floor could move the next item into the gaps as they open, on top of what you already run, what would you do with the hours?

Nathan

{{firstName}}, Nathan Belfield at Intradiem again. Sent a second note yesterday on year-end close and the hours it puts on the table, same inbox, "year-end close at {{parent_account}}". Twenty minutes before close is the ask. I'll try you once more.

{{firstName}}, one number from Optum's back office, since the mechanics are the same in servicing: 18.4 percent productivity within nine months, found inside the schedule. Is utilization something you have to prove to finance this year, or is that settled?

Hi {{firstName}},

I'll leave this here. If year-end close puts the overtime line or the dispute backlog back on your desk, reply to this thread and I'll pick it up.

Good luck with close. May it treat {{parent_account}}'s teams better than last year's did.

Nathan

Hi {{firstName}},

{{opener}}

The TAT clock on a claim runs around the clock, and the capacity to keep it green gets rebalanced once a day against yesterday's numbers. Aging inventory lives in that gap: the right people idle in one queue while another slips.

That's what Intradiem does. It sits on top of the case system and WFM your claims teams already run, shows how much work is piling up against the people you have, and moves the next case to the right person while the window is still open. {{proof_line}}

How much of {{parent_account}}'s claims capacity would you want back before the Q4 peak?

Nathan

{{firstName}}, Nathan Belfield at Intradiem. I sent you a note yesterday about the TAT clock and the once-a-day rebalance behind aging inventory. It's in your inbox under "the tat clock". I'll try you again next week.

Hi {{firstName}},

One thing I left out. Surge weeks expose it: overtime gets approved after the backlog is visible, so the operation pays a premium to fix what it could have absorbed in the moment. The teams ahead of it have shortened a queue moving to someone acting from a day to minutes.

{{enterprise_line}}

Twenty minutes before the Q4 claims peak on where {{parent_account}}'s overtime concentrates. Which week works?

Nathan

Hi {{firstName}}, shot you a note by email about the TAT clock in {{parent_account}}'s claims operation, thought this might be quicker. Nathan, Intradiem

Thanks for connecting, {{firstName}}. Short version of my email: aging inventory is a timing problem more than a staffing one. Intradiem sits on top of the case system and WFM your teams run and moves the next case into the idle hours while they're open. Worth a conversation on how other claims operations hold TAT through Q4?

Hi {{firstName}},

The Q4 claims and renewal peak puts every idle minute on the table and every open req on the plan. The claims teams that get through it without overtime aren't the ones with the best report; they're the ones acting on it by the hour.

If {{parent_account}}'s claims floor could move the next case into the gaps as they open, on top of what you already run, what would you do with the hours?

Nathan

{{firstName}}, Nathan Belfield at Intradiem again. Sent a second note yesterday on the Q4 peak and the hours it puts on the table, same inbox, "the q4 peak at {{parent_account}}". Twenty minutes before the peak is the ask. I'll try you once more.

{{firstName}}, one number from Optum's back office: 15.4X on the automation, with more than 14 idle hours per associate back every month. Is overtime in claims a line you're being asked to take down this year, or holding steady?

Hi {{firstName}},

I'll leave this here. If the Q4 peak lands the aging-inventory question back on your desk, reply to this thread and I'll pick it up.

Good luck with the peak. May it treat {{parent_account}}'s claims teams better than last year's did.

Nathan

Hi {{firstName}},

{{opener}}

In an outsourced operation idle minutes aren't an efficiency stat, they're the margin line, and most never show up in the daily numbers: the gaps between volumes, early in shifts, in queues clients never see.

That's what Intradiem does. It sits on top of the case systems and WFM your delivery teams already run, shows utilization against client demand by the hour, and moves the next item into the gaps as they open. {{proof_line}}

How much of {{parent_account}}'s margin per seat sits in minutes nobody can see?

Nathan

{{firstName}}, Nathan Belfield at Intradiem. I sent you a note yesterday about idle minutes as the margin line and where they hide between client queues. It's in your inbox under "the margin line". I'll try you again next week.

Hi {{firstName}},

One thing I left out. Client SLAs get managed in real time; the cost side usually doesn't. So the operation that never misses a service level still gives margin back through overtime, shrinkage and idle time no report catches until month end.

{{enterprise_line}}

Twenty minutes before the Q4 client peak on where {{parent_account}}'s biggest leaks sit. Which week works?

Nathan

Hi {{firstName}}, shot you a note by email about the margin line in {{parent_account}}'s delivery operation, thought this might be quicker. Nathan, Intradiem

Thanks for connecting, {{firstName}}. Short version of my email: idle minutes are the margin line in an outsourced operation, and they're invisible until month end. Intradiem sits on top of the case systems and WFM your teams run and moves the next item into the gaps by the hour. Worth a conversation on how other operators take that into renewal?

Hi {{firstName}},

The Q4 client peak puts every idle minute on the table and every seat on the renewal sheet. The delivery teams that get through it on margin aren't the ones with the best report; they're the ones acting on it by the hour.

If {{parent_account}}'s floor could move the next item into the gaps as they open, on top of what you already run, what would you do with the hours?

Nathan

{{firstName}}, Nathan Belfield at Intradiem again. Sent a second note yesterday on the Q4 client peak and the seats it puts on the renewal sheet, same inbox, "the q4 client peak at {{parent_account}}". Twenty minutes before the peak is the ask. I'll try you once more.

{{firstName}}, one number from Optum's back office, same mechanics as a delivery floor: more than 14 fewer idle hours per associate every month. Is margin per seat a number you're being asked to move this year, or holding steady?

Hi {{firstName}},

I'll leave this here. If the Q4 peak or a renewal conversation puts utilization back on your desk, reply to this thread and I'll pick it up.

Good luck with the peak. May it treat {{parent_account}}'s teams better than last year's did.

Nathan

Hi {{firstName}},

{{opener}}

Most operations share the same blind spot: the contact center is managed minute by minute while {{function}} runs on yesterday's report. Same company, same cost pressure, two clocks. Idle windows go unseen and overtime gets approved after the fact.

That's what Intradiem does. It sits on top of the case system and WFM your {{function}} teams already run, shows how much work is piling up against the people you have, and moves the next item to whoever has the minutes. {{proof_line}}

How much of {{companyName}}'s {{function}} capacity would you want back before the next headcount ask?

Nathan

{{firstName}}, Nathan Belfield at Intradiem. I sent you a note yesterday about the two-clocks problem, the front office managed in real time while {{function}} runs on yesterday's report. It's in your inbox under "two clocks at {{companyName}}". I'll try you again next week.

Hi {{firstName}},

One number I left out. A healthcare services company measured 1,649 active work hours back in a 90-day pilot, 5.9 percent more active time, with nobody added to the floor. That's the shape of it in most operations: the capacity is already on the payroll, it arrives at the wrong minute.

Twenty minutes before {{peak}}. Which week works?

Nathan

Hi {{firstName}}, shot you a note by email about the two clocks in {{companyName}}'s {{function}} operation, thought this might be quicker. Nathan, Intradiem

Thanks for connecting, {{firstName}}. Short version of my email: the idle capacity your front-office peers manage minute by minute exists in {{function}} too, invisible until the end-of-day report. Intradiem sits on top of the case system and WFM your teams run and moves the next item into those windows by the hour. Worth a conversation on how other {{function}} teams run the week?

{{firstName}}, Nathan Belfield at Intradiem. Second note from me on the two clocks at {{companyName}}. The number behind it: a healthcare services company got 1,649 active hours back in 90 days without adding a seat. Twenty minutes before {{peak}} is the ask. I'll try you again next week.

Hi {{firstName}},

Just tried your line and left a short message. The question stands: how much of {{companyName}}'s overtime in {{function}} is idle time in disguise? The pilot I mentioned answered it with 1,649 hours.

Worth twenty minutes to find out what {{companyName}}'s number is?

Nathan

Hi {{firstName}},

{{peak}} puts every idle minute on the table and every open req on the plan. The {{function}} teams that get through it without overtime aren't the ones with the best report; they're the ones acting on it by the hour.

If {{companyName}}'s floor could move the next item into the gaps as they open, on top of what you already run, what would you do with the hours?

Nathan

{{firstName}}, one number from Optum's back office: 18.4 percent productivity within nine months, found inside the schedule. Is overtime in {{function}} a line you're being asked to take down this year, or holding steady?

{{firstName}}, Nathan Belfield at Intradiem. Third note from me on the two clocks at {{companyName}}. {{colleagueLine}} Twenty minutes before {{peak}} is the ask: is intraday capacity in {{function}} on the list for this year, or next? Thanks {{firstName}}.

Hi {{firstName}},

One thing worth knowing before {{peak}}: Intradiem runs inside the staffing plan you've already set, so it can start before the peak rather than after it. {{colleagueLine}}

Is intraday capacity in {{function}} on the list for this year, or next?

Nathan

{{firstName}}, {% if colleagueFirst %}you and {{colleagueFirst}} both carry a piece of the overtime line at {{companyName}}, so you've both got the same note from me. {% endif %}Twenty minutes before {{peak}} on where the idle minutes sit in {{function}}. Which week works?

Hi {{firstName}},

I'll leave this here. If {{peak}} lands the {{function}} backlog back on your desk, or the overtime line comes up in planning, reply to this thread and I'll pick it up.

Good luck with {{peak}}. May it treat {{companyName}}'s teams better than last year's did.

Nathan