What does it read, and what happens when the playbook does not cover something?

The plan and the records you authorize, and nothing else. What no step covers is named as a gap rather than improvised around. Which of your records are in scope is what the audit establishes.

Is this the same as the onboarding workflow for new joiners, or the one for vendors?

No. The joiner workflow runs a policy checklist about a person, and the vendor workflow chases documents from a company you are contracting with. This one runs your own playbook of steps for a customer, holds the dates and the terms for the owner, and decides nothing about whether the customer is onboarded.

Customer onboarding coordination

Onboarding went quiet and nobody owned the silence

Today

Where a customer stands is a question you answer by asking three people

The onboarding plan lives in a document somebody wrote, and it stops being followed once the real work starts.
A step had no owner until somebody noticed it had not happened.
The customer is waiting on something nobody wrote down.
Answering where they stand takes a round of messages to whoever might know.

With agents

Every step carries its owner, and the status is already written down

A step without an owner stops being invisible.
The status answer stops being assembled by asking people.
A hole in the playbook becomes visible instead of improvised around.

How an agent runs it

Your playbook already says what onboarding a customer involves. What it does not carry is an owner, a state and a waiting-on for every step, which is where the plan quietly stops being followed.

01

Holds

Keeps the onboarding plan your playbook defines for this kind of customer, with the accountable owner named on it from the first day, and reads only the records you authorize.

02

Tracks

Follows each step and each item against what the playbook requires, so where a customer got to is a record rather than a recollection.

03

Surfaces

Names what is missing, what is blocked, and what no step in the playbook covers, so a hole in the playbook reads as a hole rather than being filled in by the workflow.

04

Drafts

Prepares the outstanding-items request and the status note for the owner to send, edit or discard.

05

Human gate

Every date, every scope statement and every commercial term is the accountable owner's, and so is every message that reaches the customer and the decision that a customer is onboarded. The workflow commits the customer to nothing and sends nothing at all, anything the playbook does not cover goes to that owner, and the coordination can be run by hand at any point without the agent, because the plan and the records are yours rather than the agent's.

06

Reports

Shows where each customer stands and who each one is waiting on.

07

Records

Keeps completion against the plan, so the next onboarding starts from what the last one actually did.

Results

What changes when the playbook holds the dates

A step without an owner is visible

The plan carries its accountable owner from the first day, and an unowned step is reported like any other gap.

Status without the round of asking

Each step is tracked against the playbook, and the waiting-on sits on the record.

A hole in the playbook shows

What no step covers is surfaced rather than quietly filled.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from the playbook to a status note the owner sends. Dates, scope, commercial terms and the decision that a customer is onboarded are a person's. It extends toward a customer operations role and then a customer operations back office, as a possible next step rather than a promised state; How It Works shows how the commitment gate is built.

Tier 1 / Prove

How It Works

Questions, answered

No. Every date, scope statement and commercial term is the accountable owner's, and the workflow sends nothing to the customer at all: it drafts the request and the status note, and the owner sends, edits or discards. The gate is closed by default, what the playbook does not cover goes to that owner, and the plan and the records live in your systems, so the coordination can be run by hand without the agent.