Enterprise Use-Cases
How to read these pages
Every use-case page follows the same shape:
- The problem. The manual process today.
- The agent. Goal and instructions in plain English.
- What it needs. Knowledge, tools, memory, guardrails.
- How it runs. Who triggers it and what comes out.
- What to watch. The governance and metrics that matter.
The common building blocks
| Block | Typical enterprise use |
|---|---|
| Knowledge base | SOPs, policies, contracts, product manuals, regulatory texts |
| Skills | House style, escalation rules, report formats |
| Tools | Gmail, Slack, Notion, Google Workspace, Salesforce, SAP SuccessFactors |
| Memory | Per-customer or per-case context across conversations |
| Guardrails | PII redaction, prohibited-topic blocking, output review |
| RBAC + sharing | Separating who builds, who runs and who audits |
| Traces + audit log | Evidence for internal review and external regulators |