The Onboarding Call Problem Has a Name
If you're running customer success at a growing software company, you know the math on new customer onboarding calls. Each net-new enterprise or mid-market customer needs 2-4 live sessions in the first 30 days: kickoff, product walkthrough, admin setup, Q&A. At any given time, a CSM might be running 15-20 active accounts, each somewhere in their own onboarding arc. The calendar fills fast, and the actual strategic work — checking in on product adoption, identifying expansion opportunities, building executive relationships — gets crowded out by the operational burden of repeating the same product walkthrough for the fourth time that week.
The common solution is "scale with content": build a help center, record some tutorial videos, write a setup guide. That works partially. It reduces inbound questions from self-serve customers. But mid-market and enterprise buyers rarely use self-serve documentation without a push. They expect a relationship, and a Notion wiki does not feel like a relationship.
The question isn't whether to keep a human CS touch. It's whether every part of the onboarding experience needs to be synchronous and live — or whether a well-designed async experience can handle most of the knowledge transfer while preserving the live touchpoints for things that genuinely require judgment and relationship.
Mapping Where the Time Actually Goes
Before redesigning the playbook, it helps to map the onboarding call content precisely. Most CS teams, if they audit their first 30-day call transcripts, find that the live call time breaks into roughly three categories:
First, procedural setup: walking the admin user through account configuration, user provisioning, SSO setup, data import, notification preferences. This content is essentially the same for every customer in the same tier. It changes only when the product changes. It requires no relationship; it requires clarity and patience.
Second, feature-specific walkthroughs: showing the key product capabilities relevant to the customer's use case, in the sequence that makes sense for their workflow. This content varies somewhat by customer type but is largely templated — a template for "HR team onboarding" and a template for "CS team onboarding" covers 80% of the variation.
Third, contextual Q&A and strategy: the conversation that can't be scripted — "how does this work given our org structure?", "what's the best way to get buy-in from our VP?", "we have a unique process for X, can we accommodate it?" This is the content that requires a human, that builds trust, and that actually earns the NPS points.
The insight that drives playbook redesign is this: categories one and two can move async. Category three is where the live call time should concentrate.
What the Async-First Playbook Looks Like in Practice
Consider a B2B SaaS company with roughly 200 mid-market customers that piloted an async-first onboarding redesign in their CS team. They built a library of voice-guided flows covering: initial account setup (12 minutes), the core workflow for their primary use case (8 minutes), user permissions and admin controls (6 minutes), and a "week two" flow on advanced features and integrations (14 minutes). Each flow was built by the CSM who previously delivered that content live — recorded once, iteratively improved over two quarters.
The new playbook looked like this: on the day of contract signature, the admin contact received a link to the account setup flow and a short welcome message from their assigned CSM. The CSM scheduled a kickoff call for day three rather than day one, with the expectation that the customer would have completed the setup flow and the core workflow flow beforehand. The kickoff call moved from "let me show you how to set this up" to "I see you've configured the workspace — let's talk about your goals for Q3 and how we'll measure success." The call ran 35 minutes instead of 90.
The change in what the live call contained is what made the CSAT difference, not the reduction in call time itself. Customers rated the experience higher not because they had fewer calls but because the calls they did have felt more substantive and personalized. The CSM was showing up prepared, already knowing the customer had completed setup, able to ask questions that built on that foundation rather than starting from zero.
The Completion Problem and How to Solve It
The obvious risk in moving onboarding content async is that customers won't do it. You send the flow link; it sits in their inbox. The kickoff call arrives and they haven't completed setup. You're back to running the walkthrough live.
This is a real risk and it requires active design decisions to mitigate, not wishful thinking. Three practices make the difference between async content that gets completed and async content that sits unread:
The first is urgency framing. "Here's a resource to explore" lands differently than "to get the most out of your kickoff call on Thursday, completing this 12-minute setup walkthrough beforehand means we can skip setup and go straight to strategy." The second framing creates a direct, near-term incentive. The third is sequencing: send the setup flow immediately on contract signature, when motivation is highest and the "new vendor energy" is fresh. Sending it the day before the kickoff call is too late. The fourth is visibility: knowing that the CSM will see whether the flow was completed creates accountability without being heavy-handed. Most customers will complete a 12-minute flow when they know their CSM can see it wasn't done.
We're not suggesting that async flows will achieve 100% completion rates — that's not realistic. Some customers will arrive at the kickoff call having skipped the async content, and the CSM needs a plan for that. But a realistic target of 70-80% pre-call completion for a well-designed, well-framed flow is achievable and still meaningfully changes the average cost and quality of the onboarding experience.
Playbook Structure: A Starting Template
For CS teams building this kind of playbook for the first time, a reasonable starting structure is:
Day 0 (contract signed): Welcome message from CSM + Link to Account Setup flow (10-15 min). Auto-triggered via HRIS or CRM on contract close.
Day 1-2: CSM reviews completion status. If completed: proceed to kickoff. If not completed: brief check-in to unblock any access or technical issues that prevented it.
Day 3 (kickoff call): 30-45 min. Focus on goals, success metrics, and strategic context — not product mechanics. Start with "I saw you've set up your workspace — what was your first impression?" as an opening question.
Week 2: Advanced feature flow sent after primary use case is established. Timed based on product adoption signals where available.
Day 30 check-in: Live call focused on adoption metrics, any blockers to broader rollout, and mutual success review. This call runs fast when the earlier async content did its job.
CSAT and What the Data Actually Shows
The teams that have implemented this kind of async-first playbook consistently report CSAT and NPS changes in the same direction: scores on setup experience stay flat or improve (customers don't miss the 90-minute setup call when the async walkthrough is well-made), and scores on "felt like my CSM understood my business" improve more noticeably. The second category — the relationship-quality signal — is the more durable predictor of renewal and expansion than the transactional setup score.
What's less consistent is the time-savings calculation. Teams with mostly mid-market accounts (where the async-to-live ratio shift is most dramatic) see larger per-customer time reductions than teams with mostly enterprise accounts, where the number of stakeholders and the custom-configuration complexity mean async flows cover a smaller proportion of total onboarding work. This is a genuine limitation worth acknowledging: async flows are not a substitute for the enterprise white-glove model. They're a tool that changes the ratio of repeatable-procedure time to relationship-judgment time, and the value of that ratio shift depends heavily on where the customer base actually sits on the complexity spectrum.