# Dealer onboarding checklist for one shared system

> A dealer onboarding checklist for bringing many dealers onto one system: owners, data, roles, training and the first 30 days, in an order you can run.

Dealer networks · The Intellsys team · 18 November 2026 · 6 min read

A dealer onboarding checklist is the list of things that must be true before, during and after a dealer starts working in a brand's shared system: an owner named, the dealer's data loaded, people given the right roles, training done and the first leads followed through. The checklist below is built for onboarding many dealers at once, in waves, onto one system head office can see.

## The short answer

- Onboard in waves of dealers, not all at once and not one by one.
- Agree journeys, dispositions and roles once, before the first dealer joins.
- A dealer is onboarded when its first real leads have outcomes, not when logins exist.
- Give every dealer one named owner at head office for the first 30 days.
- Measure each wave before starting the next.

## What dealer onboarding has to achieve

Most dealer rollouts are judged by logins. Two hundred dealers invited, a hundred and eighty signed in, job done. Three months later, half are back on registers and group messages.

A dealer is onboarded when its people use the system for real work, every day, because it helps them sell. That is a higher bar than access, and it is the only one that gives head office [visibility of the network](https://intellsys.cloud/blog/dealer-network-visibility).

The work splits into what head office does once for everyone, and what happens for each dealer. Mixing the two is the usual reason rollouts drag: each dealer reopens questions that should have been settled before the first one joined.

| Done once, for the network | Done for each dealer |
| --- | --- |
| Lead journey, stages and dispositions | The dealer's store, staff and catalogue loaded |
| Roles, reporting hierarchy and territories | Each person given a role and sign-in |
| Routing rules and the escalation clock | A training session on the dealer's own leads |
| The six numbers head office will watch | A named owner and a 30-day check |

## The dealer onboarding checklist

Run this list for each wave. The routing rules in item four are explained in [lead routing to dealers](https://intellsys.cloud/blog/lead-routing-to-dealers). The first four items are settled once, before the first wave, and checked again before each one after.

- [ ] **Name the owner** One person at head office owns the rollout, and one owns each wave of dealers.
- [ ] **Fix the journey** Stages, required fields and dispositions agreed, written down and tested with two dealers.
- [ ] **Set roles and hierarchy** Dealer principal, sales manager, salesperson, area and regional manager, each with what they may see.
- [ ] **Write the routing rules** Territory, fair share, capacity and the clock for untouched leads, approved by sales.
- [ ] **Load the dealer** Store details, staff list, territory and catalogue checked by the dealer before go-live.
- [ ] **Invite every person** Each salesperson has a sign-in and has logged in once with the trainer present.
- [ ] **Train on real leads** The session uses the dealer's own open leads, not a demonstration account.
- [ ] **Move open leads in** Leads in registers and sheets are entered or imported, each with an owner.
- [ ] **Switch off the side channel** Head office stops sending leads by email or group message to this dealer.
- [ ] **Check the first week** Every lead received in week one has a logged call and a next action.
- [ ] **Review day 30** The six numbers for this dealer are read with the dealer principal.
- [ ] **Close the wave** Problems found are fixed in the setup before the next wave starts.

*Twelve items for onboarding a wave of dealers onto one system. The reader can tick each one; the page counts them.*

Item nine is the one most often skipped, and the one that decides whether the rest works. While leads still arrive by email, dealers will keep working from email.

## Rolling out to many dealers in waves

A wave is a group of dealers onboarded together, typically from one region so that one regional manager can follow it closely. The first wave should be small and should include at least one dealer you expect to struggle. You learn more from them than from the enthusiasts.

- **Weeks before** Journey, roles, routing and numbers agreed and tested with two pilot dealers.
- **Go-live week** Dealers loaded, people invited and trained, open leads moved in.
- **First week** Head office checks every new lead daily and calls dealers about specific gaps.
- **Day 30** Each dealer's six numbers reviewed; setup changes listed.
- **Before the next wave** Changes made once, for everyone, and the next region begins.

*The shape of one onboarding wave, from preparation to the review that decides whether the next wave starts.*

The durations are for you to set. A network of forty dealers in one state may run two waves. A national network may run eight. What stays the same is that nothing in the setup changes in the middle of a wave.

## Where dealer onboarding usually stalls

The same few problems come up in most rollouts. Each has a fix you can plan for in advance.

- **Staff turnover** Salespeople leave mid-rollout. Reassign their leads in bulk the same week.
- **Messy dealer data** Staff lists and territories are out of date. Have the dealer sign them off.
- **Low-end phones** Training assumes a laptop. Train on the phone people actually carry.
- **Leads still on email** Head office keeps a side channel open. Close it, dealer by dealer.
- **Unclear outcomes** Salespeople guess dispositions. Give each a one-line meaning.

*Five common stalls in dealer onboarding, with the fix to plan for each before the first wave begins.*

Disagreement about outcomes deserves special care. If dispositions are vague, every dealer invents its own meaning in the first week. A tested list, with when to use each, is in [lead disposition](https://intellsys.cloud/blog/lead-disposition).

## How Intellsys OS onboards a dealer network

In Intellsys OS a business defines its own journeys, forms, dispositions, roles and territories before the first dealer joins. Each dealer store has its own catalogue and staff, and catalogues can be loaded by bulk import. Invitations and one-time sign-in codes go out by WhatsApp, SMS or email, and people can also sign in with passwords, Google or Microsoft. Permissions go down to a single record, by role, by reporting hierarchy and by geography.

When people leave mid-rollout, their work can be reassigned in bulk, round-robin, with an audit log. A business switches on the modules it needs, and Dealer Network takes each dealer through verification and an agreement signed online. More on the [workspace each business gets](https://intellsys.cloud/platform/workspace), and on the [dealer management system](https://intellsys.cloud/blog/what-is-a-dealer-management-system) as a whole.

> **How Intellsys OS handles it.** Intellsys OS sends dealer invitations and one-time sign-in codes by WhatsApp, SMS or email, onto journeys, roles and dispositions the brand set once for every dealer.

## Questions people ask

### What should a dealer onboarding checklist include?

An owner, an agreed journey and dispositions, roles and hierarchy, routing rules, the dealer's data loaded, every person invited and trained on real leads, open leads moved in, side channels closed, a first-week check and a 30-day review.

### How long does it take to onboard a dealer onto a new system?

It depends on the network. The setup done once for everyone takes the longest. After that, each wave of dealers needs a go-live week and a 30-day review, so plan in waves rather than per dealer.

### Should we onboard all dealers at once?

Rarely. A small first wave, usually one region, finds the problems in the setup while they are cheap to fix. Fix them once, for everyone, then start the next wave.

### How do you know a dealer is really onboarded?

When its people log real leads every day without being chased. A simple test: every lead the dealer received in its first week has a logged call and a next action, and at day 30 most closed leads carry an agreed outcome.

---

[Request a demo](https://intellsys.cloud/demo) · [Blog](https://intellsys.cloud/blog)

This is the Markdown version of https://intellsys.cloud/blog/dealer-onboarding-checklist. Intellsys is built by GrowthJockey, a full stack venture architect.
