Customer Onboarding Templates: Free Plan, Forms and Emails
Free customer onboarding templates in Excel: a plan that tracks first value, handoff and intake forms, a kickoff agenda, training plan and welcome emails.

Customer onboarding helps a new customer start using a product or service and reach an agreed early result, such as processing the first 50 online orders.
- Agree that result, its target date and how you will confirm it. This workbook measures time to first value from the kickoff meeting.
- Give each task an owner and a due date. Review blocked tasks separately because the workbook excludes them from its overdue totals.
- Use the sales handoff and customer intake form to prepare for the kickoff, then confirm goals and responsibilities together.
- Plan training around each role's tasks. Track course completion and check practical use separately when the task requires it.

Learn faster with AI powered courses, quizzes, and flashcards
Customer onboarding helps a new customer start using your product or service and reach an agreed early result. Below are six free templates in an Excel workbook, a completed example, and guidance on choosing the tasks, training and follow-up each customer needs.
I'm the CEO of Coursebox, where we make white-label LMS software, and I've spent over a decade selling, supporting and demoing learning platforms.
The completed example follows a fictional software company helping a three-venue restaurant group start taking online orders. On 19 October 2026, 12 of its 20 onboarding tasks are done, two are overdue and one is blocked. We'll use that plan throughout the guide to show what the team should do next.
Download the blank workbook for your own plan, or open the completed example to see the forms, emails and calculations together.
Six templates in each Excel workbook: onboarding plan, sales handoff, training plan, intake form, kickoff agenda and five emails. The completed example also includes three sample tabs. Its PDF contains the completed templates and those samples. No email required.

