Settings

Recipient Scope

NephAI follows this whenever the situation you described comes up.

On

One kind of work · must follow

For church-related replies, preserve the current thread's recipient scope by default. Use Reply All only when the response is appropriate for everyone currently included. When an inbound message reaches the user while none of the user's connected addresses appears in To or Cc, treat that hidden delivery as a blind copy for awareness by default. Do not prepare a reply unless current evidence explicitly asks the user to respond, continues one of the user's commitments, or requires the user's authority. Before sending, verify: - whether each recipient needs the information; - whether the message contains confidential or sensitive information; - whether someone was copied only for awareness; - whether someone previously included has intentionally been removed; and - whether a new recipient is being added and why. Never remove required participants, add previous participants back automatically, or expose confidential information merely to preserve Reply All.

What this rule says

Work this covers

Domain - Church email

When it kicks in

A Church thread reply is planned or sent

What NephAI does

For church-related replies, preserve the current thread's recipient scope by default. Use Reply All only when the response is appropriate for everyone currently included. When an inbound message reaches the user while none of the user's connected addresses appears in To or Cc, treat that hidden delivery as a blind copy for awareness by default. Do not prepare a reply unless current evidence explicitly asks the user to respond, continues one of the user's commitments, or requires the user's authority. Before sending, verify: - whether each recipient needs the information; - whether the message contains confidential or sensitive information; - whether someone was copied only for awareness; - whether someone previously included has intentionally been removed; and - whether a new recipient is being added and why. Never remove required participants, add previous participants back automatically, or expose confidential information merely to preserve Reply All.

When NephAI checks it

  • While it works out what is going on
  • While it decides what to do
  • Just before it acts

Limited to

Church email

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It holds that piece of work and brings it to you rather than proceeding against this rule.

Try it out

See where this rule would take effect and how NephAI reads the cases you set up. This only shows you the result — nothing is saved, sent, or changed.

Where this rule has been used

Clashes with other rules

0

None. This rule has never asked for something another rule contradicted.

Times NephAI used it

50
  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 9:57 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 9:57 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 9:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 9:55 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 8:26 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 8:18 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 8:18 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 6:18 PM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 9, 2026, 12:31 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 12:30 PM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 9, 2026, 12:13 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 12:12 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 11:44 AM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 10:24 AM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 8:22 AM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 9, 2026, 6:08 AM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 9, 2026, 6:07 AM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 9, 2026, 6:06 AM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 11:26 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 9:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 9:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 9:55 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 9:55 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 8:24 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 7:04 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 6:16 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 6:12 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 6:00 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 5:18 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 5:06 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 2:54 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 1:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 11:56 AM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 10:22 AM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 8, 2026, 7:02 AM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 8, 2026, 6:03 AM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 8, 2026, 6:03 AM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 8, 2026, 6:02 AM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 9:57 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 9:57 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 9:55 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 8:24 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 6:14 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 6:06 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 5:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 5:16 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 1:54 PM

  • Taken into account · Pre-drafted reply

    on an email conversation

    Sep 7, 2026, 12:23 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 12:22 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 7, 2026, 11:54 AM