AI Agent for B2B Customer Onboarding (2026)

Onboarding a B2B account is controls, not a welcome chatbot. Legal name, documents, sellable catalog, assigned price list, credit application, contract, then first order, then education. The agent can collect and check. It cannot approve money or paper.

On 17 June 2026, AgentCore Harness reached GA (What’s New). Use it for a guided checklist with read tools and submitCreditApplication. After 30 July 2026, Classic is not the greenfield.

This is a gate map. It is not a “time-to-first-order” customer study. We do not invent onboarding-cycle KPIs.

First-party signals we reuse (not onboarding SLAs) — Gateway server-side tools cut median tool RTT ~180 ms → ~95 ms on a B2B CRM assistant (12 tools, ~8k turns/day) — Gateway post. Doc and CRM hops will dominate. Platform ~$791/mo at 50K sessions is a silhouette (decision guide). Use the AgentCore pricing calculator.

Reproduce this — Walk b2b-onboarding-control-gates.md. firstOrderEligible stays false until credit and contract are human-approved. Folder: ecommerce-ai-agents-series/.

Opinionated take: no setCreditLimit, no countersignMsa, no placeOrder on pending. Trade-off: the agent will feel incomplete in a demo. Finance will still have a job on Monday.

Once approved, sales tools apply — sales agent. Quotes still respect caps — quote agent. Ticket-style “how do I log in” can reuse support lookup reads, not credit writes. Host story: FactualMinds on AWS.

Seven stages, two hard stops

flowchart TD
  setup[Account setup draft]
  docs[Documentation]
  prod[Product selection]
  price[Price list assigned]
  credit[Credit workflow]
  contract[Contract sign-off]
  order[First order]
  edu[Education]
  setup --> docs --> prod --> price --> credit --> contract --> order --> edu
  credit --> humans[Finance HITL]
  contract --> legal[Legal / sales HITL]

Financial and contractual approvals stay human. Credit limit / contract sign-off is not week-one auto-execute.

Public retail price during onboarding is a lie. If the list is unassigned, say so. Same fail-closed rule as sales.

Tools you omit on purpose

• setCreditLimit
• activateContract / countersignMsa
• capturePayment
• placeOrder while accountStatus != approved
• Browser “fill the ERP screen” on every turn
• Cross-account documents

Cedar default-deny. LOG_ONLY then ENFORCE. Shopper JWT DENY on onboarding account tools. Bedrock Guardrails are complementary, not the credit committee.

Pending vs approved is a commerce flag, not a prompt. Until accountStatus = approved, sales nets and issued quotes stay off. After approval, the sales agent and quote gates apply — still permissioned, still HITL over cap.

Education is versioned help (pack size, how to read a price list, how to raise an RFQ). It is not a WISMO bot. “Where is my first order” after approval is support lookup with read tools. Do not attach setCreditLimit to the support specialist “just in case.”

Public retail during onboarding trains the account on the wrong number. If the price list is unassigned, the agent says pending assignment. It does not “use the website until then.”

Context: blocked output; demo id.

{
  "accountId": "ACC-PENDING-441",
  "stage": "credit_review",
  "credit": { "status": "in_review", "limitUsd": null, "tool": "getCreditApplication" },
  "contract": { "status": "not_signed", "tool": "getContractStatus" },
  "firstOrderEligible": false,
  "blocked_reason": "credit_not_approved,contract_not_signed"
}

limitUsd: null on purpose. The agent does not guess a limit to “keep momentum.”

Hybrid: workflow owns activation — agent vs workflow. No native Shopify AgentCore connector; you own the CRM/ERP OpenAPI.

What broke

What broke — An onboarding harness with setCreditLimit “for demo completeness.” A golden task asked to finish setup. The model wrote $50,000 because the prompt said typical starter accounts. Detection: credit system audit vs Gateway trace; eval “limit must stay null until committee” failed. Fix: delete the tool; blocked_reason only; HITL credit + contract; first PO only after approved. Lesson: completeness in a demo is a production write.

The CRM canary (~180 → ~95 ms) is still the platform signal. Credit-bureau and e-sign vendors will dwarf it.

Week one is a blocked_reason machine. The buyer sees missing docs and “credit in review.” They do not see a guessed limit. Associates see the same gates plus a finance queue link. If your CRM already has a deterministic onboarding workflow that closes every box, do not wrap it in an agent — agent vs workflow. Use the agent for messy document questions and incomplete packets, not for “if W9 received then next.”

Tax IDs and credit packets are PII. Tools return status and document type, not the PDF bytes, unless an associate-only skill with a tighter policy exists. Do not dump applications into Memory. Memory is a notebook, not a filing cabinet.

First order after approved still has no payment tool. The buyer confirms in the commerce system you already run. The agent may assemble lines against the assigned list. That is the same hybrid as quotes: draft here, money there.

What to Do This Week

1. Copy b2b-onboarding-control-gates.md. Name who signs credit and who signs paper.
2. Draft pending-account reads + submitCreditApplication. No limit write. No contract countersign.
3. Prove shopper DENY. Prove placeOrder DENY on pending.
4. Goldens: missing resale cert, credit in review, “just give us 50k,” public price ask, first PO too early.
5. Education articles in a Knowledge Base; do not scrape a help HTML blob as policy.
6. Harness. Not Classic after 30 July 2026. Browser off.
7. Contact FactualMinds · Generative AI on AWS · Amazon Bedrock.

What This Post Doesn’t Cover

• Post-approval sales and net price — sales agent
• RFQ issue caps — quote agent
• WISMO / ticket lookup — support agent
• KYC vendor selection, OFAC screening playbooks, or a BAA
• Payment capture / stored cards
• Measured days-to-first-PO from a named client — we are not inventing them

FAQ

When should you NOT auto-complete B2B onboarding with an agent?

When credit, contract, docs, or price list are incomplete. Limits and sign-off stay human. Skip Classic after 30 July 2026.

What could go wrong if setCreditLimit is an agent tool?

The model will write a starter limit from chat. Omit the tool.

What could go wrong if the agent quotes public retail during onboarding?

The new account learns the wrong price. Fail closed.

Can the agent place the first order to “activate” the account?

Not while pending. Draft after approved; buyer confirms. No payment tools.

Is this a support bot with extra forms?

No. Different writes. Share Gateway patterns only.

Is Bedrock the onboarding system of record?

No. Bedrock is the model. ERP/credit/CPQ are the record.

Need onboarding control gates on AgentCore without auto-credit? Contact us or AWS for retail / eCommerce.