Onboarding a customer
The first hour of a new customer's agent: acceptance, its own Tenant and agent, its accounts, its approvals, then a first task tried before it runs.
A new Customer has a working agent within the hour of accepting the Offer. Each step below is a Verb, so a buyer's agent can run the whole sequence without a person.
Six steps
| Step | Verb | Who acts | What exists after |
|---|---|---|---|
| Accept | Offer.accept | The Customer, or its agent | A Customer and its Subscription |
| Give it a home | Tenant.provision | The Startup | A Tenant holding the Customer's Entitlements |
| Mint its agent | Agent.mint | The Startup | The Customer's own Agent, with its Mailbox |
| Connect its accounts | Integration.connect | The Customer's admin | Approved grants to its email, calendar or property system |
| Set what asks first | Mandate.authorize | The Customer | A Mandate with its Limit and approval rules |
| Try the first task | Any Verb in the try Mode | The agent | A preview of each Action, with nothing sent |
The Onboarding Specialist seat runs onboarding. It waits on the two steps only the Customer can take: connecting accounts and setting its Mandate.
The first task
The agent's first task runs in try first. Riverside Property's agent lists the leases that end in 60 days and drafts their notices, and the Portal shows each draft beside the Evaluator's verdict.
The property manager reads the drafts and says go. From then on the agent sends on its schedule, and only the classes the Mandate names wait for a yes.
What the customer sees
The Portal opens on three things: the agent's address, the accounts it may use, and what it asks before acting. Each one changes from the same screen, and each change is on the record as an Action.
When a step stalls
A step that waits on the Customer holds as pending with reason awaitingInput, and the Onboarding Specialist follows up. An account the Customer never connects leaves the agent working on what it can reach, and the try answer names the missing piece.