# From Closed Deal to Onboarded: The Customer Onboarding Workflow, With and Without an AI Agent

By Mantas Aleksiejevas

> The customer onboarding workflow from closed deal to onboarded, step by step. How each step runs the usual way, and how it runs with Obi, an AI agent.

URL: /blog/customer-onboarding-workflow
Published: 2026-10-21
Target keyword: customer onboarding workflow

**Quick answer:** A customer onboarding workflow is the set of steps between a closed deal and a customer who is set up and using your product. It usually runs in eight steps: the deal closes, kickoff, discovery, the plan, setup, follow-ups, progress tracking, and handover. Most teams run each step by hand, with calls and emails. Obi, Cor's AI onboarding agent, runs most of these steps with each customer on a live session. It emails each new customer first, learns their goal and builds a plan. An admin on your team confirms the plan, then Obi sees the customer's screen and works through setup with them. It follows up by itself when a customer goes quiet. Your team gets a report after every session and steps in when something needs a person.

## The workflow at a glance

| Step | The usual way | With Obi, AI Onboarding Manager |
|---|---|---|
| 1. Deal closes | Sales hands the account to onboarding. Someone sends a welcome email and books a kickoff. | The customer is added to Cor, directly or through an integration. Obi emails them first. |
| 2. Kickoff | A kickoff call is scheduled around both calendars and time zones. | The customer starts a live session when they are ready, any time of day. |
| 3. Discovery | A person asks about goals, team and current tools, often on the same call. | Obi runs a discovery conversation and asks questions when it needs more context. |
| 4. Plan | Someone writes an onboarding plan, often from a template. | Obi builds a plan for that customer's goal, in their preferred language. An admin on your team confirms it before any work starts. |
| 5. Setup | Setup calls, screen shares and help docs. The customer does the rest alone. | Obi sees the customer's screen and works through setup with them, step by step. Where you permit it, it completes steps for them. |
| 6. Follow-ups | Your team chases customers who stalled, by email and calls. | Obi follows up by email when a customer goes quiet. |
| 7. Progress tracking | The team updates a tracker or CRM and asks customers where they are. | Every session ends with a report. Session data syncs to your CRM, on every plan. |
| 8. Handover | Notes are passed to the account owner. Context gets lost. | Obi hands over by email, Slack or Cor Admin, with what the customer was doing, what blocked them and what needs follow-up. |

## Each step, written out

### 1. The deal closes

**The usual way.** Sales marks the deal as won. The account moves to an onboarding manager or CSM. They send a welcome email and try to book a kickoff call. The customer waits until that call.

**With Obi.** You add the new customer to Cor, either directly or through an integration. Obi then emails them first. Your team doesn't need to trigger it. Every new customer hears from Obi straight away, not when a calendar slot opens. If Obi is embedded in your product, customers can also start with it there.

### 2. Kickoff

**The usual way.** The kickoff is a scheduled call. It has to fit both teams' calendars. Customers in other time zones get early or late slots, or wait longer.

**With Obi.** There is nothing to schedule. The customer starts a live session from a link, from your onboarding portal, or from inside your product, whenever it suits them. Obi appears on their screen, greets them and confirms what they want to get done today. Sessions run 24/7, in the customer's time zone.

### 3. Discovery

**The usual way.** On the kickoff call, a person asks what the customer wants to achieve, who will use the product, and what tools they use now. The answers end up in call notes.

**With Obi.** Obi starts by learning the customer's goals and their setup. There is no fixed script. When it needs more context, it asks. It already knows who the customer is from the details your product passes to it, such as plan, account tier or signup date, so it doesn't ask what you already know.

### 4. The plan

**The usual way.** Someone writes the onboarding plan, often by copying a template and editing it. The plan lives in a document or project tool.

**With Obi.** Obi builds a plan for that customer's goal, in their preferred language. An admin on your team confirms the plan before any work starts. Then Obi leads the customer through it, step by step, and adjusts as things change. Your team decides the standard steps in advance. You walk Obi through your process once, and it turns it into session guides you review before going live.

### 5. Setup

**The usual way.** Setup happens across several calls and screen shares. Between calls the customer works from help docs. When they hit a step they can't get past, they stop and wait for the next call.

