Resend Inboxes review: a shared inbox your agent can work, with a draft folder between it and your customers

The short version

Resend Inboxes gives you a real email inbox, like [email protected], that your team and an AI agent can work at the same time. Messages are grouped into threads, people can assign and annotate them, and an agent can sort, label and draft replies as mail arrives.

It's a good fit if you build software, already send email through Resend, or want an agent to have its own address for tasks and approvals. It's a weaker fit if what you really need is a mature help desk with reporting, service-level timers and a library of canned answers.

The detail we like most is a limit. Resend's documentation says the built-in agent never sends email on its own. Replies and forwards are saved as drafts for someone on your team to review and send. An agent that drafts and a person who sends is a better first arrangement than any setting called autopilot.

What Resend launched

Resend started as a service for sending email from apps, added receiving in 2025, and announced Inboxes on October 22, 2026. Its pitch is that once email arrives, someone has to read it, sort it, reply and remember where things stand, and that someone is increasingly an agent.

From the announcement and the docs, an inbox includes:

Shared threads. Every message lands in a thread that your app, your team and your agents can all see. Teammates can assign conversations, leave notes and pick up where someone else stopped.

The usual inbox parts, exposed through an API. Folders for inbox, archive, spam, trash and sent. Search with a Gmail-like syntax. Labels, drafts, forwarding and reply-all with CC and BCC. Webhooks fire on events from a new email arriving to a thread being assigned.

Agent access from outside. You can connect agents you already use through MCP, skills, the API or a command-line tool, and ask them to summarize what came in overnight or find last month's invoice.

A built-in agent. Each inbox has one. You write instructions of up to 4,000 characters, pick the actions it may take, and set a tone from four options that run from concise and professional to expanded and casual.

Who it's for

Teams building email into a product. If your app needs to receive replies, route support mail into your own screens or let users email a task in, Inboxes hands you threads and webhooks instead of raw messages. That's a lot of plumbing you don't have to write.

Anyone giving an agent its own address. Resend suggests giving each agent an inbox for tasks, approvals and updates. That's a cleaner setup than letting an agent log into a person's mailbox, because the agent's mail, permissions and history stay separate from the person's.

Small teams with one shared address and no system. A lot of businesses run support out of a mailbox several people can read, with nobody clearly owning each thread. We've written about why a shared inbox without a route is just a pile. Assignment, notes and an agent that labels and routes as mail arrives go straight at that problem.

Cautious adopters. The agent's guardrails are specific. It skips the spam folder. If a thread already has a draft, it leaves the thread alone. It only forwards to full email addresses written in its instructions, so naming a person or a domain isn't enough. It only applies labels that already exist, and it only assigns a thread when the name in the instructions matches exactly one teammate.

Who should wait

Support teams that live on reports. The announcement covers threads, assignment, labels and an agent. It doesn't describe the reporting, response-time targets, satisfaction surveys or saved-reply libraries that full help desk products are built around. If your manager reviews response times every Monday, keep your help desk.

People who want a finished app, not parts. Resend calls Inboxes API-first and talks about building custom views. There is a dashboard UI, but much of the value shows up when a developer wires it into your product or workflows.

Anyone who wants the agent to reply on its own. It won't. For most businesses that's correct. If your plan depended on fully automatic replies, you'd need to build that sending step yourself, and you should think hard before you do.

Teams with a big inbound volume on a small plan. Resend's pricing page says inboxes don't come with a separate email allowance. Every email sent or received through an inbox counts toward your transactional email quota, so a busy support address uses up a small plan faster than you'd guess.

Pricing and alternatives

As published on October 25, 2026, every Resend plan includes three inboxes. On paid plans with pay-as-you-go turned on, each additional inbox costs $1 per month. The Free plan lists 3,000 emails a month with a 100-a-day limit. Pro lists $20 a month for 50,000 emails. Because inbound mail counts toward that quota, estimate both directions.

The common alternatives are a shared mailbox in Google Workspace or Microsoft 365, which is familiar but has no built-in agent rules or API-first threads, and a dedicated help desk product, which offers more reporting and workflow but usually treats AI as an add-on to a human queue. Inboxes sits in between: lighter than a help desk, more programmable than a shared mailbox, and designed with agents in the room from the start.

How we'd set it up

Start with the two actions Resend itself suggests: drafts and labels. Create your labels first, since the agent won't invent new ones.

Write instructions the way you'd brief a new hire. Say what kinds of mail arrive and what to do with each. Name teammates by email address. Write out full forwarding addresses. Say plainly what should be escalated, like legal threats, refund disputes or anything that mentions a deadline.

For the first few weeks, have one person read every draft before sending and keep a short list of what they changed. That list tells you whether to widen the agent's actions or tighten its instructions.

Add archiving and spam marking once you trust the labels. Be slowest with trash. Resend notes you can undo the agent's moves by organizing the thread yourself, but you still have to notice them.

If you want Inboxes, or an agent like it, wired into your product with the right boundaries and an audit trail, that's what our AI applications and agents team builds. Talk to us.

Related work: Spin Market.