In short
A customer onboarding call should end with four things written down - the customer's goals in their own words, a named owner on each side, agreed dates, and the first milestone. Send an agenda beforehand, confirm who does what during the call, and send the notes the same day.
A customer onboarding call should end with four things written down: the customer's goals in their own words, a named owner on each side, agreed dates, and the first milestone. Everything else on the call serves those four. If the call ends without them, the implementation starts on assumptions.
This guide gives an onboarding call agenda, a checklist for running the call, a notes template, and what to do about recording a kickoff call with a new customer.
How to run a customer onboarding call
- Read the sales notes first. What the customer said they needed, who was involved, what was promised. Do not make the customer repeat what they already told your colleagues.
- Send the agenda two days before. Include who you expect to attend and ask the customer to add anything.
- Open with roles. Everyone says their name and what they are responsible for in this project. Write it down.
- Ask for the goals in their words. "What does success look like in three months?" Write the answer as they say it.
- Agree how success will be measured. A number, a date or an event the customer will recognise.
- Walk through the plan and set the first milestone. Something that can be done within two to four weeks, with a date.
- List what each side needs from the other. Access, data, a contact, a decision. Each item gets an owner and a date.
- Agree how you will stay in touch. The channel, the cadence, and who to call when something is stuck.
- Read back the goals, owners, dates and milestone. Before anyone leaves.
- Send the notes the same day. Ask the customer to correct anything wrong.
The onboarding call agenda
| Time | Item | Output |
|---|---|---|
| 0:00 | Introductions and roles | Who owns what, both sides |
| 0:10 | Goals and what success looks like | Goals in the customer's words |
| 0:25 | How success will be measured | One or two measures |
| 0:30 | Plan and first milestone | Milestone with a date |
| 0:40 | What each side needs from the other | Owned, dated list |
| 0:50 | How we will work together | Channel, cadence, escalation |
| 0:55 | Read-back | Agreement on the notes |
Sixty minutes is typical. For a small product, the same structure fits in 30.
Why the customer's own words matter
Goals written in your terms drift towards what your product does. "Improve reporting efficiency" could mean anything. "Priya's team stops spending the first two days of each month building the Northwind report by hand" tells everyone what done looks like.
Write down the customer's phrasing, and use it back:
- In the plan. The milestone is expressed as progress towards their goal.
- In check-ins. "Last time you said the report took two days. Where is it now?"
- At the first review. A quarterly review that measures against the goals set here has something real to talk about; see running a quarterly business review.
The customer onboarding notes template
# Onboarding kickoff — <customer> — <date>
## Who owns what
| Role | Customer | Us |
| ----------------------- | -------- | ------ |
| Accountable for outcome | <name> | <name> |
| Day-to-day contact | <name> | <name> |
| Technical / IT | <name> | <name> |
## Goals, in their words
- "<quote>"
- "<quote>"
## How we'll measure success
- <measure> — <baseline, if known> — <target> — <by when>
## First milestone
- <what> — <date> — <owner>
## What we need from them
- <item> — <owner> — <by when>
## What they need from us
- <item> — <owner> — <by when>
## How we'll work together
- Channel: <email, shared channel>
- Check-ins: <cadence, day, time>
- If something is stuck: <who to contact>
## Risks and open questions
- <item> — <owner>Put the "who owns what" table and the first milestone at the top of the email you send. They are what the customer's own team will look for.
Action items that get done
Every item on both "need" lists is an action item. The usual rules apply: one owner, a date, and a description someone else could act on. "Access to the sandbox" is vague; "Tom (Northwind IT) creates a sandbox login for Ana by 9 October" is not. Writing action items that get done goes further.
Pay particular attention to what you need from the customer. Onboarding often stalls waiting for access, data or a decision on the customer's side, and nobody noticed because the item was never written down with a name next to it.
After the call
- Send the notes the same day. Ask for corrections by a specific date.
- Put the milestone and check-ins in both calendars.
- Hand the notes to anyone joining later on your side, so the customer does not have to explain their goals a third time.
- Keep them with the account's other notes. Client meeting notes covers keeping a record across a customer relationship.
Recording the onboarding call
A recording helps with the exact goals and the long list of who does what. It needs the customer's agreement:
- Ask in the invite. "We'd like to record the kickoff so we get the plan right. Tell us if you'd prefer we didn't."
- Ask again at the start, and accept a no.
- Check your own company's policy and the customer's. Some customers do not allow suppliers to record, and in some places the law requires everyone on a call to agree.
For the options on a Mac, recording client calls on a Mac covers them in detail. With Notey, the call is recorded and transcribed on your Mac. Nothing joins the call, so the customer knows it is being recorded only because you asked, which is why you ask. Your side and the customer's side are on separate tracks, so each line is labelled You or Them, and you can name the customer's side for the meeting. After the call you can search for the moment they described their goals and check your notes against their exact words. If you sign in and ask for notes, only the transcript text is sent, and the action items come back labelled as AI-generated, with a plain statement when nobody committed to anything. Check owners and dates against the transcript before you send them to the customer.
Common mistakes
- Making the customer repeat the sales conversation. Read the notes first.
- Goals in your words. Keep theirs.
- No owner on the customer's side. The implementation waits for someone nobody named.
- A first milestone months away. Pick something that can happen within a few weeks.
- Notes sent a week later. Send them the same day, while corrections are easy.
For how an onboarding call compares with the other meetings a customer relationship involves, see types of meetings.
Frequently asked questions
What is a customer onboarding call?
The first working meeting after a customer signs, often called a kickoff. It agrees what the customer wants to achieve, who is responsible on each side, and the dates for getting started.
What should be on an onboarding call agenda?
Introductions and roles, the customer's goals, what success looks like and how it will be measured, the plan and first milestone, what each side needs from the other, and how you will stay in touch.
Who should join a kickoff call with a new customer?
On the customer's side, the person accountable for the outcome and the person who will do the day-to-day work. On yours, whoever owns the account and whoever will run the implementation.
What should I send after an onboarding call?
The notes, the same day, with the goals, owners, dates and first milestone at the top. Ask the customer to correct anything wrong; it is easier to fix a misunderstanding in week one than in month three.
Can I record a customer onboarding call?
Only if the customer agrees. Ask in the invite and again at the start, and accept a no. Some customers' policies do not allow it, and in some places everyone on a call has to agree.