> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mailchannels.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Inbound email and replies

> Understand how to handle replies and inbound email when sending outbound messages with MailChannels Email API.

MailChannels Email API is focused on outbound email delivery. It sends messages, reports delivery events through webhooks, and helps protect your sending domains. It does not provide an inbound message content API for receiving, parsing, or storing replies.

## Supported reply patterns

Use one of these patterns when recipients need to reply:

| Pattern                         | Use it when                                                                             |
| ------------------------------- | --------------------------------------------------------------------------------------- |
| Real mailbox                    | A person or team should read and answer replies in an inbox.                            |
| Shared support address          | Replies should create or update support tickets through your help desk.                 |
| Dedicated inbound provider      | Your application needs to parse inbound message content, attachments, or reply threads. |
| No-reply sender plus `reply_to` | The visible sender should be product-owned, but replies should route elsewhere.         |

## Configure `reply_to`

Set `reply_to` in your send request when replies should go to a different mailbox than the `from` address.

```json theme={null}
{
  "from": {
    "email": "notifications@example.com",
    "name": "Example App"
  },
  "reply_to": {
    "email": "support@example.com",
    "name": "Example Support"
  }
}
```

## What webhooks do not include

MailChannels webhooks report delivery events such as processing, delivery, bounces, drops, complaints, and unsubscribe activity. They are not inbound message webhooks and do not include reply content.

If your product needs reply parsing, store the outbound `request_id` and message metadata in your application, then connect replies through your mailbox or inbound provider.