Why Are Customers Not Showing Up to Onboarding Calls?

Most of the customer onboarding best practice written for SaaS assumes the customer is in the room. The onboarding specialist whose r/CustomerSuccess thread this page answers described the four ways they are not.

Those are four different problems with four different fixes, and only the third is about scheduling. Look at what happened before the first invite. The customer was sold by someone else, on an outcome, over several calls. Then the deal closed, the salesperson's attention moved to the next deal, the customer's attention moved back to their job, and a week later a new name appeared asking for an hour. The person who signed is often not the person who will use the product, and the person who will use it may not know they have been volunteered.

The review corpus shows the same gap from the vendor side. Of the 2,094 sentences in 3,628 public reviews where reviewers describe why they bought a customer success platform, 85 mention onboarding, and 15 of those are specifically about tracking which new customers are falling behind or going quiet. One reviewer's list of problems began with "inefficient onboarding, unengaged 'dark' accounts". The no-show is the first appearance of the dark account.

That is also why it matters more than the empty slot suggests. The r/CustomerSuccess thread on the customer who stops replying traced one churn to a renewal call that "got rescheduled once politely. Then it got rescheduled again politely. Then it did not get rescheduled." The onboarding no-show is the same pattern at day 10 instead of day 340, when it is still cheap to fix.

Name the cause for each account that did not show before you change anything. The fix depends on the cause, and the same reminder email sent against all eight causes fixes one of them.

The fourth cause deserves its own note because it produces the most resentment. One delivery lead described a kickoff on June 8 with a go-live promised for July 20, where a single employee data file requested on June 10 arrived usable on June 29, and the customer's VP then asked why the project was behind. A plan that shows the customer's homework with their name on it, sent before the kickoff, is the only defence that does not feel petty in the meeting.

Book the kickoff before signature, name the customer's owner, and send a plan rather than an invite. The sequence below runs for any account above self-serve size, starts before the deal closes and ends at the week-four check-in, with every step dated relative to signature.

1. 1

   Day minus 3: the kickoff goes on the closing call

   The salesperson, with the onboarding manager's calendar open, agrees a kickoff date on the final call, within seven days of signature. It goes in the order form's notes or the closing email. A date agreed while the customer is still deciding to buy is treated as part of the purchase. A date requested afterwards is treated as a favour.

2. 2

   Day 0: the handoff note reaches you before the customer does

   From the salesperson, one page: the goal in the customer's words, who signed and who will use it, anything promised beyond the order form, and the kickoff date. If the note does not exist, write it yourself from the CRM and send it back to the salesperson to correct. The r/CustomerSuccess thread on handoffs is a list of kickoffs where the customer said "wait, we were told X would be included" and the CSM had no idea what X was.

3. 3

   Day 0: the welcome message is a plan, not an invite

   Under 150 words, from you, to the sponsor: what they told us they want, the three milestones that get them there with dates, the kickoff date already agreed, and one ask: who owns this day to day on your side?

4. 4

   Day 1 or 2: the 15-minute owner call with the sponsor

   Not the kickoff. Three questions: who is the day-to-day owner, what does done look like in 30 days, and what on your side could slow this down. Confirm the kickoff date and invite the owner. The sponsor rarely attends a kickoff and should not have to; this is the call that gets their attention while you still have it.

5. 5

   Day 2: the one-page plan, with their homework named

   Their goal, three milestones with dates, the items only they can provide (data file, integration credentials, the list of users) with an owner and a date each, and what the kickoff will decide. Send it to sponsor and owner. This page is what people reply to when they will not reply to an invite.

6. 6

   Day 5: the reminder that names the decision

   One line to the owner: "Thursday we decide the user list and the first integration; if the data file is not ready that is fine, we will work from a sample." Reminders that name a decision get attended. Reminders that say "looking forward to our session" get moved.

7. 7

   Day 7: the kickoff, 45 minutes, no product demo

   They have seen the demo. Open with their goal read back to them, confirm the milestones, agree who does what by when, and finish with the first thing they will do in the product before the next call. Send the summary within two hours, with the homework table and dates.

8. 8

   Day 28: the week-four check-in as its own meeting

   Three questions: are you using the parts you expected to, what surprised you, what would you change. One delivery lead's cohort analysis on r/CustomerSuccess found this meeting, held as a dedicated session in week four, was a stronger predictor of month-12 renewal than account manager, account size or integration quality: 91% renewed when it happened, 67% when it did not. One team's numbers, but the mechanism is sound: it is the first moment the customer says out loud whether the plan matched reality.

Change the offer rather than sending a fourth invite, and treat the second no-show as data about the account. Some customers will miss the kickoff even with the sequence running, and what you do next decides whether the account starts or drifts.

The decision rule: three touches over 14 days, then change the offer. Past three, each additional invite lowers the reply rate and raises the chance the customer's first strong feeling about you is being chased.

For the customer who started using the product and ignores you, stop treating attendance as the goal. The r/CustomerSuccess thread asking whether onboarding calls are overrated put the question well: for SMB and self-serve customers, should the goal be getting them into a meeting, or helping them succeed inside the product with guidance when they need it? Our answer is the second, with one exception: if their usage shows they have built the wrong thing (no integration, one user, a workflow that will not scale), a 20-minute "here is what you missed" review converts far better than an onboarding invite, because it is about their work.

Kickoff attendance is easy to count and is the wrong number. A team that reports 90% kickoff attendance and 55% activation at day 30 has an onboarding problem that the attendance figure hides. Track four things per account, on a sheet if that is what you have:

• Days from signature to kickoff held. Target seven. The distribution matters more than the average: every account over 14 days is a flag.
• Homework returned on the date in the plan. This is the customer-side delay the project tool cannot see, and it predicts the go-live slip.
• First value milestone reached by day 30, defined per product (first integration live and a second user active, for most). Activation, not attendance.
• Week-four check-in held as a dedicated meeting. Yes or no.

And count your own hours. One implementation specialist on r/CustomerSuccess averages six to seven one-hour meetings a day across implementations of 8 to 16 weeks. At that load the onboarding manager reschedules as often as the customer does, and the customer notices. The accounts per CSM calculator counts each new onboarding at six hours; put your monthly new-account count in and see whether the sequence above fits in the hours you have before you promise it.

When attendance is fine and the customer still churns at month four, the problem has moved from showing up to reaching value, and that is a different page: onboarding complete but the customer churned. And the account that no-shows twice, never logs in and goes silent is the same account that goes quiet at month eight; the re-engagement playbook is the follow-on.

GainTrace connects the calendar, CRM, billing and product data the sequence depends on, so a signed account with no kickoff held by day 10 and no login by day 14 is flagged automatically, with the sponsor, the salesperson and the plan attached. Product signals show which new accounts have started self-serving and which are dark, and rescue playbooks run the owner call, the plan and the week-four check-in as tasks with dates, without an admin building the workflow.