View the onboarding plan preview at full size
Which customer onboarding template do I need?
Each tab in the workbook does a different job, at a different point in the onboarding.
| Template | Job | Who fills it in | When |
|---|---|---|---|
| Handoff form | Passes what the customer bought, why and what was promised from sales to onboarding | Account executive | Before the kickoff |
| Intake form | Collects the details setup needs, so nobody chases them later | The customer | Before the kickoff |
| Kickoff agenda | Runs the first meeting and ends with first value and its date written down | Onboarding manager | Day 1 |
| Onboarding plan | Tracks every task, owner and due date, and works out what is overdue or blocked | Onboarding manager, shared with the customer | From kickoff to handover |
| Training plan | Lists what each customer role must be able to do, the course, and who has finished | Onboarding manager | During setup |
| Welcome emails | Five emails from signing to the 30-day check-in | Onboarding manager | Days 0 to 30 |
What is customer onboarding?
A customer may have bought software to reduce phone orders, save time preparing reports or make bookings easier. Onboarding connects that goal with the setup, guidance and support they need to begin using it. Reaching an early result gives you a practical point to review progress; the wider customer relationship continues after that.
Customer onboarding, user onboarding, implementation or training?
Customer onboarding can include implementation, user guidance and training. Each covers a different part of getting started.
| Term | What it covers | Who runs it | It ends when |
|---|---|---|---|
| Customer onboarding | Helping a new customer get started and reach an agreed early result | A customer success or onboarding team, with automated guidance where useful | The agreed onboarding goals and handover conditions are met |
| User onboarding | Helping a person learn how to use a product | Product guidance, support or a trainer | The user can complete the relevant starting tasks |
| Implementation | The technical setup: data, integrations, configuration | Implementation team | The system works as agreed |
| Customer training | Teaching each customer role to use the product | Onboarding team or a customer academy | Each role can do its tasks |
| Employee onboarding | Bringing a new staff member into your own company | Manager and HR | The agreed induction and role preparation are complete |
| Client intake | Collecting what a service business needs to start work | Agency or practice | Work can begin |
Here's how they fit together for the restaurant group.
For the restaurant group, implementation means importing menus, installing printers and connecting the point-of-sale (POS) system, which records sales. Training teaches kitchen staff to handle an order. User onboarding helps a cook find and use those controls on the tablet. The customer's overall onboarding plan brings these activities together, with a goal of processing the first 50 online orders across all three venues.
The stages of customer onboarding
| Stage | What happens | Example from the restaurant group |
|---|---|---|
| Handoff | Sales passes on what was sold, why, and what was promised | "Live at venue 1 before the end of October" |
| Kickoff | Both sides meet, agree first value and its date, and accept the plan | First 50 online orders by 30 October |
| Setup | Data, configuration and integrations | Menus imported; printers installed; POS integration |
| Training | Each role learns what it needs | Admins 15 minutes, kitchen 5 minutes, front of house 8 minutes |
| First value | The customer gets the result they bought | First 50 online orders across three venues |
| Check-in and handover | Review results and risks, then hand to the account manager | One-month check-in on 2 November; planned handover on 6 November |
First value and time to first value
First value is an agreed early result that shows the customer has started getting something useful from the product. Choose it with the customer. For this restaurant group, the milestone is 50 online orders. Another customer might need to send its first invoice or publish its first course. Completing setup can be necessary for that result without being the result itself.
Time to first value measures how long it takes to reach that milestone. This workbook counts calendar days from the kickoff meeting; use the same starting point when comparing customers. Enter the actual result date once it happens. A shorter time can indicate quicker progress, but also ask whether the customer can use the product and whether important problems remain.
High-touch, low-touch and tech-touch
- High-touch: substantial personal support, such as a named lead, planning meetings and live training. This can suit complex rollouts involving several teams.
- Low-touch: more of the work is self-guided, with personal help at selected points. A team might combine a kickoff call, short courses and scheduled check-ins.
- Tech-touch: onboarding delivered mainly through the product, automated messages and help resources. Customers can still have a route to human support.
These labels describe the amount of personal support, rather than fixed customer sizes. Choose according to the work involved, the customer's experience and the support you can provide. The restaurant example combines a kickoff, self-paced courses, installation support and a live questions session.
When templates are the wrong tool
- Hundreds of customers onboarding at once: a customer success or project tool tracks them better than one workbook per customer.
- Regulated identity checks, such as opening a bank account: that's a compliance process with its own required forms, not this kind of onboarding.
- Self-serve products: use the workbook to plan the experience internally if helpful. Customers may only need in-product guidance, emails and a way to ask for help.
How to onboard a customer with the templates
The steps follow the restaurant group from the signed contract to the 30-day check-in.
Step 1: Get the handoff in writing
Before the kickoff, ask the salesperson to complete the handoff form. It records what the customer bought, why they bought it, the promises made and the result they want in 90 days. The onboarding lead can then confirm these details with the customer instead of starting the conversation from scratch.
The restaurant group's reason was "We lose orders on the phone on Friday nights." The promise was live at venue 1 before the end of October. The risk was a POS provider that is slow to issue access keys.
Step 2: Send the intake form before the kickoff
The intake form collects what setup needs: opening hours, where the menus live, the POS and website, and staff numbers by role. Send it with the welcome email, so the kickoff is about decisions, not data collection.
If the product handles payments, the customer sets up their payment account in the provider's portal. The intake form says so, and nobody on your team should ask for account numbers in an email or a spreadsheet.
Step 3: Agree first value at the kickoff
The kickoff agenda runs for 60 minutes and ends with four decisions written down: first value, its target date, who the customer's admins are, and the launch order. For the restaurant group, that was the first 50 online orders by 30 October, one admin per venue, and venue 1 first.
Step 4: Assign the work and follow up delays
The Side column identifies whose work a task involves: Us, Customer or Both. The Owner column names the person who will follow it up. Keep both: a shared task still needs someone to arrange the next action. In this example, the website link and kitchen training need attention from the restaurant team, while the software company's implementation specialist follows up the blocked POS integration.

View the onboarding task-status diagram at full size
The onboarding plan as at 19 October
Example: Fictional software company onboarding a three-venue restaurant group, as at 19 October 2026.

