The setting
sells software to mid-market and large businesses. Its hold customer conversations and take actions in the business's connected systems, across digital and voice channels.
Account context moves faster than the evidence needed to state a launch commitment.
Customer leaders need timely answers, while tentative dependencies and approved commitments cannot be treated as the same thing.
Who you’d be doing this for
“My COO asked whether the billing workflow is still on track, and I’m waiting on three different answers.”
Faisal Nasr · Vice President of Customer Support · a character in this brief
Owns service outcomes and launch readiness for an enterprise customer deploying several customer-facing agent workflows.
What is at stake
Enterprise support leaders are waiting on launch answers while account evidence sits across several records. You must decide whether the AI drafts only from approved guidance or also surfaces tentative working-session details for review.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast account answers vs. precise launch commitments
- working-session context vs. approved guidance
- broad usefulness vs. predictable review boundaries
- tentative dependency disclosure vs. firm date expectations
Why Sierra
Customer-facing AI agents reach production through customer-specific scope, integrations, evaluation, and launch decisions that depend on a shared account record.
Written with these in mind
Not your kind of problem? 37 more at Sierra, 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 Sierra. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Strategist, Agent Development - Healthcare (opens in a new tab)
- Develop AI agents for healthcare financial platforms that help patients understand billing, payment status, explanations of benefits, and financial assistance eligibility.
- Strategist, Agent Development (Flemish speaking) (opens in a new tab)
- Healthcare Integrations Architect (opens in a new tab)
- Strategist, Agent Development (Norwegian speaking) (opens in a new tab)
- Strategist, Agent Development (opens in a new tab)
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 people starting something and never quite finishing it.
CSMs checked multiple records for 18 of 30 onboarding replies about next steps.
You decide when AI may draft a next step from Salesforce notes and when the CSM must settle whether a proposal became an agreement.
Enterprise CSMs must reconcile conflicting records in 17 of 40 onboarding questions.
You decide whether AI may infer a remaining step from conflicting notes, or must leave that part of the reply for the CSM.
CSMs reopened account histories for 26 of 40 routine onboarding questions.
Where will you let AI draft the next step, and where must it hold for a CSM because the answer would promise someone’s work?
The same setting, from another role
Each is set around Sierra’s Customer-facing AI agents, written for a different role. They’re separate briefs, not the same scenario.
Customer agent updates are missing release windows while engineers reconstruct failed deploys.
You must decide which evidence can support a retry recommendation and which failures stay with an engineer.
An insurer needs a voice agent ready before its next billing cycle.
You must decide which deployment capability makes isolation repeatable without turning this launch into a custom build.
Bank callers face longer pauses while the current AWS capacity expires in nine days.
You must choose where the cutover evidence is strong enough to move customer traffic.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make complicated, high-stakes systems feel simple to navigate without quietly removing the protections people depend on.
Cross-surface tasks take a median of 7.4 navigation actions, and support data ties the confusion to delayed production changes.
You have to decide how developers move between workflows, evaluations, connections and deployed agents before deep links and permissions migrate and set that path.
Admins stall at permission validation and destination selection, and many misread what happens when a connection is committed.
You have to settle the interaction model now, because changing it after rollout is costly.
In audit samples, interviewers saw context that some customers do not permit, and the migration runs one way.
You have to keep scorecards structured and auditable while narrowing what interviewers see.
