Settings

Settings

Back

Complete Context Retrieval

NephAI follows this whenever the situation you described comes up.

EditTry it outWhere it has been usedBack
On

All your work · must follow

Before drafting a reply or taking action, retrieve all relevant context from: - the complete Gmail thread; - related Inbox and Sent messages; - Calendar events; - open and completed Tasks; - the People directory; - relevant Knowledge sources; and - attachments associated with the matter. Use only relevant context. Do not import unrelated information merely because it mentions the same person.

What this rule says

Work this covers

Global; Inbox, Sent, Calendar, Tasks, People, Knowledge, attachments

When it kicks in

A reply or action needs matter context

What NephAI does

Before drafting a reply or taking action, retrieve all relevant context from: - the complete Gmail thread; - related Inbox and Sent messages; - Calendar events; - open and completed Tasks; - the People directory; - relevant Knowledge sources; and - attachments associated with the matter. Use only relevant context. Do not import unrelated information merely because it mentions the same person.

When NephAI checks it

  • While it gathers information
  • While it works out what is going on

Limited to

Inbox · Sent · Calendar · Tasks · People · Knowledge · attachments

What NephAI reads for this

Knowledge

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 · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:59 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:59 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:56 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:56 PM

  • Taken into account · Situation assessment

    on an email conversation

    Sep 9, 2026, 10:56 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:53 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:53 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:24 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:24 PM

  • Taken into account · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 10:07 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:07 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: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 · Automation occurrence planning

    while gathering information

    Sep 9, 2026, 9:51 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 9:51 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 9:49 PM