Settings

Tone and Voice

NephAI follows this whenever the situation you described comes up.

Edit Try it out Where it has been used Back

One kind of work · must follow

Church-related messages must be warm, direct, respectful, pastoral, and concise. Avoid: - corporate jargon; - artificially formal language; - excessive explanation; - unnecessary apologies; - claims of revelation; - language that sounds like a legal notice unless the situation requires it; and - language that transfers responsibility to President Ortolano without evidence.

What this rule says

Work this covers

Domain - Church email

When it kicks in

A Church message is composed or sent

What NephAI does

When NephAI checks it

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 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

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

Times NephAI used it

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