Shared Inbox Assignment Board
Build a lightweight board over your shared support mailbox so every email thread gets one clear owner, a status, and an audit trail - no more two agents replying to the same customer or threads sitting ownerless.
A team board where each email thread can be claimed or assigned to exactly one agent, moved through unassigned -> assigned -> waiting -> done, with every claim and close logged - plus a daily email of unowned and aging threads.
Before you start
- A free Supabase account
- A free Resend account (for the daily summary email)
- A free Vercel account (to put it online)
- An export or copy-paste of your support@ inbox threads (sender, subject, received-at, snippet)
- Your list of support agents (names + emails)
The problem this kills
You run support out of a shared mailbox - support@yourcompany.com - and a handful of people all log in to the same inbox. It works until it doesn't. Two agents open the same angry email and both reply, so the customer gets two different answers. A thread nobody noticed sits for three days with no owner. Someone marks a message "read" and now everyone assumes it's handled - it isn't. You have no idea who is working what, and nothing tells you when something is quietly aging out.
Helpdesk software fixes this, but it's expensive, heavy, and you'd have to migrate your whole team onto it. You don't need a helpdesk. You need a simple board that sits on top of the inbox you already have and answers one question for everyone: who owns this thread right now?
What you'll build
A small, private web app for your support team - a board that shows every inbox thread as a card. Each card can be claimed by an agent (or assigned by a lead) and moves through clear lanes: Unassigned -> Assigned -> Waiting on customer -> Done. The rule the whole thing protects: one owner per thread at a time - so nobody can grab a thread someone else already has. Every claim, reassignment, and "resolve" is written to an audit log (who, what, when). Each morning, the team gets an email listing anything still unowned or sitting too long.
What's inside the Implementation Plan
- It starts by interviewing you about your business. Before it builds anything, the plan has the AI agent ask you about how your team works today - your inbox export format, your agent roster, the statuses you actually use, how a thread gets "claimed," what counts as "aging," and your messy exceptions (out-of-office, escalations, spam). It reads a short tailored spec back to you, you give a thumbs-up, and only then does it build. You get a board shaped around your team, not a generic template.
- A complete, copy-paste runbook: every step ends with a ready-to-paste prompt for Claude Code.
- A data model built around your inbox: threads keyed by message/thread ID so the same email can't be loaded twice.
- The collision-prevention logic that's the whole point: a thread locks to one owner, and a second person trying to claim it is told it's taken.
- A daily "unowned and aging" digest emailed via Resend.
- A no-integration fallback so you can build and use this today.
The governance it includes (this is the point)
- Login so only your team can open the board.
- Row-level security so your data is fenced off to your team only - nobody outside sees a thing.
- A full audit trail: every claim, reassignment, status change, and resolve is logged with the agent's name and a timestamp.
- A human-in-the-loop action gate: ownership and "resolve" never happen automatically - they require the acting agent's explicit click, and that action is what gets logged.
- Duplicate guards: the email thread/message ID is the dedupe key, so re-importing your inbox never creates phantom duplicate cards.
Who it's for
Small support teams running support@ out of a shared Gmail, Outlook, or similar mailbox with no helpdesk - where ownership is informal, collisions happen, and things slip. If "wait, did anyone answer this?" is a daily question, this is for you. No coding background needed.
You've got this - paste the first prompt and let the agent interview you.