The setting
develops an AI answer engine that searches the web and gives answers with sources. is its AI agent that uses tools and applications to complete multi-step tasks for professionals and enterprises.
An onboarding update becomes a commitment when the next step implies who will do it.
Account-specific replies protect customer momentum, while explicit holds protect delivery scope.
Who you’d be doing this for
“I asked what we still needed to finish, and now I'm waiting to know whether to book our technical lead.”
Youssef Dabiri · Enterprise onboarding administrator · a character in this brief
Coordinates a mid-market customer's onboarding and needs a reliable next step before scheduling colleagues.
What is at stake
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?
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- account-specific guidance vs consistent onboarding language
- clear next steps vs implied delivery commitments
- narrative context vs structured milestones
- broad question coverage vs bounded technical scope
Why Perplexity
Computer onboarding spans configured workflows, permissions, and bounded technical help, so account history determines what guidance actually applies.
Written with these in mind
Not your kind of problem? 44 more at Perplexity, 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 Perplexity. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- AI Strategist, Legal (opens in a new tab)
- Customer Success Lead (opens in a new tab)
- You’ll own the customer success strategy and operating model, lead CSMs across customer segments, and be accountable for gross and net revenue retention across the post-sale book, with expansion targets shared with Sales.
- Set the customer success strategy, and coverage model across high-touch Enterprise, scaled SMB and Mid-Market, and technical API customers
- Applied AI Architect, Perplexity Computer (opens in a new tab)
- Our customers are using Computer to transform work that traditional software has not been able to address.
- Convert repeated customer needs into reusable workflows, implementation patterns, demos, guidance, and product feedback.
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.
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.
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.
Enterprise CSMs reopen Salesforce notes and Google Sheets the night before renewal calls to rebuild what each customer was promised.
You have to decide where the drafted brief hands off to the CSM when a recorded warning sign has no clear source behind it.
The same setting, from another role
Each is set around Perplexity’s Perplexity Computer, written for a different role. They’re separate briefs, not the same scenario.
Connector onboarding takes 10 business days, and repeated review defects delay enterprise workflows.
You must decide where the draft packet ends and the engineers' approval of each schema, fixture and evaluation suite begins.
Scheduled research workflows stop after spending credits, leaving coordinators with incomplete briefings.
You must weigh useful visibility against protected connector details and uncertain agent plans.
Removed access sometimes still reaches workspace records through resumed sessions.
You must weigh rollout timing against proof that every connector fails closed.