1. What the team does (the function)
Case Status is not primarily an inbound desk. It is an outbound operation: staff spend their day calling SSA field offices and disability determination services to pull claim status, then relaying it to clients and keeping each file current. The inbound calls it fields are mostly clients asking the same question the team is built to answer: "where is my claim?"
Where the effort goes
| Activity | Volume (3 wk) | What it is |
|---|---|---|
| Outbound SSA status calls | 4,287 calls / 1,289 h | Calling SSA and DDS to retrieve claim status. The core job. |
| Inbound client calls | 1,046 calls / 160 h | Clients checking status, returning our calls, asking questions |
| Fielding SSA and provider calls | 31% of inbound | SSA, DDS, and providers calling us about a client |
| File hygiene updates | most client calls | Re-verifying contact and medical information while on the line |
The SSA-call reality (measured)
How inbound client calls end
| Outcome | Share | Meaning |
|---|---|---|
| Resolved with info | 63% | Client got an answer |
| Not resolved | 10% | Agent could not see status; no answer given |
| Message taken | 9% | Passed on |
| Callback scheduled | 8% | Agent will call SSA and call the client back |
| Partial / transferred | 6% | Handed off |
| No contact | 4% | Never connected |
The "not resolved" and "callback scheduled" calls share one root cause: the agent cannot see live SSA status on the call, so a status question the client expected answered instead turns into an outbound SSA call and a promised callback. That is a routing-and-data gap, not an effort gap.
2. How the team performs today
Where it breaks down
- The inbound status call often cannot deliver. The client calls to hear where their claim stands; the agent holds two to three minutes to "check," then returns with "it is still at SSA, we will call them and get back to you." The client leaves without the answer they came for.
- Clarity and plain language. This is a mostly offshore team, and explanations are frequently convoluted. In the calls reviewed, clients said things like "I do not understand anything you said." The information is usually correct; the delivery is not always clear.
- Continuity friction, made worse here. These are long-running cases, so clients have real relationships with a specific person and keep asking for them ("can I speak with Amari, with Patty, with Daphne"). The pooled-team answer lands harder on a client who has worked with someone for a year.
- Promised callbacks that depend on a coin-flip SSA call. "We will call SSA and call you back" is a fair promise, but the SSA-call data shows those calls reach a human only 65 percent of the time and yield info about half the time, so the loop is structurally hard to close.
3. The opportunities
1. Automate the SSA hold-and-retrieve
Roughly 456 agent-hours on hold in three weeks, 69 percent of SSA calls yielding nothing. This is the firm's largest pool of repetitive, low-value human effort. Reducing it is the clearest path to lowering total staff hours on this function, honestly stated.
2. Let inbound status calls self-resolve
If live status were on the file (from the outbound SSA work, captured and surfaced), inbound status checks could be answered on the spot or deflected to a self-service status line, instead of becoming a second SSA call and a callback.
3. Clarity and plain language
The team gives correct information unclearly. A plain-language standard, with "check for understanding," is a fast, high-impact lift on client experience for this team specifically.
4. Restore continuity
Long-running-case clients feel the loss of their person most. A consistent, warm reframe of the pooled-team model matters more here than anywhere.
4. Solutions
Start now No new technology required
| Move | What it fixes |
|---|---|
| A plain-language standard: explain status in one clear sentence, then check for understanding ("does that make sense, or should I put it another way?"). | Opportunity 3 |
| Manage the hold: if you must hold to check, say why and how long, and come back with either an answer or a concrete next step and time. | Client experience |
| The pooled-team reframe, delivered warmly: our whole team can see your case, so you never wait on one person. | Opportunity 4 |
| Close-the-loop discipline: every promised SSA callback becomes a tracked task with an owner and a due time, verified by QA. | Callback follow-through |
Soon The structural and automation wins
| Move | What it fixes |
|---|---|
| Automate the SSA hold-and-retrieve (AI or RPA that navigates the SSA menu, waits on hold, and pulls status; or a status-data integration where one exists). | Opportunity 1, the FTE prize |
| Surface live status on the file and a self-service status line (IVR plus client lookup) so inbound status checks resolve without a second SSA call. | Opportunity 2 |
| Screen-pop and skill routing on the client-facing calls, as with Concierge. | Client open, continuity |
The automation opportunity here is unusually concrete because the work is repetitive and measurable. Reducing SSA hold-and-retrieve hours is a direct reduction in total staff hours on this function, which is the honest goal, starting with the most repetitive work.
5. Folding Case Status into the QA journey
Case Status uses the same seven-fundamental standard as Concierge, with two facets weighted more heavily for this team: plain-language clarity and managing the hold. The v0 rubric:
| # | Fundamental | The standard | QA check |
|---|---|---|---|
| 1 | Open | Name plus firm plus offer to help | Did they identify themselves and the firm? |
| 2 | Verify before disclosing | Confirm identity smoothly, not as an interrogation | Verified before case info, without over-asking? |
| 3 | Confirm the ask | Reflect the reason for the call back in one sentence | Did they confirm what the client needed? |
| 4 | Own it plus set expectations | Plain status; if a callback is needed, say what, who, and when | Concrete next step with a timeframe? |
| 5 | Capture plus correct | Update the file; read back; fix bad data on the spot | Were updates captured and confirmed? |
| 6 | Close the loop | Recap next step, confirm channel, warm close | Did they recap what happens next? |
| 7 | Rapport (scored) | Recognition plus warmth, quickly and clearly, never robotic | Scored low / medium / high |
Two additions this team is scored on especially:
- Clarity (part of Rapport): did the client clearly understand the status and next step? Plain language, and a check for understanding.
- Hold handling (part of Own it): if placed on hold, was the client told why and how long, and did the agent return with an answer or a concrete next step?
The human-in-the-loop model, same as Concierge
The AI QA engine scores every call against the seven fundamentals and flags both directions: exceptions (unclear explanations, unmanaged holds, unresolved status calls, an open loop) go to coaching, and exemplars (a status explained clearly and warmly, a hard case handled well) go to recognition and become the "good call" clips. Humans review the flagged and sampled calls, coach with the specific clip, verify that promised SSA callbacks were actually made, and escalate the structural issues (the hold-and-retrieve burden, the live-status gap) rather than blaming staff for them. Orient first, then score, then hold accountable.
6. The immediate next moves
- Finalize the plain-language and hold-handling standards and a one-page Communications Excellence sheet for the team.
- Turn on AI scoring for Case Status and pull a two-week baseline, with clarity and hold handling weighted.
- Scope the SSA hold-and-retrieve automation as a standalone business case: the ~456 hold-hours per three weeks is the sizing input.
- Stand up the SSA-callback tracker so every promised callback has an owner and a due time.