Internal Help Desk Intake & Routing: One Inbox, Auto-Sorted to the Right Team

The problem this kills

Internal requests arrive everywhere and from everyone: an email to "IT," a Slack DM to the office manager, a sticky note on a desk, a "quick favor" caught in the hallway. Someone has to read each one, figure out whether it's IT, facilities, or HR-ops, decide how urgent it is, and find the right person to hand it to. Things fall through the cracks. The same broken printer gets reported four times. Nobody can say how long tickets actually take, and the "urgent" ones are whoever shouted loudest.

You don't need to buy a heavyweight ITSM platform or learn to code to fix this. You need one front door, smart sorting, and a human who confirms where each ticket goes before it lands on an agent's plate.

What you'll build

A simple internal web tool. Staff submit a request through one clean form. The tool reads the wording, suggests a category (e.g. "Laptop won't boot" → IT / Hardware), suggests the owning team and an agent, and sets a priority and SLA clock from your rules. It checks whether this looks like a duplicate of an open ticket and offers to merge. Your triage lead sees each new ticket with the AI's suggestion, adjusts anything that's off, and clicks Confirm & assign — only then is the agent notified. From there every ticket moves through a clear status flow to Resolved, with a live queue dashboard showing who's working what, what's breaching SLA, and a CSV export in the exact columns your existing ITSM or spreadsheet expects.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — which request types you actually handle, how your teams and agents are named, your real priority and SLA rules, your typical and peak ticket volumes, and the messy edge cases (the VIP exec, the after-hours outage, the request that's really two requests) — and then it tailors the categories, routing rules, and every later step to your answers. This is not a generic template: the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the intake form, the keyword auto-categorizer, the dedupe-and-merge logic, the triage review-and-confirm screen, the agent notifications, the SLA clocks, and the queue dashboard plus CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build the whole thing today even with no API into your current help-desk system.

The governance it includes (this is the point)

This is a real operations tool, so it ships with the controls a shared-services team needs: login so only your staff can use it, row-level security so each organization only ever sees its own tickets, a complete audit trail of who submitted, triaged, reassigned, and resolved every ticket and when, a hard human-in-the-loop gate so the AI only suggests a category, team, and priority while a triage lead commits the routing before any agent is notified, and duplicate guards keyed on requester plus subject within a time window so the same issue can't spawn five tickets.

Who it's for

IT and facilities help-desk leads, shared-services and ops teams, and office managers who are the unofficial "where do I send this?" router for the whole company. If you can describe how you decide who handles what, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your first auto-routed ticket land in the triage queue the same afternoon.