A human-staffed shared inbox — support email that becomes an assignable, trackable conversation — is a genuinely different, simpler build than an AI chatbot, closer to a well-organized email client than a specialist support platform.
Build it
Effort: a weekendRunning cost: $0/mo to start
Why CanICodeThis says Build it
Incoming email via a forwarding address becomes a conversation, assignable to a team member — a small state machine on top of a message table
Conversation status (open, pending, closed) is a simple field
For a small team's support inbox, this is genuinely a weekend build
The parts that'll cause problems
A public knowledge base with search, alongside the inbox, is a real, separate content feature
Automated workflows (auto-tag and route based on keywords) need a small rules engine
Reliably ingesting multiple channels (email, chat, social DMs) into one unified queue is real, separate per-channel integration work
How I'd build this
frontend
Next.js
database
Supabase
email
Resend inbound routing or a forwarding address
hosting
Vercel
MVP scope
A forwarding address that turns incoming email into a conversation
Assign conversations to a team member
Status field (open, pending, closed)
Internal notes on a thread
Postpone to v2
A public knowledge base
Auto-tagging and routing rules
Multi-channel intake (chat, social)
What it actually costs to build
AI agent — with a subscription (Claude Pro/Max, Cursor, etc.)
$0 marginal
AI agent — pay-per-use API, no subscription
$43–$86 one-time
Hosting, once it's running
$0/mo (free tier)
Domain name, if you want your own
~$12/yr
Existing tools solving a similar problem typically run $19–$20/mo — see how they compare below.
The build prompt
Build me a shared support inbox, sharing this register's Front-style build spec:
1. A forwarding address that turns incoming email into an assignable conversation — email parsing plus a conversation table.
2. Assign conversations to a team member.
3. A status field (open, pending, closed).
4. Internal notes on a thread, visible to your team but not the sender.
That's a real, complete shared inbox for a small team. Out of scope: a public knowledge base with search alongside the inbox, a real, separate content feature, and automated workflows (auto-tag and route based on keywords), which need a small rules engine most small teams don't need to start with.
