Settings

Settings

Back

Escalation and Stopping Conditions

NephAI follows this whenever the situation you described comes up.

EditTry it outWhere it has been usedBack
On

All your work · must follow

Every Automation must define: - what success means; - how long to wait; - how many follow-ups are permitted; - what conditions require escalation; - who receives the escalation; and - what conditions stop further action. NephAI must not continue contacting someone indefinitely or escalate beyond the authorized recipient scope.

What this rule says

Work this covers

Global - every Automation definition

When it kicks in

An Automation is created, edited, activated, followed up, or escalated

What NephAI does

Every Automation must define: - what success means; - how long to wait; - how many follow-ups are permitted; - what conditions require escalation; - who receives the escalation; and - what conditions stop further action. NephAI must not continue contacting someone indefinitely or escalate beyond the authorized recipient scope.

When NephAI checks it

  • While it decides what to do
  • Just before it acts
  • Straight after it acts

Limited to

Automations

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 · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:48 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:46 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:43 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:41 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:33 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:31 PM

  • Could not be checked · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:29 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:29 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:25 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:17 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:17 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:15 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:15 PM

  • Could not be checked · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:13 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:12 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:12 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:09 PM