Checklists

When a job takes several related changes, the agent writes them all down as a checklist before it changes anything. You start it once, and it follows you from page to page until it’s done.

One job, not five requests

Say a product manager wants the board of customer questions to show which team answers each one. That’s two changes. There’s a new field, Team, and a change to the template customer questions follow, so every one of them carries Team on its card.

Asked one change at a time, you’d make each on its own page, in the right order, and keep in your head what was left. We built checklists after an agent was asked for a template and the fields it needs, drafted the template, and told the person to make the fields by hand. Now the checklist keeps the order and the progress. You can leave a job, come back to it, or stop it, and what’s done stays done.

Written down, then started

You ask any agent for the job, in your words. The agent checks what exists already and leaves that out. It writes the rest on one card in the chat, every step in order and nothing done yet. Starting it is your go-ahead for the whole list.

From then on the checklist sits in the right rail of whichever page you open. The agent runs a long step, like writing a topic, while you do something else. When it’s done, it lists what it made, each with a link.

When what’s left is a single change, there’s no checklist to run. The card is that change, and one press makes it.

Guided or Autonomous

In Guided, the agent waits for your Next at every step, so you can read why. When a step fills in a page, like a template, the agent fills it part by part as you watch, with its reason beside each part.

In Autonomous, the agent goes through the steps you approved without that walk-through. It still stops for what only you can do, like a deletion, a key only you have, or anything that leaves Emargen. It stops at a failure too.

You choose on the card, and can switch at any time. Until you change it in Your profile, you start on Guided.

Stopping, and failures

No step runs twice, and nothing is undone. Stop keeps what’s done. If a step fails, the checklist stops there and shows you the page’s own message. Ask the agent beside the page to change it. It offers a changed checklist as a new card, and once you start that, it carries on from the first step not done.

A checklist runs as you, so it can do only what you may do, and nobody else sees it. You have one at a time. A second one waits until the first ends or you stop it. While a checklist waits on you, it also shows in Decisions, so it doesn’t wait unseen.

A checklist is a job of your own, done once. A flow is different. It takes case after case through a kind of work, between several people.

Next

How to

• Let the agent do a job of several steps

Page by page

• The checklistthe rail part by part