HR Case Intake & Triage
A confidential HR help-desk where employees submit issues, the tool categorizes and prioritizes them, routes to the right HR owner, and tracks every case to resolution with SLA timers - so nothing falls through the cracks.
A private, login-protected HR case queue where employees submit issues, HR triages and routes them, SLA timers run, sensitive cases stay locked to assigned staff, every action is audited, and you can export the full caseload to CSV.
Before you start
- A free Vercel account
- A free Supabase account
- A free Resend account
- Claude Code installed on a Linux machine
The problem this kills
Right now your HR questions arrive everywhere at once: an email here, a Slack DM there, a "got a sec?" in the hallway, a sticky note on someone's desk. There's no single list, no owner, no clock. The quiet-but-urgent stuff (a harassment report, a pay discrepancy, a leave request that's about to blow a legal deadline) gets buried under the routine stuff. You find out something fell through the cracks only when it becomes a much bigger problem.
And HR cases are the kind of data you absolutely cannot leave lying around in a shared inbox. Sensitive matters need to be visible only to the people handling them - not the whole team, not by accident.
This Implementation Plan kills both problems at once: one confidential intake, automatic triage, clear ownership, a ticking SLA clock, and an iron-clad confidentiality wall.
What you'll build
A private web app - only your HR team can log in - with a clean case queue:
- An intake form employees use to submit a question or issue (category, description, urgency, and a "this is sensitive/confidential" flag). Anonymous submission can be switched on if your policy allows it.
- Automatic categorization and prioritization so every case lands with a suggested category, priority, and SLA target the moment it arrives.
- Routing to the right HR owner based on a map you define (benefits questions to one person, employee-relations matters to another, and so on).
- SLA timers that count down per case and flag breaches before they happen, with email alerts.
- A confidentiality wall: sensitive cases are visible only to the assigned HR owner and authorized staff - enforced at the database level, not just hidden in the UI.
- A human approval gate: the owner accepts each case, confirms category and priority, and approves closure. Nothing is auto-resolved.
- A complete audit trail and a one-click CSV export of your whole caseload.
What's inside the Implementation Plan
A step-by-step runbook you paste into Claude Code (an AI coding assistant). It does the building; you answer questions and click approve.
It opens by interviewing you about your actual HR operation - your categories, your owners, your urgency levels, your SLA targets, your confidentiality rules - and tailors the whole tool to that. This is the part that matters: you get a help-desk shaped like your HR team, not a generic ticket system you have to bend yourself around. The plan reads a short spec back to you and waits for your thumbs-up before it builds anything.
Then it walks through the database, the confidentiality wall, the intake form, triage and routing, SLA timers and alerts, the audit log, and the CSV export - each step ending in a prompt you copy and paste.
The governance it includes (this is the point)
- Login so only your HR team can see the queue.
- Row-level security so sensitive cases are locked to assigned and authorized staff - the database itself refuses to show them to anyone else.
- A full audit trail: who opened, accepted, re-categorized, updated, and closed each case, and exactly when.
- A human-in-the-loop gate: the AI drafts the category and priority; a person confirms, works the case, and approves the closure.
- Duplicate guards: every case gets a unique ID, and the tool warns you if the same employee opens a similar case that's still open.
Who it's for
HR teams - one person or a small department - currently fielding questions across email, Slack, and hallway conversations with no system and no record. If you can describe your categories and who owns what, you can build this. No coding background needed.
You've got this - paste the first prompt and let the agent interview you.