> ## Documentation Index
> Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The Digital Workers Pool

> Watch every Digital Worker conversation, filter by worker or assignee, review held drafts, and approve tool calls.

<Note>
  **Preview feature.** The Digital Workers pool is available to selected workspaces while we refine it.
</Note>

The **Digital Workers pool** (the **Digital Workers** tab in the top navigation) is where every conversation your workers are handling shows up — across portal, in-app, email, and Slack. Open it to read threads, review and send drafts a worker held for approval, and approve or reject actions a worker proposed.

You can view the pool two ways, switched with the **Board** and **List** buttons in the header:

* **Board** — a column per status; drag a conversation between columns to change its status.
* **List** — a status-tabbed list with an inline detail pane on the right.

## Scoping which workers you see

Use the **worker scope** selector in the header:

* **All workers** — conversations from every worker in the workspace.
* **My workers** — only the workers you belong to (you're in the worker's reviewer pool, or you own an account it handles).

Admins and builders default to **All workers**; everyone else defaults to **My workers**.

When the scope is **My workers**, a **Refresh My workers** button appears next to the selector. Click it after CSM-pool or account-owner changes to recompute which workers are "yours" and reload the threads.

## Filtering by assignee

The assignee chips narrow the list by who owns each conversation (pick one; click it again to clear):

| Chip                       | Shows                                                                             |
| -------------------------- | --------------------------------------------------------------------------------- |
| **My items**               | Conversations assigned to you.                                                    |
| **Assigned to Human**      | Conversations assigned to any person in your organization.                        |
| **Auto-managed by Worker** | Conversations with no human assignee — the worker is handling them automatically. |

You can further narrow the list with the standard filter bar (by account, channel, and more).

## Conversation statuses

Each conversation has a **status** — for example **In Progress**, **Needs Response** (a reply is waiting on a human), **On Hold**, or **Closed**. In Board view each status is a column; in List view it's a tab.

<Note>
  Statuses come from a configurable **Conversation** status template — admins can rename them, change their colors, or add new ones under **Settings → Manage status templates**, so your workspace may show a different set.
</Note>

## Opening a conversation

Click a conversation to open its detail. The **Details** tab shows:

* **Status** — change it here (or, in Board view, by dragging the card).
* **Assignee** — assign the conversation to a person from the worker's reviewer pool. Leaving it unassigned means the worker manages it.
* **Digital owner** — the worker responsible (read-only).
* **AI details** — for a held draft, what the worker did to produce it.

Below that, collapsible panels show the customer context (with an **Open account** link) and recent activity.

### Reviewing and sending a held reply

When a worker's autonomy holds a reply (HIL, or the worker deferred), the conversation lands in the response-needed status (often **Needs Response**) with the drafted reply ready to review. Edit it if needed and send. For Slack, a **Send as** selector lets you post as **yourself** or as **the worker** before sending. (Edits autosave — you'll see **Saving… / Saved** as you type.)

### Approving proposed tool calls

If a worker proposes an action that needs approval (for example, creating Jira tickets), it appears as a **tool-approval** card in the conversation: *"Review the pending tool call(s). Approve runs them; Dismiss rejects them."* When several calls are bundled, you can approve or dismiss them individually or all at once. Nothing runs until you approve.

## Related

<CardGroup cols={2}>
  <Card title="Configuring a Digital Worker" icon="sliders" href="/digital-workers/configuring_a_worker">
    Persona, knowledge, tools, autonomy, and channels.
  </Card>

  <Card title="Approvals" icon="circle-check" href="/approvals/overview">
    Review automated workflow actions that need sign-off.
  </Card>
</CardGroup>