**With Obi.** The customer shares their screen and Obi sees exactly what they see, in their real account. Obi walks them through setup, integrations and configuration one step at a time, and answers questions as they come up. It follows the customer across tabs, windows and the other tools they connect, so integrations and data migrations are covered too. Where you permit it, Obi completes steps on the customer's behalf. It only starts once an admin has confirmed the plan, and it asks for confirmation before major actions.

### 6. Follow-ups

**The usual way.** Customers get stuck between calls and go quiet. Your team notices days later, sends a follow-up, reschedules and waits again.

**With Obi.** When a customer goes quiet between sessions, Obi follows up with them by email, by itself. Your team doesn't have to notice first. When the customer comes back, Obi picks up the plan where they left off.

### 7. Progress tracking

**The usual way.** The team keeps a tracker or updates the CRM by hand. To find out where a customer is, someone has to ask them.

**With Obi.** After every session, Obi writes a report: what the customer got done, where they got stuck, and what needs follow-up. You also get the recording and the transcript. A running issue log collects the knowledge gaps and blockers from every session. Your team can ask Cor plain questions across all sessions, such as "which accounts are struggling?". Session data and account-level friction signals sync to your CRM. CRM sync is on every plan.

### 8. Handover

**The usual way.** When onboarding ends, or when a problem needs an expert, notes are passed to the next person. Some context is lost, and the customer repeats themselves.

**With Obi.** When something needs a person, Obi hands over to your team. It passes on what the customer was trying to do, what blocked them, and what your team needs to pick it up. You set when this happens: by question type, customer tier or session stage. The handover reaches your team by email, in Slack and in Cor Admin. After onboarding, Obi can stay inside your product to help with new workflows and features.

## What your team still does

Obi takes on the repeated onboarding work. Your team stays in charge of how it runs.

- **Teach Obi once.** Connect your help docs (direct integrations for Intercom and Zendesk), upload screen recordings or walk through your key workflows, and test a session yourself before any customer sees it.
- **Set the rules.** Choose what Obi will and won't discuss, when it hands over to a person, and which actions it can take by itself.
- **Approve each plan.** An admin confirms Obi's plan before any work starts.
- **Approve critical changes.** Changes to what customers see must be approved in Cor Admin. Obi can't approve them.
- **Take the handovers.** Work the accounts and questions that need a person.
- **Improve from real sessions.** Review reports and the issue log, then fix gaps in the portal. You can also do this from Claude or ChatGPT through Cor MCP.

## When this workflow fits

It fits B2B software where every customer needs a slightly different setup, where setup has many steps or spans several apps, and where customers sit in many time zones. It matters less when setup is one or two clicks.

## FAQ

**What is a customer onboarding workflow?**
A customer onboarding workflow is the set of steps that takes a new customer from a closed deal to being set up and using your product. The usual steps are kickoff, discovery, a plan, setup, follow-ups, progress tracking and handover. Many teams run these by hand with calls and emails. Some now use an AI agent such as Obi to run the steps with each customer.

**Can an AI agent run customer onboarding from closed deal to handover?**
Yes, most of it. Obi emails each new customer, learns their goal, builds a plan, and works through setup with them on a live session where it sees their screen. It follows up by email when a customer goes quiet. Your team gets a report after every session and takes over when something needs a person. Your team still sets the rules, confirms each plan and approves critical changes.

**Do customers still need a kickoff call with our team?**
No, not to get started. The customer starts a live session with Obi whenever it suits them, from a link, your onboarding portal or inside your product. Obi greets them, confirms their goal and starts the work. You can still hold a call for accounts that need one.

**How does our team see where each customer is?**
Through the report Obi writes after every session. It shows what the customer got done, where they got stuck and what needs follow-up, with the recording and transcript if you want them. Your team can also ask Cor plain questions across all sessions, and session data syncs to your CRM on every plan.

**What happens when a customer gets stuck?**
Obi sees their screen and works through the blocker with them during the session. If it can't clear it, Obi hands over to your team by email, Slack or Cor Admin, with what the customer was trying to do and what blocked them. If a customer goes quiet between sessions, Obi follows up with them by email.