Sales use cases
Sales teams typically use Salesforce or HubSpot. The highest-value use cases are lead routing, follow-up, CRM hygiene, pipeline hygiene, and meeting summaries.
| Use case | Stack | Inputs | Outputs |
|---|---|---|---|
| Lead routing | Salesforce | New lead records | Lead assigned to rep, notification sent |
| Follow-up | Salesforce | Stale opportunities | Follow-up task created, reminder sent |
| CRM hygiene | Salesforce | Incomplete or duplicate records | Records updated or merged |
| Pipeline hygiene | Salesforce | Stale opportunities | Opportunities closed or updated |
| Meeting summary | Salesforce + Slack | Meeting notes or transcript | Summary logged in Salesforce |
Support use cases
Support teams typically use Zendesk or Intercom. The highest-value use cases are ticket triage, escalation, reply drafts, SLA breach prevention, and help center updates.
| Use case | Stack | Inputs | Outputs |
|---|---|---|---|
| Ticket triage | Zendesk | New tickets | Ticket routed to right team |
| Escalation | Zendesk | High-priority keywords | Ticket flagged and escalated |
| Reply draft | Zendesk | Ticket content | Draft response suggested |
| SLA breach prevention | Zendesk | Ticket age and SLA deadline | Alert sent before deadline |
| Help center updates | Zendesk | Ticket trends | Content update suggested |
Finance use cases
Finance teams typically use QuickBooks or Xero. The highest-value use cases are invoice follow-up, reconciliation, AP coding, expense categorization, and month-end close.
| Use case | Stack | Inputs | Outputs |
|---|---|---|---|
| Invoice follow-up | QuickBooks | Unpaid invoices | Reminder email sent |
| Reconciliation | QuickBooks | Transactions and invoices | Transactions matched |
| AP coding | QuickBooks | Expense descriptions | Category suggested |
| Expense categorization | QuickBooks | Transactions | Category applied |
| Month-end close | QuickBooks | Outstanding items | Close checklist prepared |
Operations use cases
Operations teams typically use Slack, Notion, and Jira. The highest-value use cases are meeting follow-up, standup summaries, approvals, internal helpdesk, and issue intake.
| Use case | Stack | Inputs | Outputs |
|---|---|---|---|
| Meeting follow-up | Slack | Meeting notes | Summary and action items posted |
| Standup summaries | Slack | Standup messages | Summary compiled and posted |
| Approvals | Slack | Approval requests | Request routed to approver |
| Internal helpdesk | Slack | Questions in channel | Answer drafted or routed |
| Issue intake | Jira | Issue descriptions | Issue created and routed |
Frequently asked questions
Which department should we start with?
Start with the department that is most motivated to adopt, review approvals, and report what is working. If there is no clear first mover, finance or operations are often a good place to begin with a narrow, low-risk agent.
Can we deploy use cases across multiple departments in parallel?
Start with one department and one narrow agent. Prove the rollout model, then expand. Parallel launches create approval bottlenecks and unclear ownership when there is no dedicated AI team.
How do we know if a use case is ready for deployment?
A use case is ready when the job is clear, the input is clear, the expected result is clear, and the team knows what should be reviewed before the agent acts. If any of that is fuzzy, narrow it down first.
What if a department wants a use case we have not seen before?
Review the request, define the job clearly, decide what needs approval, and launch it narrowly first. The goal is not to predict every use case in advance. It is to make safe rollout easy when a real use case appears.