05 — How it works
From an uncovered function to a record of the work.
Ten steps, in the order you would actually take them. The workspace beside them changes as each step becomes current.
- Step 1
Select an employee role
You start from the work, not from the technology. Pick the role that matches the function nobody is covering.
See every roleInteractive product walkthrough- AE-01 Customer Support
- AE-02 Sales Development
- AE-03 Marketing
- Step 2
Configure its remit
What this employee is for, in your words. Just as importantly: what falls outside it, so it knows where to stop.
Interactive product walkthrough- Handles inbound questions in the connected inbox
- Outside: billing decisions, refunds, delivery dates
- Step 3
Provide business context
Your policies, your tone, what counts as an escalation. This is what it retains across assignments so you are not briefing it again each time.
Interactive product walkthrough- Documented policies
- Tone guidance
- Escalation rules
- Step 4
Connect permitted tools
Choose what it may reach and at what level. Read access is separate from the ability to act, and scope narrows both.
Interactive product walkthrough- Inbox — read + act, support address only
- Helpdesk — read
- Billing — none
- Step 5
Define approval boundaries
Name the actions that must wait for a person. This is the decision the rest of the product is built around.
Interactive product walkthrough- First reply in a new thread — waits
- Anything touching billing — waits
- Committing to a date — waits
- Step 6
Assign the first work
Through a structured task, a chat message, or your voice. Whichever route you use, it becomes the same object.
Interactive product walkthrough- Assigned via voice · 08:41
- Step 7
Monitor progress
The work carries on after you close the laptop. The queue shows where every item has got to, without you asking.
Interactive product walkthrough- Read the thread and the delivery policy · 08:44
- Reply drafted · 09:20
- Step 8
Answer a question, or approve an action
At a boundary it stops and asks, naming which boundary it hit. You approve, request changes, or stop the work.
Read how control worksInteractive product walkthrough- Stopped at a boundary and asked for approval · 09:22
Waiting for you
ApproveRequest changes - Step 9
Receive the deliverable
Named and typed in text, with the role and task reference that produced it. Never a fake file preview.
Interactive product walkthrough- Approved replying for the first time · 09:36
- Delivered Draft reply · 09:41
- Step 10
Keep the record
Append-only, and permanent. A rejected action stays in it exactly like an approved one — that is what makes it a record rather than a feed.
See the whole workspaceInteractive product walkthrough- T-2288 · Draft reply · 09:41
- T-2274 · Unresolved issues, week 21 · Fri 17:48