Workflows · People

A new teammate,nothing forgotten.

Tell the lead agent who joins and when. It writes the checklist, puts the work on a board, and you give each task an owner — a helper drafts the access requests, the lead plans the first week, and the welcome message waits until the accounts exist. Every morning its daily prompt reads the checklist and, with your OK, reminds whoever is holding a step up in the team chat.

Day one: checklist and requests. Next morning: a nudge, two answers, the blocked task goes out. Allow the nudge when asked.

The lead builds a checklist and a board; a helper drafts access requests; next morning the daily prompt nudges the owners and the blocked welcome goes out.

One checklist

A to-do card both of you edit: the lead ticks steps as answers come in, you can click any step yourself.

Tasks with owners

Each task on the board is assigned to one agent; auto-dispatch sends it only to that agent.

Blocked until ready

The welcome message depends on the access task and goes out by itself the moment that task is done.

Nudges, not nagging

The morning prompt reminds only the owners of waiting steps, in one message, after you allow it.

Workflows · People

From “she starts Monday” to a ready first day

Two agents, a checklist, a board and the team chat.

01
Plan
Checklist and board tasks.
02
Assign
An owner per task, one dependency.
03
Nudge
Each morning, only what is stuck.
04
Welcome
Goes out when the accounts exist.
Related scenarios

More in Workflows

Other live scenarios from the same shelf — and a few close relatives.

Browse all 40 scenarios

Give every new hire a first day that works

The agents track it; people do only their part.

Download for WindowsWindows 10 / 11 · 64-bit

macOS and Linux are coming later.

The first-run wizard installs an agent CLI, Git and the dictation model for you — or skips each step.