The AgentivUse cases

A first line IT agent in Teams that walks staff through the fix from the IT runbooks and opens a routed ticket when it cannot

Function: ITEffort: About a weekPublished: 2026-10-17
ClaudeMicrosoft TeamsSharePointMicrosoft 365JiraServiceNow

The problem

A one or two person IT team in an SMB spends most of the day on the same requests: VPN will not connect, printer offline, forgot the Wi-Fi password, need access to a shared folder. The runbooks exist but staff message the IT person directly, so real incidents wait behind password questions and nothing is logged.

How the agent works

Staff post the problem in an IT help channel in Microsoft Teams, where the agent is the first responder. It searches the IT runbooks and SOPs in SharePoint, asks one or two clarifying questions (which device, which network, what the error says) and replies with the matching steps, citing the runbook it used. If the steps solve it, the agent closes the thread and logs the case; if not, or if the request needs a change it is not allowed to make, such as granting access or resetting an account, it opens a ticket in the helpdesk tool (Jira or ServiceNow) with the device, the steps already tried and a priority, and routes it to the right person. The IT lead reviews new tickets and anything flagged as a possible security issue, and the agent never touches accounts, permissions or devices itself. A weekly summary of the most frequent questions tells IT which runbook to improve or which fix to automate next.

Worked example

Smartsheet reports that roughly 30% of its IT helpdesk tickets are now handled automatically by Claude powered agents, which shrinks the support team's queue. The same triage pattern is sold at enterprise scale in Google's Gemini Enterprise agent gallery, where the HCLTech ITOps agent triages incidents inside ServiceNow, surfaces the relevant SOPs and drives guided remediation. Anthropic's Microsoft 365 connector gives an SMB the building blocks: Claude can read Teams channels and SharePoint documents with the user's own permissions, and sending Teams messages is a write action an admin must switch on tool by tool.

PDPA note. Tickets contain employee names, device identifiers and sometimes screenshots of personal data. Keep the agent read only on SharePoint and Teams, let only humans change accounts or permissions, and purge screenshots and logs on a set schedule.

Get a new agent use case every week

Join the Agent OS Club: every week a new use case with the exact prompts, skill files and setup steps, so you can build your own team of AI agents to run the work for you. It is how The Agentiv runs, on a team of 40 agents and growing. USD 15 a month, cancel any time.

Join the Agent OS Club

Building this for an organization? Learn more at theagentiv.com

Sources

Related use cases

An agent in Outlook that sorts the unread inbox into what needs you, drafts the replies it can handle and writes a one page brief before each meeting

OperationsEffort: An afternoonOutlook · Claude for Outlook · Microsoft 365

A manager on Microsoft 365 starts the day with eighty unread emails, half of them calendar responses and newsletters, and the three that need a decision are buried. Meeting prep means scrolling back through threads with each attendee, so people walk in without knowing what was last agreed.

An agent that reconciles the month against Stripe, card spend and payroll, flags every mismatch and writes the close packet for your accountant

FinanceEffort: About a weekClaude Cowork · Xero · QuickBooks

Month end in a small company means the owner or one admin exports the bank, the payment processor and the payroll run into separate sheets and hunts for why the totals do not match. The accountant gets the files a week late with questions still open, and the P&L arrives too late to change anything.

An HR agent that answers routine policy questions from the employee handbook in SharePoint, so leave, expense and benefit queries never reach the HR inbox

HREffort: About a weekClaude · Microsoft 365 · SharePoint

In a company of fifty to three hundred people the HR team answers the same questions every week: how many days of annual leave are left this year, can I claim a taxi after 9pm, what is the probation rule. The answers are all in the handbook and the HR policy folder, but nobody reads them, so HR spends hours a week acting as a search engine.