- 1. Overdue customer tasks: The website link is five days late and kitchen training is three days late. Agree who will finish each task and when.
- 2. Blocked: The POS integration is waiting for the provider's access key. Its due date has passed too, but this workbook shows Blocked ahead of Overdue. Review blocked tasks separately; the overdue count does not include them.
- 3. Days to target: 11 days left to reach first value by 30 October.
Open this plan preview at full size
Update the As at date to review a particular day. Status shows Done, Blocked, Overdue or Open, while Days late preserves lateness for completed tasks. Clear Blocked by when a task can proceed. The summary counts shared overdue tasks under Overdue: us, so check the task rows as well as the totals.
Step 5: Train each role on what it needs
Start with the tasks each role needs to perform. Kitchen staff need to accept and complete orders; venue admins also need to change menus and opening hours. Give each group the relevant instructions and a chance to try the task. The example's 5-, 8- and 15-minute courses are suggested lengths for those particular tasks, not limits for every customer.
The customer training plan by role
Example: Illustrative role-based training plan for the same restaurant group.

- 1. Kitchen staff: 10 of 12 people have completed the course, leaving two unfinished after the due date. The sheet does not record when those ten completed it.
- 2. Front of house: 7 of 18 finished, but the due date is two days away, so it is still Open.
Open the training plan preview at full size
A short course can cover a walkthrough customers need repeatedly. In a Coursebox sales call, a restaurant software company described plans to replace its reps' 30-minute merchant walkthroughs with 5- to 15-minute courses and track completion. A course outline template helps you plan each one.
The training plan counts completions by role. A completion tells you someone finished the course or session; it does not show that they can handle an order correctly. Use a practice task or observation when you need to check that. Enter zero in Completed when nobody has finished, rather than leaving the count unknown.
Step 6: Send emails that explain the next action
The workbook includes five suggested messages, from signing to the first-month check-in. Adjust their timing to the actual plan. The welcome email names the person leading onboarding and gives the customer separate links to book the kickoff and provide setup details.
Send it the day the customer signs, from the person who will run their onboarding.
Subject: Welcome, and what happens next Hi [Name], Welcome aboard. I'm [Onboarding manager], and I'll look after your onboarding. Our first step is a 60-minute kickoff to agree your first goal, target date and responsibilities. Please book a time here: [Booking link]. Before then, please fill in the intake form: [Intake link]. Thanks, [Onboarding manager]
- [Name]
- : The customer's main contact (for example, Sam)
- [Onboarding manager]
- : Your name (for example, Alex)
- [Booking link]
- : The link for booking your kickoff meeting (for example, Your calendar booking page)
- [Intake link]
- : The link to your customer intake form (for example, Your shared intake form)
Step 7: Review the result and agree the handover
At the first-month check-in, ask what the customer has achieved, what remains difficult and who needs more help. Review the result date, unfinished tasks and support questions together. The restaurant example schedules that conversation for 2 November and a handover for 6 November. Those are planned dates: if an important task is still blocked, agree how it will be resolved and who will own it after handover.
Customer onboarding samples for other situations
The completed workbook includes three further illustrative samples. Use them to change the amount of support, the sequence and the questions, rather than applying the restaurant plan to every customer.
Enterprise rollout over 12 weeks
An illustrative 12-week rollout for a 2,000-person customer. Training for the pilot group must be ready before they start using the system; wider staff training follows before the full launch.
| When | Stage | What happens | Owner |
|---|---|---|---|
| Week 0 | Handoff | Sales hands over the contract, goals and promises made | Account executive |
| Weeks 1 to 2 | Kickoff and plan | Steering group meets; first value and the go-live date agreed | Onboarding lead |
| Weeks 2 to 6 | Setup and integration | Single sign-on, user import and data checks | Implementation team |
| Weeks 5 to 8 | Pilot | Train the pilot group, launch one department and resolve issues before wider rollout | Customer project lead |
| Weeks 8 to 10 | Training | Admins trained live; users get a short course by role | Onboarding lead |
| Week 10 | Go-live | All departments live; first value measured | Both |
| Week 12 | Review and handover | Results against the goal; handover to the account manager | Onboarding lead |
A pilot gives the team a chance to find problems with a smaller group. Decide what needs to work before the wider launch, such as a successful sign-in, an accurate data import and completion of a core task.
Self-serve onboarding with no calls
An illustrative self-serve sequence for customers who sign up online. The days below are suggested review points. Send a message only when its trigger applies, and stop reminders once the task is done.
| Day | Trigger | What they get | Goal |
|---|---|---|---|
| 0 | Account created | Welcome email with one first step and a 3-minute video | Log in again |
| 1 | First step not done | Reminder with the most important first step | First step done |
| 3 | First step done | Short course in the customer academy: the core feature | Use the core feature |
| 7 | Core feature not used | Email with a customer example and a booking link for help | Use the core feature |
| 14 | Core feature used 3 times | Invite to the advanced course and the community | Return to the core task |
| 30 | Any | Check-in email with their usage and one next step | Agree the next useful step |
Offer a way to get help when a customer cannot complete the next task. A usage trigger can tell you where they stopped; it does not tell you why. They may need an explanation, a permission change or a product fix.
Client intake for an agency or practice
For an agency or practice, begin with the intake form, kickoff agenda and emails. Replace the restaurant-specific questions about menus, venues and payment systems with the information your service needs. Keep the training plan only if the client must learn a process or tool.
| Section | What to ask | Why |
|---|---|---|
| Contacts | Who decides, who approves, who sends us information | No waiting on the wrong person |
| Goals | What a good result looks like in 3 months | Agree success before work starts |
| Access | Accounts and logins we need, shared through a password manager | Never by email |
| Documents | Contracts, brand files or last year's records | Everything in one place on day one |
| Ways of working | How often to meet, how to report, response times | No surprises in month one |
Timi Csontos: introductory learning before a call
Leadership coach Timi Csontos was repeatedly answering introductory questions from people considering a coaching career. She turned an existing webinar slide deck into a free Coursebox mini-course and reviewed the generated content before sharing it.
Her journey starts with the course, followed by an optional one-to-one call and then an introduction to formal coach training when appropriate. This is a pre-sales education example rather than a post-purchase implementation. It shows how an agency or practice could let people learn the basics before a personal conversation, while keeping that conversation available.
When customer onboarding templates are not enough
- To train many customers at once, run a customer academy on a white-label LMS and compare options in this guide to the best LMS for customer training.
- To onboard resellers or partners, see how to build a channel partner training programme.
- To build the courses themselves, start with how to create training modules.
Version 1.1, reviewed 19 October 2026 in Excel on Windows. The workbook does not send emails or reminders. It has 50 task rows and 15 training-role rows. Use the supplied rows, preserve the grey formula cells, and recheck the formulas and summary ranges before extending them.
Starting your next customer onboarding
Start by agreeing what the customer wants to achieve. Use the forms to collect the information, the plan to assign the work, and the check-in to decide what happens next. If you need a place to deliver and track the training, explore Coursebox's white-label LMS.
Frequently Asked Questions
A plan with tasks, owners on both sides and due dates; a handoff from sales; an intake form; a kickoff agenda; a training plan by role; and welcome emails. The plan should show first value and its target date.
Base the schedule on the result the customer needs, the setup work and the people involved. A self-serve customer may get started in days; a complex rollout can take months. Agree milestones together and review delays before changing the target.
Customer onboarding covers the new customer's overall start, including setup, training and support. User onboarding focuses on helping one person learn to use the product. Both can combine automated guidance with personal help.
A form the customer fills in before the kickoff with the details setup needs, such as systems, contacts, hours and staff numbers. In banking, the same phrase means identity checks, which follow their own regulations.
Name one person responsible for coordinating the plan, often an onboarding or customer success manager. Assign customer-side tasks to named contacts too. In smaller teams, the same person may manage onboarding and the ongoing account.

Travis Clapp
Travis Clapp is the original founder and CEO of Coursebox. As an experienced instructional designer, he has lived through the process of building high quality courses. These experiences brought about his idea to upload all your documents and ideas into a virtual box that could convert those magically into a course. Prior to Coursebox, he successfully founded and built a social based LMS. Travis has 15+ years of experience designing courses and EdTech platforms from university MOOCs to enterprise LMS. Travis has built training for reputable companies like Johnson & Johnson, Electrolux, Michael Hill and SA Health. One of his courses reached 20,000+ learners which was a flagship edX course. He is based in the Adelaide, South Australia office and passionately works on customer support, sales and bringing the original product vision to life every day.


