Settings
Edit this starting point
Set this up once and reuse it whenever the same kind of work comes round. Nothing you are already running changes unless you choose it below.
What this should achieve
Start here. Everything below is about how NephAI pursues the result you describe in this section, and each part opens when you get to it.
A short name you will recognise in your list — for example “Bishop interviews stay on schedule”.
Describe the finished state, not the steps. For example: “Every bishop has had his yearly interview with me before the end of the year.” NephAI works out the steps.
Choosing stake work lets NephAI route coordination through your executive secretary.
Groups this with similar work in your list, so a long list stays easy to scan.
Context that changes how it goes about the work — for example “interviews are 45 minutes and I prefer mornings”.
For your own memory, months from now, when you wonder whether you still need it.
Fine-tuning most work does not need
Already set to yours. Change it only if this work runs on someone else's clock.
Leave empty and it starts as soon as you switch it on.
Leave empty and it keeps going until you pause it. Useful for one season or one event.
What sets it off
A row you have not finished stays saved as a draft and will not run until you complete it. If you pick a date that some months do not have, such as the 31st, that month is skipped rather than moved to a different day.
The kind of event that should set this off.
Narrow it in your own words so it does not fire on everything — for example “only mail from a bishop asking to reschedule”.
Who is involved
Describe people by their calling or responsibility rather than by name. NephAI looks up who holds that calling at the moment it acts, so this keeps working after a release or a change of calling.
He is your usual route for scheduling, reminders, and chasing things up. NephAI looks up who holds the calling each time — you never name him here.
Write the limit plainly — for example “he may know the meeting is about a temple recommend, but not why”. NephAI does not exceed what you write here.
Identify them by their calling or responsibility, not by name, so it keeps working after a change of calling.
Whatever you chose above, spelled out — for example “Bishop” or “Stake Young Women President”.
A few words — for example “sets up the interview” or “needs to know the date”.
“Every one of them, separately” gives each person their own piece of work.
This happens when a calling is vacant, held by two people, or has no saved email address.
Fine-tuning most work does not need
Only needed when the same calling exists in several places. Leave empty otherwise.
Only needed when you mean the person over one particular area. Leave empty otherwise.
What NephAI is allowed to work on
Tick everything you are happy for it to do here. Ticking something does not let anything leave your name — you set that in the next section.
What you approve, and what NephAI may do on its own
For each thing NephAI works on, say whether you want to see it first or whether it may go ahead alone. Anything that may go ahead alone needs limits: exactly who may be contacted, what may be said, why, when, and when to stop. You confirm those limits once, when you switch this on.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
Chosen from what you ticked above.
If in doubt, choose to see it first. You can always widen this later.
You will see this sentence again when you switch the Automation on, so write it as the thing you are agreeing to — for example “email a bishop to offer two interview times”.
How NephAI knows what is happening
Tell it where to look for progress and how to read what it finds. This section saves once you have answered all of it.
For example “replies in my email” or “the bishop's entry on my calendar”.
So a reply from someone else, or an out-of-office notice, is not mistaken for real progress.
For example “he names a date” rather than “he acknowledges the email”.
Stops NephAI chasing an answer before anyone has had time to give one — for example “not before two working days”.
For example “assume nothing and tell me what is unclear”. It never invents a fact to fill a gap.
For example “after two weeks with no reply, or the moment anything sensitive comes up”.
Fine-tuning most work does not need
One per line. For example “the calling must be confirmed within the last month”. Leave empty if it does not matter.
One per line — for example “the bishop is released” or “the interview is moved”. NephAI then starts again from what is true now.
How NephAI knows it is finished
What actually proves the result you wanted has happened. A sent email, a silent inbox, and a passed deadline never count as proof on their own.
Chasing things up, and when to stop
NephAI never chases anyone unless you set a number below — it stays at none until you change it. This section saves once you have answered all of it.
So NephAI knows when to stop nudging. For example “he gives me a date, or tells me he cannot”.
For example “one week”. Say it however you would to a person.
Zero means it never nudges anyone on its own — it brings it to you instead. This is the safe default.
Usually you. Name a calling rather than a person if it should go to someone else.
One per line — for example “no reply after two nudges” or “the date has passed”.
One per line — for example “he tells me he will handle it himself” or “the meeting is cancelled”.
Fine-tuning most work does not need
Leave empty and the wait above applies each time. Set it to avoid nudging twice in quick succession.
For example “nothing before 8am or after 9pm, and nothing on Sunday”.