The setting
is an AI customer-agent platform for businesses and customer-support teams. Its answers support questions, performs set support actions, and passes cases to human agents across several channels.
Releasing overflow capacity locks in a staffing assumption that the rehearsal has called into question.
Customer Support wants protection against specialist overload, while Engineering wants to preserve the release that renewal would displace.
Who you’d be doing this for
“Yesterday I told a customer they'd hear from a specialist by lunch, then spent the afternoon chasing someone who could actually help.”
Nora Nordstrom · Customer Support Director · a character in this brief
Leads support for a digital business whose unresolved technical issues escalate to specialists.
What is at stake
Overflow support capacity expires while a rehearsal casts doubt on specialist coverage. You must weigh an irreversible capacity release against a $420,000 renewal that displaces planned Engineering work.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- coverage certainty vs. release commitments
- training completion vs. demonstrated proficiency
- fast classification vs. costly verification
- irreversible savings vs. uncertain specialist demand
Why Fin
Autonomous resolution leaves people handling exceptions, so conversation counts alone do not establish whether specialist coverage is sufficient.
Written with these in mind
Not your kind of problem? 28 more at Fin, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Fin. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Events Producer (opens in a new tab)
- Principal Program Manager (opens in a new tab)
- Hold people accountable at every level, from workstream drivers to exec sponsors, ensuring progress and ownership across complex, cross-functional programs
- Senior Program Manager (opens in a new tab)
- Customer Support Process & Continuous Improvement Manager (opens in a new tab)
- Take full ownership of large, cross-functional special projects that improve the customer experience, increase teammate efficiency and engagement, and drive company goals
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about an irreversible change forced by a fixed date.
Monitoring shows 98.9% agreement, but a sample of hand-checked cases ranks some urgent ones differently.
Once supervisors drop the legacy queue you cannot roll back without disrupting service.
High-severity requests changed after a routing update, and the customer must report a material regression within seven days.
You must weigh continuity for business users against evidence that can withstand security review.
Long-running Kubernetes tests still produce intermittent latency spikes as the customer’s current capacity window closes.
You must weigh launch capacity against the cost of committing before the customer can trust sustained performance.
The same setting, from another role
Each is set around Fin’s Autonomous support resolution, written for a different role. They’re separate briefs, not the same scenario.
Verified customers still reach human agents for approved actions because enterprise teams cannot safely widen agent authority.
You have to weigh faster autonomous resolution against boundaries that remain inspectable when an action goes wrong.
Complex exceptions become full transfers even when a specialist only needs to answer one question.
You have to weigh conversation continuity against a boundary that people can understand and trust.
Existing customers are using initial workflows but hesitate to expand when they cannot explain how escalations and agent roles will change.
You must weigh a bold adoption narrative against claims that support leaders can defend inside their own operations.