Inbound

A domain that you created with Inbound has a reply.<domain> host with an MX for receiving. The platform stores and parses the replies that arrive there. The worker ingests them. Inbound shows them.

What is stored

The platform stores the from, the to, the subject, the parsed text and HTML bodies, and the headers. It clips the bodies at 512 KB. The raw message stays in storage. The list shows the newest first. Click a row to see the bodies.

Threading

Outbound messages carry Message-ID: <message id>@<domain>. The platform reads the In-Reply-To and References headers of each reply. If a header names a message id under one of the domains of the organization, the platform links the reply to that message. The reply then appears in the In reply to column here. It also appears at the bottom of the page of the original message in Emails.

Webhooks

The platform delivers every reply to subscribed endpoints as email.received. The payload has inbound_id, email_id (when threaded), from, to and subject. See Webhook payloads.

Using it

Set reply_to on outbound messages to an address on reply.<domain> ("reply_to": "support@reply.example.com"). Replies then come back to the platform. Consume email.received in your app.