Operations & Management
Use case 1: Support triage
| Setting | Value |
|---|
| Goal | Read an incoming support email, classify it, rate urgency, and draft a first reply. |
| Knowledge base | Product documentation, known issues, refund and SLA policy |
| Skills | Brand voice, escalation policy |
| Tools | Gmail read only to fetch, Slack to notify on High urgency |
| Output | JSON: category, urgency, draftReply, needsHuman |
| Guardrail | Both directions |
Use case 2: Internal helpdesk
| Setting | Value |
|---|
| Goal | Answer employee questions about IT, HR and facilities policy. |
| Knowledge base | Employee handbook, IT policy, travel and expense policy, benefits guide |
| Tools | Slack to answer in channel, SAP SuccessFactors read only for HR lookups |
| Tool mode | Sign in individually, so each employee only ever reaches their own record |
Use case 3: Meeting notes to actions
| Setting | Value |
|---|
| Goal | Turn raw meeting notes into a decision log and a list of owned actions with dates. |
| Output | JSON: decisions[], actions[] { what, owner, due }, openQuestions[] |
| Tools | Notion to write the page, Google Calendar for follow ups |
| Instructions | Only record an action if an owner was named. Otherwise put it in open questions. |
Use case 4: Vendor and procurement intake
| Setting | Value |
|---|
| Goal | Take a purchase request, check it against procurement policy, and produce a routing decision. |
| Knowledge base | Procurement policy, approved vendor list, delegation of authority matrix |
| Output | JSON: route, approver, policyChecks[], blockers[] |
| Tools | Slack, Google Sheets |
Use case 5: Weekly operations digest
| Setting | Value |
|---|
| Goal | Read this week's operational data and write a one page digest for the leadership team. |
| Tools | Google Sheets to read, Google Docs or Notion to write, Slack to post |
| Memory | On, so it can say what changed since last week |
| Skills | Management reporting style |
Governance for operations
| Concern | Setup |
|---|
| Agent sprawl | Grant agent: create through a Builder role, not to everyone. |
| Consistency across teams | Shared skills for tone, escalation and formatting. |
| Accidental sends | Tick read only actions unless writing is genuinely required. |
| Onboarding and offboarding | Share with groups, so joining or leaving a team moves all access at once. |
| Cost visibility | Give ops leads trace: read so they see spend without reading conversations. |
