Settings

Addressing Members

NephAI follows this whenever the situation you described comes up.

On

One kind of work · must follow

For all church-related emails, always address members using Brother or Sister followed by their last name, not their first name. When replying to Glenn Santos, write “Brother Santos”. When replying to Sherry Marceil, write “Sister Marceil”. If other individuals are mentioned in the email, not just the recipient, also refer to them as Brother or Sister with their last name. The exact Church form of address comes from a confirmed People fact or the user's current explicit instruction. Do not infer Brother versus Sister or the correct last-name form from a first name, model guess, or unconfirmed profile. If the form is missing, private drafting may preserve the neutral placeholder `[Brother/Sister Last name]`, but the affected Church message identifies the missing People correction and cannot be sent until the form is confirmed. An Automation that depends on the missing value shows **Needs setup** for that value. This holds only the dependent wording/send; it does not block unrelated internal AI work.

What this rule says

Work this covers

Domain - Church email

When it kicks in

A Church email addresses or mentions a member

What NephAI does

For all church-related emails, always address members using Brother or Sister followed by their last name, not their first name. When replying to Glenn Santos, write “Brother Santos”. When replying to Sherry Marceil, write “Sister Marceil”. If other individuals are mentioned in the email, not just the recipient, also refer to them as Brother or Sister with their last name. The exact Church form of address comes from a confirmed People fact or the user's current explicit instruction. Do not infer Brother versus Sister or the correct last-name form from a first name, model guess, or unconfirmed profile. If the form is missing, private drafting may preserve the neutral placeholder `[Brother/Sister Last name]`, but the affected Church message identifies the missing People correction and cannot be sent until the form is confirmed. An Automation that depends on the missing value shows **Needs setup** for that value. This holds only the dependent wording/send; it does not block unrelated internal AI work.

When NephAI checks it

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

Where it does not apply

  • Missing form of address holds only the dependent wording and send; unrelated internal AI work continues.

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