Email replies that find their conversation
Mail you send from a mailbox, a ticket or a contact's card carries a private reply address, so the customer's answer lands on the same conversation, ticket and card. Here is how to read where a reply went, which address you answer from, and what to do when a reply did not attach.
Steps
- Send as usual. Mail sent from a mailbox of your workspace, from a ticket or from a contact's card leaves from the same address as always. Only its reply address carries a private tag, which is how the answer finds its way back.
- When the customer answers, the answer lands on the same conversation, and on the ticket and the contact's card that point at it. A pending or solved ticket goes back to Open and the response clocks move. A closed ticket stays closed.
- Open Mail, Team and pick a conversation. The panel How this conversation was put together shows why the latest message is there: Reply address, Headers, or Sender and subject. It also shows the workspace, domain, client and queues the conversation sits in.
- Look at the sending address above the reply box before you send. A reply leaves from the address the mail arrived at. When there is none, the system tries the ticket's mailbox, then the one last used with this contact, then the client's default, the queue's default and the workspace default. The reason is shown, you can choose only among mailboxes you may send as, and if nothing fits you are asked to choose, never guessed for you.
- A reply from an address that is not the customer's is attached and marked Different sender, with Needs review on the list. Check that it is the same person and press Yes, this is the same customer. Until then it does not move any clock.
- Automatic answers, such as out of office, are attached but do not reopen the conversation or start a clock. A message that bounced shows as not delivered on the conversation.
- A conversation that gets more replies in a day than one reply address allows (30) holds the rest for review and shows Held. A reply to a conversation that was closed more than 90 days ago opens a linked follow-up, with a link to the earlier one.
- Brand My Inbox MCP: conversations_overview, conversation_explain, conversation_confirm_sender (inbound:write) and conversation_set_default_sender (addresses:write). EmailPro MCP: conversation_thread reads the email thread of a ticket as you.
Questions
- Why did a reply not attach to the conversation?
- Open the conversation and read How this conversation was put together. The usual reasons: the customer wrote from another address (confirm it); the conversation was closed more than 90 days ago (a linked follow-up was opened); the sender and subject fit more than one open conversation, so nothing was joined by itself and the possible ones are listed; the monthly limit of tracked conversations was reached (mail still arrives and is threaded by its headers); or the mail was sent from a desktop mail program over SMTP, which carries no tag.
- Does the customer see the private tag?
- Only inside the reply address. The From address is never changed, and the customer answers as they always do.
- Is this on the free plan?
- Yes, within a small limit: 100 tracked conversations a month on Free, 2,000 on Paid and 10,000 on Agency. At the limit nothing is lost: mail still arrives and is threaded by its headers, and only the private tag is left out.
- Can a colleague read a thread from a mailbox they cannot read?
- No. A conversation, its ticket thread and its line on a card are exactly as visible as the mailbox and queues they belong to.
Updated 2026-11-19 · llms-full.txt