Customer Onboarding: Process, Checklist, and Metrics
Customer onboarding is the process of helping new customers get started with a product or service and learn to use it successfully. As Zendesk’s onboarding guide explains, it connects signing up with successful use. A practical onboarding process covers the welcome, necessary setup, task-focused guidance, the first useful result, and a clear route to continued support.
What customer onboarding includes
The scope extends beyond a welcome email or an introductory tour. HubSpot’s customer onboarding guide identifies product adoption, customer satisfaction, and retention as objectives of onboarding. Use these as goals for the program, and measure whether customers reach the intended result and continue using the product.
Three related terms help define the work:
- User onboarding focuses on learning to use an interface and completing its initial setup. Nielsen Norman Group’s mobile-app analysis uses this narrower interface definition.
- Activation is a defined action that signals meaningful product value. Amplitude’s activation guidance recommends choosing the action for the product and checking it against behavioral data.
- Customer success covers the wider relationship. HubSpot’s customer success framework places onboarding alongside later stages such as adoption and retention.
Define the initial onboarding finish separately from ongoing education and support. The process below is a suggested structure; adapt the work to the product or service rather than requiring every customer to complete identical activities.
A customer onboarding process in six steps
1. Welcome the customer and show the next action
Send a welcome message that explains how to begin, where to find essential resources, and how to ask for help. HubSpot’s welcome-email guidance recommends a clear next action and a manageable selection of resources.
Keep the message focused on starting: provide the relevant access link, identify the first task, and include a support contact. For onboarding that involves direct assistance, introduce the person coordinating the process and explain how the customer can contact them.
2. Agree on the goal and responsibilities
Record the intended outcome, first milestone, task owners, and required inputs. HubSpot’s onboarding checklist recommends success criteria, ownership, and a review of goals and deliverables.
Use an intake form or conversation to collect these details. Hold a kickoff when coordination requires it, and keep the plan accessible to everyone responsible for a step.
3. Complete the setup needed for initial use
Complete the configuration needed for the first task. HubSpot’s setup checklist includes permissions, data import, and integration testing where required.
Mark each requirement as applicable or unnecessary. Assign an owner, confirm that access and configuration work, and keep optional setup separate from the initial path.
4. Teach the task the customer needs to perform
Build guidance around the work the customer will actually do. Salesforce’s training-planning module begins by identifying learners, their roles, and the relevant tasks before defining a training plan.
Provide a short guide, demonstration, or assisted session for the core task, followed by an opportunity to practice. Link to instructions that remain available afterward. Record any unresolved question and its next action. Choose the format according to the task and the assistance required.
5. Confirm the first useful result
Help the customer complete the intended task and check whether the result meets the agreed goal. Amplitude’s explanation of time to value distinguishes a meaningful benefit from merely completing setup or an onboarding action.
Record the completed outcome and when it happened. Use product evidence where the outcome is directly observable; ask the customer to confirm whether it was useful when judgment is required. Keep the record specific to what was accomplished rather than treating attendance or account creation as the final milestone.
6. Close the initial journey and establish ongoing support
Review completion against the agreed criteria. HubSpot’s framework proposes finished setup, initial training, and a defined first-value milestone as the criteria for leaving onboarding.
As a practical handoff, record the outcome, any remaining work, the ongoing contact or support channel, and the next review when needed. Make the change in responsibility clear to the customer. Keep unfinished dependencies assigned to an owner instead of leaving them in an untracked closing note.
A practical customer onboarding checklist
Use the following checklist to record the steps above. Add an owner, target date, and status for each applicable item.
| Item | What to record before marking it complete |
|---|---|
| Welcome | Access or starting instructions, the first action, and a help contact |
| Goal | The customer’s intended outcome and agreed first milestone |
| Responsibilities | The owner of each required task and any customer inputs |
| Setup | Confirmation that required access and configuration work |
| Training | The core task practiced, instructions shared, and questions recorded |
| First value | The useful result achieved, its date, and supporting evidence |
| Handoff | The ongoing support route and owners of remaining work |
Keep this record focused on applicable tasks and their completion evidence. Review outstanding items at each check-in, update the next action, and preserve the result when the initial journey closes.
Choose the right level of assistance
Zendesk distinguishes three onboarding models: self-service, low-touch, and high-touch. They differ in how much direct assistance the customer receives.
| Model | How help is provided |
|---|---|
| Self-service | Customers work through the process independently using available guidance |
| Low-touch | Automated communication and shared support provide lighter assistance |
| High-touch | Dedicated representatives provide personalized guidance |
Choose the level of help according to the required setup, the customer’s familiarity with the task, and the need for coordination. Keep an accessible route to assistance alongside independent instructions.
For interface guidance, Nielsen Norman Group recommends contextual tips and testing whether the design can be made easier to learn before adding dedicated onboarding screens. Apply that advice to the interface portion of onboarding: show instructions where the relevant action occurs and test whether customers can complete it.
When selecting tools, prioritize the functions required by the process: a customer record, task ownership and status, reusable instructions, communication history, and milestone reporting. Specify the information each function must capture before choosing software.
Measure progress, completion, and time to value
Start by defining the customer group, the entry point, the required milestone, and the period allowed to reach it. For digital journeys, Amplitude’s funnel documentation counts conversion from an entry event through the required steps within a defined window. It also distinguishes unique-user counts from event and session counts.
Use these calculations as a basic reporting structure:
| Measure | Calculation or record |
|---|---|
| Setup completion rate | Customers completing required setup divided by customers starting onboarding, multiplied by 100 |
| Activation rate | Customers completing the defined activation action divided by customers starting onboarding, multiplied by 100 |
| Onboarding completion rate | Customers meeting all agreed exit criteria divided by customers starting onboarding, multiplied by 100 |
| Time to first value | Time of the first useful result minus the agreed start time |
For every rate, use the same starting group and state the observation window. Specify whether the unit is an individual user or a customer account, and count each unit consistently.
Amplitude defines time to value from sign-up to a meaningful benefit. If a report starts from a different event, label that start explicitly. Report how many customers reached value alongside the timing, and show those still waiting separately.
Check the activation definition as well as the count. Amplitude recommends validating activation actions against later behavior. Review whether the selected action reflects the intended outcome, then adjust the definition or the onboarding path when the evidence calls for it.
Improve the step where progress stops
Amplitude’s activation guidance recommends funnel analysis to locate stalled steps and testing changes to the path. Review incomplete milestones for missing inputs, access, unclear instructions, or a need for assistance.
After setup, check the intended outcome and the prerequisites that remain. Choose one change, specify the milestone it should improve, and compare completion and customer feedback afterward.
Frequently asked questions
Who is responsible for customer onboarding?
HubSpot describes customer success as a common process owner, with implementation, support, and product education contributing. Assign one coordinating owner and name the people responsible for individual tasks, including required customer inputs.
How long should customer onboarding take?
Base the timeline on the required setup, training, and first useful outcome. HubSpot’s checklist separates these activities. Assign target dates and measure the actual time to the agreed result.
When is onboarding complete?
Define completion through an observable outcome. HubSpot’s suggested exit criteria combine setup, initial training, and a first-value milestone. Add the support route and ownership of remaining work to the closing record so the customer knows what happens next.
Can existing customers need onboarding again?
New features and redesigned interfaces can create a need for further guidance, as Nielsen Norman Group explains. Provide instructions for the changed task at the point of use and retain access to refresher help.