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

# Statuses

> Every thread status in Plain - Todo, Snoozed and Done - what each means and when to use it.

Every thread has a **status** to show you exactly where it is in your workflow at a glance. New threads are created with *Needs first response*; once you reply, they move to *Needs next response*. You can snooze a thread while waiting on the customer, move it to *Investigating* for deeper internal work, and mark it *Done* when resolved. Statuses drive your **SLA** timers. Plain tracks first and next response time commitments per thread and you can configure alerts for your team before a breach occurs.

[Read about SLAs →](/docs/product/platform/slas)

Every thread in Plain has a status that reflects where it sits in your support workflow. Statuses keep your queue organized and drive SLA timers so your team always knows what needs attention and what can wait.

There are three status groups: **Todo**, **Snoozed**, and **Done**.

What each status means, and when to use it.

## Todo

Todo threads are active and require action from your team.

### Needs first response

<Frame>
  <img src="https://mintcdn.com/plain/O6H8aFQxBwl-gnm6/public/images/statuses-todo-needs-first-response.png?fit=max&auto=format&n=O6H8aFQxBwl-gnm6&q=85&s=2d4f45f7785a1e36744bbe9c2786d03c" alt="Needs first response in Plain" width="2400" height="639" data-path="public/images/statuses-todo-needs-first-response.png" />
</Frame>

The thread has been created, but the customer hasn't received any reply yet. This is where **First Response Time SLAs** apply.

### Needs next response

<Frame>
  <img src="https://mintcdn.com/plain/O6H8aFQxBwl-gnm6/public/images/statuses-todo-needs-next-response.png?fit=max&auto=format&n=O6H8aFQxBwl-gnm6&q=85&s=1bca21be6c72ed8ae4440baf0a8b0a96" alt="Needs next response in Plain" width="2400" height="639" data-path="public/images/statuses-todo-needs-next-response.png" />
</Frame>

The customer has replied, and it's your turn to respond. This is where **Next Response Time SLAs** apply.

### Investigating

<Frame>
  <img src="https://mintcdn.com/plain/O6H8aFQxBwl-gnm6/public/images/statuses-todo-investigating.png?fit=max&auto=format&n=O6H8aFQxBwl-gnm6&q=85&s=e67b393c2ca003a2693ba4639a57692a" alt="Investigating in Plain" width="2400" height="639" data-path="public/images/statuses-todo-investigating.png" />
</Frame>

Your team is working on the request internally. Use this status when a thread needs deeper technical investigation before you can reply.

### Close the loop

<Frame>
  <img src="https://mintcdn.com/plain/O6H8aFQxBwl-gnm6/public/images/statuses-todo-close-loop.png?fit=max&auto=format&n=O6H8aFQxBwl-gnm6&q=85&s=048f5ee8be777e72b02f89becdf088f5" alt="Close the loop in Plain" width="2400" height="639" data-path="public/images/statuses-todo-close-loop.png" />
</Frame>

The thread is linked to a known issue that has now been resolved. Plain moves threads to this status automatically so you can follow up with the customer.

## Snoozed

Snoozed threads are temporarily paused and won't surface in your active queue.

### Waiting for customer

<Frame>
  <img src="https://mintcdn.com/plain/O6H8aFQxBwl-gnm6/public/images/statuses-snoozed-waiting-customer.png?fit=max&auto=format&n=O6H8aFQxBwl-gnm6&q=85&s=1387da31289355f77923dbe5e38590d0" alt="Waiting for customer in Plain" width="2400" height="639" data-path="public/images/statuses-snoozed-waiting-customer.png" />
</Frame>

You've responded and are waiting on the customer to reply.

By default, Plain moves threads to this status after your reply. You can change this in **Settings → Workflow.**

### Paused for later

<Frame>
  <img src="https://mintcdn.com/plain/esnLSCL6AbjPxXFS/public/images/statuses-snoozed-paused-later.png?fit=max&auto=format&n=esnLSCL6AbjPxXFS&q=85&s=685d695634fd70cb8de7e553ff5fc550" alt="Paused for later in Plain" width="2400" height="639" data-path="public/images/statuses-snoozed-paused-later.png" />
</Frame>

You've intentionally paused the thread.

## Done

Done threads are closed and no longer require action.

### Done

<Frame>
  <img src="https://mintcdn.com/plain/esnLSCL6AbjPxXFS/public/images/statuses-done.png?fit=max&auto=format&n=esnLSCL6AbjPxXFS&q=85&s=6a308faab6943f78f1ec04160011058a" alt="Done in Plain" width="2400" height="639" data-path="public/images/statuses-done.png" />
</Frame>

The issue is resolved, and you've marked the thread as complete. This status feeds into reporting, helps clear your queue, and provides clarity across your team. If the customer replies again, the thread will reopen automatically.

### Ignored

<Frame>
  <img src="https://mintcdn.com/plain/esnLSCL6AbjPxXFS/public/images/statuses-ignored.png?fit=max&auto=format&n=esnLSCL6AbjPxXFS&q=85&s=bc1457101c00622aedefdc3de68a14d7" alt="Ignored in Plain" width="2400" height="639" data-path="public/images/statuses-ignored.png" />
</Frame>

The thread needs no action from your team and has been explicitly ignored. Ignored threads are silenced. They won't trigger notifications, affect metrics, or move statuses. This is ideal for keeping your support workflow clean in multi-use Slack channels or integrations.
