Skip to content
ONE3.ai

How it works · Flow F1

From sign-up to first value in one guided session

A new business or an agency sub-account is set up by a Copilot interview, an Onboarding Agent proposal and one owner approval. Agents start in shadow mode.

What the Tenant onboarding flow does

Onboarding is the first flow every tenant runs, and it sets the pattern for everything after it: the system proposes, a human approves, and then One3 acts.

A business signs up directly, or an agency partner creates a client sub-account. The Copilot interviews the owner about industry, size, channels and goals. The Onboarding Agent turns the answers into a plan: which Packs to install, which pipelines and roles to create, which automations to switch on and which Digital Employees to start. The owner approves the plan before anything is installed.

After approval, One3 installs the Packs with seed configuration and a brand kit, connects the tools the business already uses, imports data with AI-assisted mapping and deduplication, and invites the team. Agent identities are created in shadow mode, so they propose and humans act until they earn more autonomy.

The plan's target is time to first value under 30 minutes (target). The platform modules this flow uses are in the Year-1 boundary (W0–W1).

Every step on this page is an Action: a typed verb with a risk tier (R0 read-only to R4 irreversible or financial), a permission check and a reversibility class. Agents and humans call the same Actions, so the same approval rules apply whether a person clicks a button or a Digital Employee acts.

Tenant onboarding, step by step

Ten steps from sign-up to the first recommended actions. Human gates are marked with their risk tier.

  1. 1

    1. Sign up or partner creates a sub-account

    **Platform · Tenants & Workspaces.** A business signs up, or an agency partner creates a client sub-account under its partner tier. Event: `tenant.created`.

  2. 2

    2. Verify and create the tenant

    **Platform · Identity & Access.** Email or phone is verified, and the Tenant and its Owner membership are created inside one isolated tenant boundary.

  3. 3

    3. Copilot interview

    **Platform · Copilot.** The Copilot asks about industry, company size, channels (WhatsApp, email, ads, calls) and goals. No data leaves the tenant.

  4. 4

    4. Onboarding Agent proposes a plan

    **AI Workforce · Onboarding Agent.** It proposes Packs, pipelines, roles, automations and Digital Employees to start with, with reasons for each.

  5. 5

    5. Owner approves the plan (R2)

    **Human gate.** The owner reviews and approves, edits or rejects the plan in the Approvals Inbox. Nothing is installed before this decision.

  6. 6

    6. Install Packs, seed config and brand kit

    **Platform · Tenants & Workspaces.** Approved Packs are installed with seed configuration and the brand kit. Event: `pack.installed`.

  7. 7

    7. Connect existing tools (R3 consent)

    **Platform · Integration Hub.** Gmail or Microsoft 365, WhatsApp, Meta and Google, Tally or bank feeds are connected. Each OAuth consent is a human decision at risk tier R3. Event: `connection.established`.

  8. 8

    8. Import data with AI-assisted mapping

    **Platform · Migration Factory.** CSV or connector data is mapped and deduplicated with AI suggestions. Mappings are proposed, never auto-applied. Event: `import.completed`.

  9. 9

    9. Invite the team and create agent identities

    **Platform · Identity & Access.** Team members are invited and given roles. Agent identities are created as a separate principal type, in shadow mode (A1). Events: `user.invited`, `agent.created`.

  10. 10

    10. First value

    **Intelligence · Dashboards.** The owner sees a first dashboard and three recommended next actions, each one a real Action they can approve.

Events, gates and KPIs

ItemDetail
Events`tenant.created`, `pack.installed`, `connection.established`, `import.completed`, `user.invited`, `agent.created`
Human gatesPlan approval (R2); OAuth consent for each connection (R3)
KPIsTime to first value under 30 minutes *(target)*; share of tenants with at least one connection on day 1; day-7 activation

Questions about this flow

Does the Onboarding Agent install anything on its own?

No. It proposes a plan. The owner approves, edits or rejects it in the Approvals Inbox before any Pack is installed.

Can an agency onboard clients this way?

Yes. An agency partner can create a client sub-account and run the same flow under its own white-label workspace. Agency OS is planned for W2.

What happens to agents created during onboarding?

They start in shadow mode (A1). They propose actions and humans act. They move up the autonomy ladder only after measured agreement and a minimum Eval Coverage Score.

Is imported data merged automatically?

No. AI suggests mappings and duplicate merges with a confidence score. A human approves them. Silent merges are not allowed.

Is this available today?

No. One3 is being built in waves. The platform modules behind onboarding are planned for W0–W1, inside the Year-1 boundary.

Help shape onboarding as a design partner

One3 is working with a small group of agencies and SMBs during the first waves. Tell us how you onboard clients today.

Become a design partner