> For the complete documentation index, see [llms.txt](https://limechatai.gitbook.io/limechat-product-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limechatai.gitbook.io/limechat-product-guide/whatsapp-marketing/flows/action-nodes/change-conversation-status-to-open.md).

# Change Conversation Status to Open

Action Node · Conversation Status Management

### What It Does

This node updates the conversation status in LimeChat CRM to **Open**.

Once marked as Open, the conversation becomes visible and actionable for human support agents inside the CRM.

This is commonly used when transitioning a conversation from an automated workflow to a live support or agent-assisted workflow.

***

### Example

A customer asks a question that the bot cannot resolve automatically.

Before routing the conversation to a support agent, the workflow updates the conversation status to:

> Open

The support team can now view, manage, and respond to the conversation directly from the CRM.

***

## When to Use This Node

Use this node when:

1. You want to move a conversation from an automated state to an active support state
2. You are preparing the conversation for human agent handoff
3. The customer requires manual support or follow-up
4. You want agents to see and act on the conversation in the CRM
5. You are building escalation or live support workflows

***

## Requirements

Before using this node:

* Ensure the workflow logic correctly determines when human intervention is needed
* Use alongside agent assignment or handoff nodes for complete support workflows if required

***

## Supported Events

This node supports:

1. All Events

***

## Setting It Up

### Inputs

This node does not require any user configuration or manual input.

| Input              | Type | Required | Description                                          |
| ------------------ | ---- | -------- | ---------------------------------------------------- |
| No Inputs Required | N/A  | N/A      | Conversation status is automatically updated to Open |

***

## Special Behavior

* The conversation status is automatically set to **Open**
* No manual configuration is required
* The node does not assign ownership to any agent
* Only the conversation status is updated

***

## Outputs

| Output     | Type    | Description                                                                |
| ---------- | ------- | -------------------------------------------------------------------------- |
| successful | Boolean | Indicates whether the conversation status was successfully updated to Open |

***

## Output Behavior

| Output Value | Meaning                                  | Recommended Next Step                     |
| ------------ | ---------------------------------------- | ----------------------------------------- |
| true         | Conversation status updated successfully | Continue with handoff or support workflow |
| false        | Failed to update conversation status     | Retry update or trigger fallback handling |

***

## What Happens After It Runs

Once executed:

* The conversation status changes to **Open**
* The conversation becomes visible to support agents inside LimeChat CRM
* Agents can manually review and respond to the conversation
* The workflow can continue toward assignment, escalation, or handoff steps

***

## Best Practices

Use this node immediately before:

* Agent handoff
* Ticket escalation
* Manual review workflows

Combine with nodes like:

* Assign Agent
* Add Internal Notes
* Handoff to Agent
* Update Ticket Status

Ensure conversations are only opened when human intervention is genuinely required to avoid unnecessary agent workload.

Use proper tagging and notes alongside status updates for better agent context.

***

## Key Reminders

1. No inputs or configuration are required
2. This node only changes the conversation status to Open
3. It does not assign an agent automatically
4. Commonly used before human handoff workflows
5. Helps make conversations visible and actionable inside LimeChat CRM
6. Supports all workflow events
7. No external integrations are required