usejarvis Back to homepage

02 / MAKE IT REPEATABLE

Same workflow.
A better-prepared week.

Take call preparation. The people change.
The process doesn’t need reinventing.
Authored example. No apps connected.

Call preparation / exampleREAD THE RESULT. EXPLORE THE PROCESS.
CALL BRIEFMONDAY · 10:00

Before you join

Maya Chen

Founder, Fieldwork

Agree the shape of a two-week pilot.

01

The context

Maya is exploring a pilot for recurring client updates. Keep the conversation focused on approval and the first two accounts.

02

What to remember

You promised an example brief. Bring it, then agree who reviews the first Friday update.

Conversation notes included
ONE QUESTION WORTH ASKING

Who will review the first output before it goes to a client?

3 sources behind this brief
  • Calendar

    Agree the shape of a two-week pilot.

  • Email

    Maya wants to start with two client accounts. She asked how approvals would work before anything reaches a client.

  • Conversation notes · 17 Sep

    Last conversation: the team writes a client update every Friday. You offered to bring an example brief to the next call.

Prepared for you. Nothing sent to attendees.SAMPLE
Try removing a source. The brief should say what’s missing.
THE PROCESS BEHIND THE BRIEF

Four steps.
One needs judgement.

This example keeps the known operations fixed. AI interprets the context.

  1. 01
    FIXED STEPNotice the next meeting

    An upcoming calendar event starts the configured workflow. It needs a connected calendar and an enabled trigger.

  2. 02
    FIXED STEPGather the relevant context

    Read the sources configured for this routine. Missing notes remain missing; this example does not invent conversation history.

  3. 03
    AI · JUDGEMENTPrepare a useful brief

    AI turns the gathered context into a short brief with sources and open questions. This is the part that needs interpretation and uses an AI allowance.

  4. 04
    FIXED STEPSave it for your review

    Save the result to the configured destination. This example sends nothing to meeting attendees. Additional message delivery needs its own connection and permissions.

Before the first real run
Review the draft. Connect sources. Test. Publish. Enable.

Services and inputs can change. Fixed steps make a process inspectable; they don’t guarantee every run succeeds.

Save sample brief

Call preparation is an example you can request, not a routine the current awareness detector automatically suggests. Connections and permissions need to be configured.

Explore workflows in the docs