Resend InboxesTranslation site

AI Email Infrastructure · Shared Inbox · Developer Tools

Setting up a webhook to receive emails is just the beginning. Once emails arrive, they need to be assigned, categorized, drafted, and the conversation preserved. Resend Inboxes organizes these capabilities into inboxes that can be accessed via the interface, API, and AI tools.

What is it, and who is behind it?

Resend is an email platform for developers. According to the official description, its founders are Zeno Rocha, Bu Kinoshita, and Jonni Lundy. The platform launched its email delivery service in 2023; the legal entity listed in the Terms of Service is Plus Five Five, Inc..Company Profile,Terms of Service.

In an official blog post dated October 22, 2026, Resend introduced Inboxes and its workflows. It sends and receives emails using addresses under your domain, organizes emails into threads, and enables collaboration among team members and agents. It is better suited for teams that need to integrate email into their business workflows, rather than individuals who simply want to switch their everyday email client.Official Release Notes.

What issues does it address?

• Conversation Continuity:By placing email exchanges in the same thread, applications or agents can access the context rather than processing each message in isolation.
• Collaboration Between People and Agents:A shared inbox can be used for assigning sessions, internal notes, and handoffs. It allows people to focus on complex decision-making while letting agents handle the organizational work.
• Programmable Mailbox Object:The API targets objects such as inbox, thread, label, and draft, making it easy to build business features around emails.
• Workflow Entry Point:You can respond to new emails or assignment changes via webhooks, and you can also configure the built-in agent's instructions, tone, and permitted actions within the interface.

Based on the foregoingOfficial Product Pagetogether withRelease Notes. Features such as the table of contents, search, tags, and drafts help organize work, but it is still up to the team to verify whether emails are categorized accurately and whether replies are appropriate.

Which teams is this suitable for?

From a functional and structural perspective, the following three types of scenarios are particularly worth piloting first; these are editorial recommendations, not official customer case studies.

• SaaS Customer Service:Have agents first summarize issues, apply tags, and draft responses; refer complex issues to customer service. The business system can link order statuses to email threads.
• Internal Request Entry Point:Set up a dedicated address for a specific process to receive requests, supplementary materials, and approval results. It can handle correspondence but cannot replace the approval process itself.
• Reminders and Duty Schedules:Import the notifications into the shared portal and clearly designate the person responsible for each session. Before going live, design a mechanism to handle duplicate events to prevent the same notification from triggering multiple actions.

If you only send and receive personal emails occasionally, the effort required to learn the API, configure domain names, and manage proxy permissions may not be worth the trouble. Product teams that already use Resend to send transactional emails and need to handle replies will find it easier to assess the value of integrating it with their existing systems.

Getting Started: Check your email first, then unlock the actions

1. Prepare a domain name.The standard email reception method requires enabling domain reception capabilities and verifying DKIM, SPF, and the inbound MX record. The official API also offers a forwarding mode: after the domain passes DKIM/SPF verification, you obtain a dedicated receiving address and then configure your original email account to forward messages to it. Do not arbitrarily replace the MX record of your production domain for testing purposes.
2. Create a dedicated inbox.Set the email address, internal name, and sender name through the interface or the Create Inbox API. First, use a test email address to verify receipt, reply-to settings, and thread content.
3. Integrate into the workflow.Use the API, CLI, or MCP as needed. The official documentation specifically states: Inboxes are available only on the remote MCP server and are not included in the local resend-mcp package.
4. Start with small permissions.First, allow drafts and tags to be created, then manually review the categorization and wording before deciding whether to forward, assign, or archive the email. Actions such as deleting emails should be evaluated on a case-by-case basis; do not grant all permissions to the agent at once.

For domain name requirements and forwarding methods, seeCreate Inbox Documentation; For coverage details, seeMCP Documentation; For a list of controllable actions for the built-in proxy, seeRelease Notes. The recommendations for production environment security and testing in Steps 1 and 2 are supplementary implementation recommendations provided in this article.

Cost: The number of email accounts and the volume of emails must be calculated together.

Each plan includes 3 Inboxes. Once pay-as-you-go billing is enabled for a paid plan, each additional inbox costs $1 per month. The inbox does not have a separate email quota; every email sent or received counts toward the transactional email quota.Official Pricing and FAQs.

• Free: $0/month, 3,000 emails/month; the page lists a daily limit of 100 emails.
• Pro: $20/month, 50,000 emails/month; any excess is charged at $0.90 per 1,000 emails, provided that pay-as-you-go settings are enabled.
• AI credits, automation usage, and other such items are separate amounts that need to be verified; “$1 per additional email account” should not be interpreted as the total cost for all emails and AI usage.

For example, if you use 5 inboxes on the Pro plan, under the current rules, the plan fee and the fee for additional mailboxes would total $22 per month, not including overage charges, other add-ons, or taxes. This is merely an example calculation based on published prices and does not constitute a billing quote.

How do we compare with actual competitors?

These pricing models differ: Resend focuses primarily on the plan, email address, and email volume; AgentMail also considers storage capacity and rate limits; Front is priced per seat and may charge separately for AI add-ons. You can’t simply compare the price of a single email address to the price of a single seat to determine “which is cheaper.”

Privacy, Retention Periods, and Service Boundaries

According to Resend’s official security page, data is encrypted using static AES-256 and HTTPS/TLS encryption during transmission, and the service holds SOC 2 Type II certification; stored data is located in the United States, and selecting a European delivery region does not mean that the data is stored in Europe. The official documentation also states that the service does not currently comply with HIPAA and cannot sign a BAA. When dealing with healthcare or specific residency requirements, compliance should not be assumed solely based on the fact that “encryption is in place.”Official Safety Notice.

The same security page lists the standard retention period for emails and logs in the Free, Pro, and Scale plans as 30 days. Publicly available information does not explicitly clarify whether there are special retention rules for complete threads, attachments, and drafts in the new Inboxes; businesses requiring long-term retention should confirm with the official provider and design their own retention plans before going live, and should not treat it as a default permanent archive.

When connecting to an external proxy, you must also verify which email content is routed to which model service. Do not automatically apply the “data processing methods used by the standard email sending API” to all AI features. We recommend starting with a draft workflow that employs the principle of least privilege, test email accounts, and manual review; instructions contained in external emails should not be granted direct permission to perform internal company operations.

reach a verdict

What makes Resend Inboxes worth developers’ attention is its ability to transform email addresses, conversations, and collaborative actions into unified work objects. The most reliable way to test it is to choose a narrow use case—such as receiving, categorizing, and drafting emails—and then observe whether manual processing becomes easier. If the goal is to immediately deploy a complete customer service system, you should also evaluate work platforms like Front, rather than focusing solely on whether the API is convenient.

Visit Resend Inboxes - View the API documentation