Where Do Resend Replies Go? Resend Inbound and Your Options

Replies to an email you send with Resend go to the address in its From field, or to its Reply-To if you set one (replyTo in the Node SDK, reply_to in the API). Resend only gets them if that domain's MX record points at Resend (that's Resend inbound), or you forward them to a Resend receiving address. If there's no inbox behind the address, the reply bounces. Resend's send. subdomain is the Return-Path (docs), which only collects bounces.

A reply can land in one of four places: a mailbox already on that domain, Resend Inbound (a webhook plus a Receiving tab), Resend Inboxes (private beta), or a separate inbox on the same domain or a subdomain. I built Mailyond for the last one. You keep Resend for sending, point the reply domain's MX at Mailyond, and answer replies for all your domains in one inbox, at a flat $10 or $40 a month.

Where replies to Resend email actually go

Resend recommends sending from a subdomain such as updates.example.com (Domains introduction). I'd keep that and add a replyTo where someone reads mail:

await resend.emails.send({
  from: 'App <hello@updates.example.com>',
  replyTo: 'hello@example.com',
  // to, subject, html
});

Without replyTo, customers reply to hello@updates.example.com, a subdomain that often has no inbox, and that's the usual reason replies disappear. So check the MX on the reply name first.

How Resend inbound works today

Resend receives on every plan (pricing, checked 19 October 2026). Mail arrives at your <id>.resend.app address or your verified domain once you add its MX (Receiving Emails). It shows up in the Receiving tab, and an email.received webhook tells your app.

Replying is up to your code: In-Reply-To set to the received message_id, a Re: subject, and References for later replies (Reply to Receiving Emails).

For code that acts on replies (parse, route, hand to an agent), I think this is the right tool.

Can Resend receive email for a person to answer?

Yes. Inbound hands the message to your code. For a person to answer it in the thread, there's Resend Inboxes, a client built on Resend, or a separate inbox (compared at the end). Forwarding replies into Gmail and answering with Send-as usually fails DMARC, as I explain in how to reply from a custom domain.

How to keep Resend for sending and get replies on the same domain

1. Pick the reply address: the From domain (updates.example.com) or a replyTo like hello@example.com or info@example.com.
2. Check that name's MX. If it already has a mailbox (Google Workspace on the apex, say), use a subdomain instead. If Resend Receiving is on for that name, turn off "Enable Receiving" and remove Resend's MX, since with two MX hosts mail usually only goes to the lowest number (Custom Receiving Domains).
3. Connect the name in Mailyond. It's one 5-minute DNS setup with 3 records: DKIM TXT at <selector>pm._domainkey.<name>, Return-Path CNAME pm-bounces.<name> to pm.mtasv.net, and MX <name> to inbound.postmarkapp.com at priority 10. These don't overlap with Resend's DKIM or send. records, so both senders stay verified.
4. Leave your Resend code alone. Only from or replyTo has to be on the connected name.
5. Test it. Run the domain through the DMARC checker, send from your app to a personal Gmail, reply, and answer it in Mailyond. To confirm the MX for your reply domain points at inbound.postmarkapp.com, paste it into the MX record checker.
6. Optional: Mailyond's send endpoint is Resend-compatible, so new Resend('myond_...', { baseUrl: 'https://mailyond.com/api/external' }) keeps resend.emails.send() working.

A reply to an email Resend sent starts a new conversation in Mailyond. Mailyond threads by matching In-Reply-To and References against its own sends, and the original is in Resend. Once you answer from Mailyond, later replies thread normally.

Inbound mail counts toward the allowance on both: Mailyond counts everything sent and received (3,000 a month on Basic, 15,000 on Agency), and Resend counts each received email toward its transactional quota.

Where Mailyond fits

If you send with Resend from a few products and replies are scattered or bouncing, Mailyond puts them in one inbox, tagged by domain. You answer as the address they wrote to, or an agent does over MCP. What each sender costs across domains is in transactional email for multiple domains.

Basic is $10 a month for up to 5 domains and one user. Agency is $40 for up to 30 domains and up to 10 members. With one domain and a couple of addresses, Resend Inboxes will probably cost less once you get access.

Try it on one domain: 7 days free on Basic.

Resend Inboxes, inboxes.net, ReTicketDesk and Mailyond

All checked 19 October 2026. Resend's Create Inbox docs say "Inboxes are currently in private beta and only available to a limited number of users".

• Pick Resend Inboxes if you're on Resend, need a few addresses and have beta access.
• Pick inboxes.net if you want open source, self-hosting or the lowest price.
• Pick ReTicketDesk if your support team wants tickets and assignment on top of Resend.
• Pick Mailyond if replies come in across several domains and you want them in one inbox at a flat price, live today, with any sender.

FAQ

Where do replies to Resend emails go?

To the From address, or the Reply-To if you set reply_to. Resend only receives them if that name's MX points at Resend (Resend Inbound), or you forward them to a Resend receiving address.

Can Resend receive emails?

Yes. Resend Inbound is on every plan, with a Receiving tab and an email.received webhook. Each received email counts toward the transactional quota.

How do I set reply_to in Resend?

Pass reply_to (replyTo in the Node SDK) to emails.send, as a string or an array (Send Email API).

Is Resend Inboxes available?

As of 19 October 2026 it's in private beta, with early access on request through Resend Labs.

Can I keep Resend and receive replies somewhere else on the same domain?

Yes, if that name's MX points at the other inbox and Resend Receiving is off for it. Resend's sending records don't clash with that MX.