Internal IT and office request triage
An agent sorts staff IT and office requests from Slack and email into a simple queue, adds the details a helper needs, and suggests fixes from past answers before routing them to the right person.
The use case
In small companies, IT and office requests arrive everywhere: a Slack message about a printer, an email about a new laptop, a hallway mention of a broken badge reader. The person who handles them, often an office manager or outside IT provider, loses track and staff repeat themselves. The agent watches a request channel and inbox, creates a ticket for each request, sorts it by type such as access, hardware, software, or facilities, and asks the requester for missing details like device or error message. It searches past resolved tickets and internal guides for a likely fix and adds it to the ticket. It routes the ticket to the right person or vendor. The helper decides on the fix and completes the work. Requests for new access or purchases require a manager's approval.
Example workflow
- Staff post requests in a dedicated Slack channel or send them to an IT email address.
- The agent creates a ticket in Jira Service Management, Freshservice, or Airtable and sorts it by type.
- It asks the requester for missing details, such as device, location, or error message.
- It searches past tickets and internal guides in Notion and adds a likely fix as an internal note.
- The ticket is routed to the office manager, IT provider, or vendor, who completes the work.
- Requests for new access or purchases are held until a manager approves them in the ticket.
Tools
- Slack
- Jira Service Management
- Freshservice
- Airtable
- Notion
- Claude
Risks and guardrails
- A suggested fix is wrong or unsafe — guardrail: suggestions are internal notes for the helper, not instructions sent to staff.
- Access is granted without approval — guardrail: access and purchase requests wait for a manager's recorded approval.
- Staff share passwords in requests — guardrail: the agent warns the requester, redacts the password from the ticket, and suggests a reset.
- Urgent problems, such as a possible security issue, sit in the normal queue — guardrail: keywords linked to security incidents alert the IT lead immediately.
Related recipe
Support Ticket and Review Triage with Policy-Cited Draft Replies: An agent tags every helpdesk ticket and public review by intent, urgency, and sentiment, routes it, and drafts a reply that cites your help center. People approve refunds and all public replies.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- Freshservice (official page): support.freshservice.com/support/solutions/articles/50000012678-model-context-protocol-mcp-integration-in-freshservice-eap (checked 2026-11-19)
- Airtable MCP server (official page): support.airtable.com/articles/9897799762-using-the-airtable-mcp-server (checked 2026-11-09)
- Notion MCP server (official page): developers.notion.com/guides/mcp/overview (checked 2026-11-09)
- Claude (official page): claude.ai (checked 2026-11-09)