Settings

Calling-Based Routing

NephAI follows this whenever the situation you described comes up.

On

One kind of work · must follow

Route matters according to current callings and stewardships, not hard-coded names. For example: - matters assigned to the first counselor follow whoever currently holds that calling; - every stake scheduling or administrative coordination occurrence evaluates the current executive secretary as its default route and then applies the scenario's Primary, Sanitized, Supporting, or Not routine handling according to verified responsibility, confidentiality, and the explicit Automation; - routine reimbursement processing routes to the current stake clerk, while a current finance clerk already included remains included for support or visibility; - ward matters route through the current bishop or branch president; and - elders quorum matters identify the current elders quorum president and assigned high councilor.

What this rule says

Work this covers

Domain - Church routing

When it kicks in

A Church matter is routed by calling or stewardship

What NephAI does

Route matters according to current callings and stewardships, not hard-coded names. For example: - matters assigned to the first counselor follow whoever currently holds that calling; - every stake scheduling or administrative coordination occurrence evaluates the current executive secretary as its default route and then applies the scenario's Primary, Sanitized, Supporting, or Not routine handling according to verified responsibility, confidentiality, and the explicit Automation; - routine reimbursement processing routes to the current stake clerk, while a current finance clerk already included remains included for support or visibility; - ward matters route through the current bishop or branch president; and - elders quorum matters identify the current elders quorum president and assigned high councilor.

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 routing · Gmail reply drafting

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It carries on. This rule shapes how NephAI thinks and writes, but it never stops work by itself.

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