# Get replies to your app's email

Connect Resend, which your app sends its email through, and replies arrive with the email they answer and your order or account on them.

For developers · Updated October 18, 2026 · https://userookery.com/help/connect-your-sending-service/

Your app sends its own email: receipts, shipping updates, password resets. When a customer hits Reply, that reply can land in Rookery as a conversation in the right inbox, with the email your app sent shown above it and the order or account it's about.

Rookery doesn't send your app's email. Your app keeps sending through its own service. Rookery takes over at the reply.

Connections come with the Pro and Team plans, with the API. Only owners and admins can set them up.

## Step 1: point replies at Rookery

In your app, set the reply address on the email it sends to one of your Rookery inboxes, with your order or account id after a `+`:

`support+order_8841@yourdomain.com`

When the customer replies, the conversation shows **Ref order_8841**. Your developer changes one line for this; the [developer guide](https://userookery.com/developers/send-from-your-app/) has it for each service. This works with any sending service, connected or not.

## Step 2: connect Resend

If your app sends through Resend, connect it, and Rookery keeps an outline of what your app sent, so a reply arrives with that email above it:

1. In Resend, go to **API Keys** and create a key with **Full access**. Rookery uses it to add its webhook, and to read one email when someone replies to it.
2. In Rookery, go to **Settings → Developers → Connections**.
3. On **Connect Resend**, paste the key in **API key**.
4. Click **Connect Resend**.

The card says **Connected**, the last four characters of the key, and when Resend last told Rookery about an email.

## What Rookery keeps

- **For each email your app sends:** who it went to, when, the subject, and its reference. Not its words. Nobody sees it in an inbox, and it doesn't count as an email you sent from Rookery.
- **After 30 days with no reply,** Rookery forgets it.
- **When a customer replies,** Rookery reads that one email's words from Resend, shows them under **What your app sent** at the top of the conversation, and keeps them with the conversation.
- **Each workspace keeps up to 50,000** emails nobody has replied to. Past that, the oldest go first.

## Disconnect

Go to **Settings → Developers → Connections** and click **Disconnect**. Rookery removes its webhook from Resend and forgets the key. Conversations that already have replies keep what your app sent.

## Good to know

- If Resend turns the key down (it was deleted there, say), the card says **Needs a look** with the reason, and the conversation shows only the outline. If Resend is just slow or down for a while, Rookery tries again over the next couple of hours before it says so. One email Resend no longer has doesn't change the card.
- Only a reply from someone your app's email went to gets that email shown above it. Anyone else who replies to it gets a conversation of their own.
- Apps on other services can tell Rookery what they sent with the API instead: see [Send from your app, reply in Rookery](https://userookery.com/developers/send-from-your-app/).
- [Webhooks](https://userookery.com/help/webhooks/) tell your app when someone replies, with your reference on them.