# Superhuman mail Auto Label with only first contact emails

**URL:** <https://connect.superhuman.com/t/superhuman-mail-auto-label-with-only-first-contact-emails/61975>\
**Category:** Bugs\
**Created:** [November 3, 2026, 10:01am UTC](https://connect.superhuman.com/t/superhuman-mail-auto-label-with-only-first-contact-emails/61975 "2026-11-03T10:01:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eva\_Cossart](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/eva_cossart/32/50360_2.png) [@Eva\_Cossart](https://connect.superhuman.com/u/Eva_Cossart)\
**Post date:** [November 3, 2026, 10:01am UTC](https://connect.superhuman.com/t/superhuman-mail-auto-label-with-only-first-contact-emails/61975/1 "2026-11-03T10:01:02Z")

</div>

Hello all 😊

I want an auto-label “Newsletter\_to\_do” to include only relevant, original incoming emails from external sources, such as press releases, press invitations, event announcements from members, and job, internship, or freelance opportunities.

The label keeps being applied to emails that should be excluded, especially replies, forwarded messages, and threads involving our organization.

\*_I want to exclude all replies and follow-ups in conversations involving my domain @domainename.fr._

I’ve tried making these exclusions explicit in the prompt, but the filter still labels all those messages. Is there a recommended way to write this rule, or a limitation in how AI labels evaluate email threads, sender/recipient domains, or the first message in a conversation?

Here are some screenshots to help understand the problem:

 ![image](https://global.discourse-cdn.com/coda1/original/3X/4/b/4bab8b5eef18ba739e2ffbdd0c824c6045a5a898.png)

Thanks in advance for reading me 😊

---

<div class="post-metadata">

**Author:** ![Christiaan\_Huizer](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/christiaan_huizer/32/28269_2.png) [@Christiaan\_Huizer](https://connect.superhuman.com/u/Christiaan_Huizer)\
**Post date:** [November 3, 2026, 11:16am UTC](https://connect.superhuman.com/t/superhuman-mail-auto-label-with-only-first-contact-emails/61975/2 "2026-11-03T11:16:04Z")

</div>

The reason this prompt is failing comes down to how Superhuman evaluates conversations and how LLMs process negative conditions inside conversational threads.

### Why the Current Rule Fails

1. **Thread-Level Context Leakage:** Superhuman’s Auto Label evaluates the **entire conversation thread** , not just individual incoming messages. If an initial external email meets the criteria for a press release or announcement, the model matches the positive signal. When you reply or forward it, the original positive text is still sitting in the thread history.

2. **Negative Condition Drift:** Natural language instructions like _“Exclusion prioritaire : si le … a envoyé un mail…”_ require the LLM to reason across multiple roles, timestamps, and message origins. Language models frequently suffer from “negative constraint neglect”—they latch onto the strong positive topical signals (e.g., _communiqué de presse_, _invitation_, _offres d’emploi_) and overlook the exclusion condition.

3. **Drafting at Character Limits:** The prompt in the screenshot is at **993 / 1000 characters** , forcing complex French phrasing into a cramped space where attention to exclusions degrades.

### The Architecture Fix

Rather than asking an LLM to do deterministic routing that email headers handle much better, split the logic into two parts: **deterministic boundaries** and **semantic classification**.

#### 1. Move Hard Exclusions to the UI Filter

Directly below the prompt box, click **“Add exclusions”** :

- Set a hard deterministic rule: **From / Sender does not contain `@domainename.fr`** (or use the deterministic filter blocks if available in your rule builder).

- If you only want original external emails, use the deterministic exclusion chips to strip your internal domain entirely before the LLM even evaluates the text.

#### 2. Reframe the AI Prompt (Positive Boundaries + Strict Negatives)

When structuring rules for an LLM classifier, avoid narrative conversational French. Use crisp, hierarchical Markdown with explicit positive targets and clear exclusion gates:

Markdown

```auto
## Goal
Label only incoming, first-contact announcements from external senders suitable for newsletter publication.

## Must Include
- Original press releases (communiqués de presse)
- Press invitations & member event announcements
- Job, internship, or freelance opportunities (offres d'emploi, stages, piges)

## Strictly Exclude (DO NOT LABEL)
- Any conversation containing a reply, forward, or message from *@domainename.fr*
- Subject lines containing "Re:", "Fwd:", or "Tr:"
- Internal operational discussions, administrative confirmations, or follow-up threads
- Routine correspondence or 1-on-1 member discussions

```

### Best Practices to Lock It Down

- **Subject Line Signals:** Explicitly adding `Subject lines starting with Re:, Fwd:, Tr:` gives the model a clear syntactic anchor rather than forcing it to analyze conversational chronology.

- **Active Tuning:** Use the **✔ / ✖** buttons on the right-hand preview panel for the false matches (such as the `Re: Communiqué` threads currently showing). Superhuman uses those binary signals to calibrate the threshold and reinforce the exclusion rule across the thread evaluation layer.

---

<div class="post-metadata">

**Author:** ![Eva\_Cossart](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/eva_cossart/32/50360_2.png) [@Eva\_Cossart](https://connect.superhuman.com/u/Eva_Cossart)\
**Post date:** [November 4, 2026, 9:28am UTC](https://connect.superhuman.com/t/superhuman-mail-auto-label-with-only-first-contact-emails/61975/3 "2026-11-04T09:28:50Z")

</div>

> [@Christiaan\_Huizer](#):
>
> - **Active Tuning:** Use the **✔ / ✖** buttons on the right-hand preview panel for the false matches (such as the `Re: Communiqué` threads currently showing). Superhuman uses those binary signals to calibrate the threshold and reinforce the exclusion rule across the thread evaluation layer.

Thanks so much for answering my question @Christiaan_Huizer and for the explanation 🤩 ✨

I’d tried exclusion rules for both a domain and a specific email address yesterday, but neither worked really well until… I followed your advice 😊

I shortened the prompt and changed the exclusion setting from `*@mydomainname.com` to `@mydomainname.com`. It works much better now.

Before: Emails in reply threads (with “Re:” in the subject) were automatically labeled.

 ![Auto_label-Superhuman-2b](https://global.discourse-cdn.com/coda1/original/3X/b/9/b9a89981ef602b450637a3d60cccb1b61f593550.png)

Now: Nearly all email threads with replies from my domain are excluded (some still bypass the rule but it may come from how I parameter it.

 ![image](https://global.discourse-cdn.com/coda1/original/3X/1/d/1dcc3e62980d278a1d8bcd9a3ee677450888fe66.png)

Thank you for the help and have a nice day !

---

<div class="post-metadata">

**Author:** ![Eva-Automation](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/eva-automation/32/49253_2.png) [@Eva-Automation](https://connect.superhuman.com/u/Eva-Automation)\
**Post date:** [November 4, 2026, 10:15am UTC](https://connect.superhuman.com/t/superhuman-mail-auto-label-with-only-first-contact-emails/61975/4 "2026-11-04T10:15:02Z")

</div>

> [@Eva\_Cossart](#):
>
> I shortened the prompt and changed the exclusion setting from `*@mydomainname.com` to `@mydomainname.com`. It works much better now.

Edit : it seemed to work better with last settings but you can’t put “@yourdomainname.com” as it’s not a valid request. Be sure to use “\*@yourdomainname.com” if you ever want to do this.

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/system/32/24484_2.png) [@system](https://connect.superhuman.com/u/system)\
**Post date:** [November 6, 2026, 10:15am UTC](https://connect.superhuman.com/t/superhuman-mail-auto-label-with-only-first-contact-emails/61975/5 "2026-11-06T10:15:59Z")

</div>

Closed on November 6, 2026, 10:15am UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
