How email replies are grouped into a single thread

Why your customers' replies land in the right conversation, what happens with the subject, and why a closed conversation sometimes reopens.

Aug 19, 2026

When a customer replies to one of your emails, Omnifox has to decide whether that reply belongs to an existing conversation or starts a new one. The decision is not made from the subject: it is made from the technical email headers, which is the reliable method.

How the decision is made

When an email comes in, Omnifox tries this, in order:

  1. Check whether the In-Reply-To header points to an email that went out from Omnifox.
  2. Read the conversation identifier that Omnifox embeds in its own emails.
  3. Walk the References chain, newest to oldest, applying the two strategies above.

If none of them match, the reply is grouped by contact and channel, the same as on every other channel.

There is one important safeguard: a reply only attaches to a conversation on the same channel. If you have several mailboxes connected, an email that arrived at one will not slip into the conversation of another.

The subject does not group anything

The subject plays no part in the decision. Two emails with the same subject are not merged if they do not share headers, and changing the subject mid-thread does not break it.

When you reply from Omnifox without writing a subject, the subject of the last incoming email is copied and Re: is added in front unless it was already there. That keeps the thread grouped on the customer's side too, in Gmail or Outlook.

Closed conversations reopen

If the customer replies to a thread whose conversation was closed, resolved, or snoozed, the reply reopens it automatically and it returns to the inbox. That is the intended behavior: a customer writing again needs attention.

What does not reopen anything are automatic replies: out-of-office notices, mailing list messages, and bounces are discarded before they reach the inbox.

The references chain gets trimmed

On very long threads, the references chain that Omnifox sends keeps the root email plus the most recent ones that fit. That is standard practice and avoids oversized headers; grouping keeps working.

Verify it

Write to a customer from Omnifox, reply from the customer's mailbox, and check that the reply lands in the same conversation and not in a new one.

If something doesn't work

  • Every reply opens a new conversation: the customer is writing new emails instead of replying, so there are no headers to link.
  • A reply landed in the wrong conversation: check whether the customer replied to a very old email in the same thread.
  • The customer replies from a different address: the email attaches to the thread through the headers, but the new address is not automatically linked to the contact.

Tips

  • Ask customers to reply to the email instead of writing a new one: that is what keeps the history together.
  • If you need to start a separate topic with the same customer, write a new email from the contact instead of replying to the old thread.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp