# A day with a worker

> One worker, two clients, one morning. What it looks like from inside Slack.

Ergoly Docs › Overview. Web: https://www.ergoly.ai/docs/a-day-with-a-worker · Index: https://www.ergoly.ai/docs/llms.txt

Your agency is on Ergoly with one worker, Nora, who handles account management for two clients, Acme and Globex. Here is a Tuesday.

## 9:00 — a routine runs

Nora has a routine that runs every weekday morning for each client: pull what moved in the project tracker and post a status note. Nobody asked for it today. It runs because it was scheduled once.

```slack
#acme

Nora (worker) [Every weekday 9:00]: Morning. Status as of 9:00: identity approved, website build past halfway, launch copy with your legal team. A board-ready one-pager is in this thread.
  [Acme rebrand · status] Identity: approved Sep 12 · Website: 14 of 22 pages built · Launch copy: with Acme legal
```

*A routine posts where it was told to. Globex gets its own note, from its own copy of Nora.*

## 10:40 — a client asks

Daniel at Acme asks for something in the shared channel. Nora answers in a thread, as your agency, from everything it knows about Acme and nothing else.

```slack
#acme

Daniel · Acme: @Nora can you send over where the rebrand stands before our board meeting Thursday?
Nora (worker): Yes. Everything from this morning still holds, and legal came back an hour ago with two small edits. I've folded them in; the updated one-pager is attached.
```

## 11:15 — you correct it

You read the thread and want the one-pager shorter. You say so, once. Nora fixes it and keeps the rule.

```slack
#acme-internal

Sam: @Nora board one-pagers for Acme should fit on one screen. No appendix.
Nora (worker): Done. I've cut the appendix and I'll keep Acme's board one-pagers to one screen from now on.
```

*The rule is filed with Acme. Globex's one-pagers are unchanged.*

## 14:00 — it asks before acting

Nora is set to get approval before anything goes to a client's mailing list. It drafts, then asks.

```slack
#globex-internal

Nora (worker): Globex's launch email is drafted for Thursday 8:00. It goes to 1,240 subscribers. Approve to schedule it, or tell me what to change.
  [Approve · Reject] Launch email · Globex · Thursday 8:00 · 1,240 recipients
Priya: Approved.
Nora (worker): Scheduled. Priya approved at 14:02.
```

*Whoever presses the button is recorded with the decision.*

## 16:30 — it hands something off

A question comes up that needs a person. Nora opens a task, hands it to the account lead, and waits.

```slack
#acme-internal

Nora (worker): Acme asked whether the launch can move a week. That's a scope and budget call, so I've handed it to @Sam. I'll reply to Acme once you decide.
```

*A task waits for its holder. Nothing goes to the client until you answer.*

That is the whole loop: routines run, clients ask, you correct, it asks when it should, and it hands off what is not its call. Each of those has a page of its own.

- [Routines](https://www.ergoly.ai/docs/work/routines): Tasks that repeat, across clients.
- [Memory](https://www.ergoly.ai/docs/workers/knowledge/memory): How a correction becomes a rule, and where it is kept.
- [Approvals](https://www.ergoly.ai/docs/work/approvals): Asking first, and the record of who decided.
- [Tasks](https://www.ergoly.ai/docs/work/tasks): Handing work to a worker, or to a person.