When a new customer goes quiet during onboarding

A CSM on r/CustomerSuccess described it exactly. Customers get through the sales process, get handed off to CS, and then stop engaging. What follows is weeks of polite chasing.

It rarely feels like a crisis while it is happening. The kickoff went well. Everyone was enthusiastic. There is just one small thing waiting on their side, an admin account, a data export, a security questionnaire, and it has been waiting for three weeks.

Often the cause is structural, not a sign the customer has cooled on you. Your onboarding plan tracks your tasks carefully and lists theirs as "customer". A task owned by the customer is owned by nobody.

Kickoff · Owner: CSM

One plan, visible to both sides, listing every task that stands between signature and first value. Each task gets an owner by name and a date. Their names, not "IT team" or "customer".

Fill the names in live, on the kickoff call, with them. Asking afterwards gets you "we will figure out who owns that", which is how the stall starts. Asking in the room, with their sponsor watching, gets you a name.

If you ran a proper sales to CS handoff, the goal and the stakeholders are already known, so the kickoff can go straight to the plan.

Milestone          Task                          Owner (name, side)       Due
SSO live           Create SAML app in Okta       Priya R. (customer IT)   2026-10-08
SSO live           Configure and test SSO        Dev (us)                 2026-10-10
Data imported      Export last 12 months tickets Sam K. (customer ops)    2026-10-14
Data imported      Map fields, run import        Dev (us)                 2026-10-17
First report       Agree the one report for VP   Jo L. (customer VP CS)   2026-10-21

Owner: CSM

Another CSM on r/CustomerSuccess complained that their 30, 60 and 90-day check-ins made it hard to show any value, because a meeting called "30-day check-in" has no content until someone invents some.

Rename them after the milestones in the plan. "SSO live". "First team trained". "First report shipped". A meeting called "first report shipped" has its agenda and its success test built into the name, and it is obvious to everyone when it has not happened.

Small change. It moves the conversation from how things are going to whether a specific thing is done.

Weekly · Owner: CSM

Pick a rule and write it down. A reasonable one: ten business days with no customer-side task completed is a stall. Tune the number to your onboarding length, but have one, because without a rule a stall is only ever noticed when it has already become a problem.

Check it weekly, ten minutes across your book. The plan does the tracking, so there is no need for the weekly "any update?" email one CSM described using to track customers through a ten-step setup. That email trains the customer to ignore you.

Owner: CSM, then CS lead

When the rule trips, climb a short ladder, and never ask "any update?" at any rung.

Day 10 of the stall: message the named owner about the specific task, and offer to do it with them on a 20-minute call. If the blocker was time rather than will, this is where it ends.

Day 15: go to the champion. Same specifics, plus what the stall is holding up.

Day 20: the sponsor. Frame it around their own goal and the date it now slips to. "The Q4 support reporting you bought this for is waiting on the ticket export. At the current pace it moves from October to December. Can we get 20 minutes with Sam this week?" Sponsors answer that. They ignore status updates.

Owner: CSM

"Configured" is your milestone. The customer's milestone is the first outcome from the goal they bought for: the first report their VP actually uses, the first ticket routed correctly, the first hour saved.

Do not close onboarding until that outcome has happened and the sponsor has seen it. Then write it into the account's running log as the first entry. It is the opening line of the first QBR, and the QBR prep playbook picks up from here. Our own version of this handoff into delivery is in onboarding automation.

The mutual plan fails in one predictable way: the customer's named owner leaves or changes role, and the plan still says their name. Check names, not just dates, at every milestone.

Whether to pause the contract clock for a customer whose onboarding has stalled through their own delay is a question this playbook leaves open. Some teams extend the term as goodwill. Others hold firm and treat the stall as the customer's cost. It depends on how much you want the account to succeed versus how much you want the principle.

Onboarding is the one phase where the customer has already paid and still has to do work for you. Make their part as visible as yours, and put a name on it.