Multi-step back-office work, done under governance.
Agents plan the steps, gather context through approved tools, draft records, and wait for a human before anything sensitive — with a full audit trail. Same adapter as the storefront, elevated only because the user’s permissions allow it.
Back-office merchant or operations user — the same adapter as the customer assistant, with user.role = merchant.
On an order screen, the merchant asks: “Refund this order and adjust stock.”
Plan → governed tools → cards.
Illustrative tool ids and risk levels — a host defines its own. The primitives underneath (the governance gate that runs permission, policy and audit, context minimization, the 12 card types) are built and tested, and the data-handling and security controls around them are documented.
A plan card breaks the request into steps; read-only lookups (order status, related records) run automatically to build context.
issue_refund and adjust_stock are controlled writes — each pauses for its own approval card, and a comparison card can weigh partial versus full refund.
Permissions expand only because the merchant’s references allow it — the exact same code path as the customer assistant, with elevated but still-approved authority.
Every write is gated and logged; results render as detail and result cards with no custom UI.
Customer value.
Faster resolution of multi-step back-office jobs without leaving the app.
Every write is approved and audited; nothing is committed silently.
Role is just user.role plus permission references — flip from customer to merchant and refund tools appear, no new adapter.
Target: [CUSTOMER RESULT REQUIRES VALIDATION].
Flip user.role from customer to merchant and watch issue_refund appear as an approval-gated action — no new adapter, same governed path.
Employee helpdesk agent
An assistant inside your internal portal that answers policy and account questions from the employee’s own scope, and routes privileged actions like an access reset through approval — opening a ticket only when needed.
Use case · Sales & revenue opsOperations copilot
A copilot that assembles context across records — even across multiple host apps — and stages sensitive actions for a human to approve, inside the CRM or internal tools your team already uses.
Flagship · Multi-agent reportingGoverned reporting & analytics team
A multi-agent team — one coordinator plus permission-scoped specialists — that turns plain-language questions into governed tables and diagrams, with provenance on every answer and no dashboards to build.
See “Merchant & back-office agent” running under governance.
Book a demo and we’ll walk your team through this workflow, the governance gate, and the interactive cards — using an example close to your stack.