
Stalled Onboarding: How Outlit's AI Tells Slow From Stuck
Author: Josh Earle
TL;dr
Stalled onboarding rarely looks dramatic: a few invited people who never signed in, an admin who's gone quiet, a setup step past its date. Taken at face value, most of those signals point you at the wrong person. Twelve people who can't sign in until single sign-on is live aren't twelve problems. They're one step the admin owns, and emailing those twelve people goes around the one person who can fix it. A quiet week after the admin told you they're waiting for their quarter to close is a plan, even though usage data will flag it within days. And often the stall is ours: the admin asked a question nobody answered, so a reminder about the overdue step only points at our own delay. Outlit checks for each of these on every new customer, every day, before anything goes out.
Why does a checklist miss stalled onboarding?
A stall nobody notices tends to surface at the first renewal conversation, after months of paying for a product the customer never finished setting up.
A checklist can tell you a step is overdue, but not why. "Turn on single sign-on" looks the same whether the admin forgot, is waiting on their security team, or asked us a question last week that nobody answered. A checklist sends the same reminder in all three cases, and in the third it reminds the customer about our own delay.
An AI agent fails the other way: it can nudge every quiet account every day, and customers learn to ignore all of it. Which stalls reach an owner first is covered in how we prioritize accounts.
Who holds the next step?
Every stalled setup has a next step, and someone holds it. Find that person first.
| Who holds the next step | What it looks like | What should happen |
|---|---|---|
| Us | A setup question we haven't answered, or a promise we haven't kept | Answer it, or hand it to the owner |
| The person running the rollout | Progress stopped on a step they own, and they still reply | One short follow-up that names the step |
| Someone the admin needs | The step needs the customer's IT, security or finance team | Ask the admin who, and offer to help that person |
| Nobody we can reach | The rollout owner left, or stopped replying after a follow-up | A person on your team steps in |
Outlit answers any customer question still waiting on us before it follows up. If the answer is already in the customer's emails, calls or tickets, the draft gives it. If not, the owner gets the question to answer.
Whose silence matters?
Silence from the person running the rollout, usually an admin, matters most. Before setup is done, people who haven't signed in are a symptom: end users can't do much until the admin connects the data or turns on single sign-on. Emailing each idle user goes around the admin and asks people to use something that isn't ready.
Once setup is done, people who still don't use it start to mean something, and the question for the admin is who was meant to use the product and what's in the way.
When is a quiet week normal?
When the customer told you why. "We'll pick this back up after our quarter closes on the 30th" turns two quiet weeks into a plan. Product usage alone would flag that account within days. An agent that reads the email thread knows the reason and the date. Until then the account is slow; if the date passes with no progress, it's stuck.
A reason only counts while it's recent. Outlit's drafts only draw on recent emails, calls and tickets, and anything older is left out or carries the month it was said.
Why does a new senior user get a welcome instead of a nudge?
A VP who signs in for the first time three weeks into a rollout is forming a view of the product and of your team. What matters is whether anyone on your team has met them, and whether they hear from you first.
Outlit drafts every new senior user a short welcome that introduces the account owner and says they can reply any time. Every welcome is checked for three things it must leave out:
- a link, or a request to book a call
- a demo, tour, tips or setup pitch
- anything about what they did in the product, such as "I saw you signed in"
The last matters most, because an email that opens with someone's first login reads as being watched.
What should a customer onboarding brief include?
The first three rows are the ones most briefs leave out.
| Include | Why | Where it usually lives |
|---|---|---|
| Questions waiting on us and promises we made | These come before any follow-up | Email, Slack, support tickets, call notes |
| Stated pauses, with their end dates | They separate a planned quiet week from a stall | Email, Slack, calls |
| The last two-way contact with the rollout owner | It separates a slow reply from no reply | Email, Slack, calls, meetings |
| The outcome they bought, in their words, with the date they said it | Follow-ups point at their goal, and an old goal reads as old | Sales and kickoff calls, CRM notes |
| Setup steps: done, next, and who owns each | The next step and its holder decide the response | Product usage, the shared onboarding plan |
| Who runs the rollout, who signed, and who's new | Whose silence matters, and who gets a welcome | CRM, product sign-ins, email |
| What they pay for and how fast they're using it: seats, credits or a usage commitment | Low use means little before setup is done. After, credits or a commitment drawing down slower than planned is often the first sign value isn't landing | Billing, product usage |
When should a person step in?
You decide how much of onboarding Outlit runs, and you can set it differently for each customer segment. In any segment, Outlit can send follow-ups itself, write them for someone on your team to review and send, or hand the account to its owner. One way to split it:
| Segment | What Outlit does |
|---|---|
| Smaller customers | Sends follow-ups about a named setup step on its own |
| Mid-market | Writes the follow-up; the CSM reviews and sends it |
| Enterprise rollouts | Hands the stall to the account owner, with what's stuck and who holds it |
Give a segment more autonomy once the drafts you review for it rarely need edits.
Whatever you set, we'd keep two kinds of stall with a person:
- The answer we owe isn't in anything the customer or your team has written or said. Often that's pricing, contract terms, a security review or a roadmap question. Outlit gives these to the owner instead of drafting an answer.
- The rollout owner left or stopped replying. Finding out why, or who replaces them, takes a conversation.
With more new customers than CSMs, start with scaled customer success.
What does one stalled account look like?
Worked example
An illustrative account, not a customer record. A team switches Outlit on mid-rollout, and Tuesday is Outlit's first day reading the account.
- What Outlit sees: kickoff call in
Gong on . In
PostHog, three of five setup steps are done, and the last one finished on . Three of the 15 people with access have signed in: the admin, a colleague and, on , a VP of Operations. The other 12 are waiting on single sign-on, which is step four. - What changed: on Thursday , the admin asked in
Gmail whether single sign-on groups can map to workspace roles. Nobody on our side replied.
HubSpot and the email history show nobody on our team has met the VP. - What a checklist would do: remind the admin about step four, which they're waiting on us to explain.
- Decision: the stall is ours. The question has waited since Thursday, eight business days counting today, so it goes to the owner's inbox as a reply we owe, with a drafted answer if past emails, calls or tickets hold one. The VP gets a short welcome with no link, no pitch and no mention of her signing in.
- Next check: the admin's reply, and step four completing in
PostHog. If single sign-on goes live and the 12 still don't sign in, ask the admin who was meant to use the product.
How do you know it's working?
Outlit keeps the count for you. For each onboarding follow-up you switch on, it shows how many customers it started with, how many replied, and how many reached the goal you set, such as first value within a window you choose. Each step shows how often it went out and, when it was held back, why. Before you switch a follow-up on, Outlit shows how many customers it would have started with, so you know the volume before anything sends.
When doesn't this apply?
If you onboard a few customers a quarter, each with an implementation manager on a weekly call, that person already knows who holds the next step. For self-serve sign-ups with no admin or account owner, in-product onboarding does this job better than email.
Where does Outlit fit?
Outlit tracks each new customer's setup steps, product usage and replies every day and notices the day progress stops. It checks the customer's recent emails, calls and tickets for anything we owe, follows up on its own within your rules, and welcomes new senior people. When a customer needs a person, the work lands in an inbox that decides each day what deserves attention. See the onboarding use case. If you'd rather build your own stall checks on Outlit's CLI, the developer guide to automating onboarding walks through it.
Read next

Customer Success Account Prioritization: Outlit's AI Rubric
Customer success account prioritization for AI agents: Outlit's rubric, how it reads customer conversations, how it avoids invented urgency, and a copy to use.

Helping At-Risk Customers
How do you help at-risk customers? Confirm what changed, check the account history and open commitments, then choose new help, follow-through, or no outreach.

How to Automate Onboarding with an AI Agent
Automate customer onboarding with Outlit. Includes new signup briefs, activation stall detection, first-week prep, milestone tracking, and CS handoffs.