Inboxes

An inbox is a shared mailbox for one address, such as [email protected]. Mail sent to the address is grouped into conversations (threads) that your team can read, label, assign, archive and answer from the dashboard or the API. Replies are sent from the inbox address through usend's normal sending pipeline.

#Create an inbox

1. Verify your domain and turn on receiving for it.
2. Open Inboxes in the dashboard and choose New inbox, or call POST /inboxes.

The address must be on one of your verified domains with receiving enabled. Addresses nobody has created an inbox for keep working as before: everything sent to your receiving domain is still stored under Inbound and fires email.received. An inbox adds threads on top; it does not replace that.

#Threads

A received message joins an existing thread when:

1. its In-Reply-To or References header names a message already in the inbox, including the messages you sent from it, or
2. it has the same subject (ignoring Re: and Fwd:) as a thread from the last 30 days that the sender already took part in.

Otherwise it starts a new thread. New mail in an archived thread moves it back to the inbox.

Each thread lives in one folder: inbox, archive, spam or trash. It can have labels and one assignee, who must be a member of your organization.

#Reply, forward and drafts

• Reply goes to the sender (or their Reply-To); reply all includes the other recipients. In-Reply-To and References are set so the conversation threads in the recipient's mail client.
• Forward quotes the original message and forwards its attachments.
• Drafts are saved messages, new, reply or forward, that you can edit and send later. Sending a draft deletes it.

Sent messages count towards your quota and follow your sending policy like any other email, and show up in Emails too.

#Webhooks

Inboxes fire inbox.* events, for example inbox.email.received and inbox.thread.assigned. See Event types.