121 CRM playbook · Customer onboarding

Move a new customer from agreement to a clear, owned start with the information, access and expectations they need.

A fictional consultancy opens an onboarding journey after a signed agreement, not merely after a sales-stage change. This playbook turns that kind of situation into an owned sequence with explicit stop points, exceptions and measures. Use only channels, data and capabilities approved for your setup.

Subscribe to 121 CRM Seller, billing and cancellationRead the automation guide

Customer Thread

Customer onboarding: the working sequence

Illustrative example

Confirm the handover
Check scope, commercial approval, owner and any unresolved sales promises.
Collect information safely
Request only necessary data through the approved channel.
Review readiness
A person confirms that prerequisites are met before service delivery starts.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Customer onboarding, with controls and handovers visible

The coded interface shows an example sequence using fictional data and does not expose a live CRM account.

121 CRM · Onboarding control room

Discover

Goals and dependencies

Prepare

Data and workflow inputs

Configure

Account and journeys

Customer tests the result

Handover

Owners and next review

Open decision

Migration history depth

Customer owner

Operations lead

Acceptance gate

Representative journeys pass

Illustrative exampleSequence only. Deliverables, timings, support and cost require an agreed scope.

What supports the playbook

See what the CRM can coordinate — and where your team steps in.

The CRM can organise the sequence, but the business still sets the rules, checks consent and handles the moments that need human judgement.

Capability 01

Contacts

Stores a person or lead with contact details, activity, ownership and related records.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 02

Opportunities

Represents a potential sale or deal linked to a contact, value, owner and pipeline position.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Shows which customer conversations are active commercial work rather than general contacts.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 03

Tasks

Creates assigned, dated and optionally recurring actions against contacts or opportunities.

How it works: Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it: Turns the next step into owned work instead of leaving it inside notes or inboxes.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 04

Workflow builder

Combines a start event with an ordered sequence of configurable actions.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Turns a repeatable customer process into a visible, reviewable flow.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Entry criteria

Begin with a valid trigger, enough context and one owner

A customer has accepted the approved offer and the business confirms the onboarding entry criteria. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A customer has accepted the approved offer and the business confirms the onboarding entry criteria.

Practical scenario

A fictional consultancy opens an onboarding journey after a signed agreement, not merely after a sales-stage change.

Human decision retained

Accountable owner

Name the person or queue that accepts the work, monitors exceptions and can stop the sequence.

The sequence

Run the customer onboarding playbook step by step

Each step should leave evidence a colleague can understand. Timing and channels should follow the customer context rather than a generic high-pressure cadence.

1. Confirm the handover

Check scope, commercial approval, owner and any unresolved sales promises.

2. Welcome with a plan

Explain contacts, milestones, information requests and the route for questions.

3. Collect information safely

Request only necessary data through the approved channel.

4. Create operational tasks

Assign setup, review and customer actions with due dates.

Close the loop

5. Review readiness

A person confirms that prerequisites are met before service delivery starts.

Owner, timing and exception

Make the operational state easy to review

The supporting view keeps the next action and human checkpoint visible around the automated steps.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314

11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Exception paths

Stop the normal route when the facts change

Exceptions are part of the process, not failures to be hidden. Route them to a person with the authority and context to decide what happens next.

Human review

Scope mismatch

Pause and resolve the promise rather than pushing the customer through a standard checklist.

Human review

Missing or sensitive information

Use the approved secure route and clarify why it is needed.

Human review

Delayed customer action

Adjust dates transparently and avoid repetitive automated chasing.

Operational review

Measure whether the work became safer and clearer

Use measures that reveal ownership, service quality and control. Counts of messages, tasks or workflow runs are supporting signals, not proof of customer value.

Onboardings with a named owner and plan

Check completeness at entry.

Milestones completed on time

Separate customer, business and dependency delays.

Early questions and exceptions

Use them to improve instructions and handover.

Questions about this page

Useful answers, without the sales fog.

1. When should the customer onboarding playbook start?

A customer has accepted the approved offer and the business confirms the onboarding entry criteria. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action.

2. Which channels should the customer onboarding playbook use?

Use only configured channels that suit the purpose, customer preference and consent position. Give each channel a distinct role and check provider availability and usage charges before launch.

3. When should customer onboarding automation stop?

Stop when the purpose is complete, the customer responds or opts out, the data conflicts, or an exception needs judgement. In this playbook, pay particular attention to scope mismatch, missing or sensitive information, delayed customer action.

4. How should we judge whether customer onboarding works?

Review onboardings with a named owner and plan, milestones completed on time, early questions and exceptions. Combine the numbers with sampled records and customer context; do not treat activity volume as a business outcome.

Read all CRM questions

Continue the journey

Onboarding and support Tasks and activities Customer management Renewal follow-up

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing