# Defining Ticket lifecycle

***

Using this feature, the account owner can configure set time intervals after which the conversations automatically move to **Resolved** or **Closed** states.

<table data-full-width="true"><thead><tr><th width="217.5">Setting</th><th>What does it mean</th></tr></thead><tbody><tr><td><strong>Auto Resolve</strong></td><td>Time after which an inactive conversation should get resolved</td></tr><tr><td><strong>Auto Close Duration</strong></td><td>Time after which resolved tickets get closed.</td></tr><tr><td><strong>Auto Resolve Bot Duration</strong></td><td>Time after which an inactive bot conversation should get resolved</td></tr><tr><td><strong>Auto Alert Duration</strong></td><td>Time after which a new conversation should get alerted in case of inactivity</td></tr></tbody></table>

## How to set Auto Resolve, Auto Alert and Auto Close Duration?[​](https://docs.limechat.ai/other-features/auto-resolve-auto-alert-and-auto-close-duration#how-to-set-auto-resolve-auto-alert-and-auto-close-duration)

{% stepper %}
{% step %}
Go to **Settings** > **Inboxes**

<figure><img src="/files/TszcqQLstWgL0TEvjIYK" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click on **Settings** of the Inbox for which you want to do the configurations

<figure><img src="/files/GPolgUf6C6bS1gZouShS" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Turn on the relevant toggles and update time duration for **Auto close, Auto resolve, Auto Resolve Bot,** and **Auto Alert**

<figure><img src="/files/p3v71NDcpLc2j5LQyM7B" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
After updating the duration, click on **Update.**

<figure><img src="/files/4NghZIa2dsDz05hDi9MG" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***

## FAQ's

<details>

<summary><strong>What determines the lifecycle of a conversation?</strong></summary>

The lifecycle of a conversation depends on the bot, customer interactions, and agent activities. States like "Waiting" and "Follow-Up" are optional and can be applied based on the agent's specific actions or requirements.

</details>

<details>

<summary><strong>Can I skip the "Waiting" or "Follow-Up" states for a ticket?</strong></summary>

Yes, these states are not mandatory in the conversation lifecycle. They are used at the discretion of agents, depending on whether they are waiting for customer input or need additional time for investigation.

</details>

<details>

<summary><strong>What happens if a ticket is marked as "Closed" and the customer sends a message?</strong></summary>

For social channels (WhatsApp, Instagram, Facebook, and Voice), the customer query will create a new conversation, but the previous conversation will remain accessible under "Previous Conversations." For email, if the customer replies to the same thread, the ticket reopens. If they start a new thread, a new ticket is created.

</details>

<details>

<summary><strong>How does the system ensure tickets are not closed prematurely?</strong></summary>

Tickets cannot be manually moved to the "Closed" state to ensure customers can reopen tickets if they feel their queries were not resolved. The transition to "Closed" happens automatically after a configured time of inactivity in the "Resolved" state.

</details>

<details>

<summary><strong>If a ticket is in the "Resolved" state and the customer replies, will it reopen with the same agent?</strong></summary>

The system attempts to assign the ticket to the previous handler first. However, if the agent is unavailable or assignment settings dictate otherwise, the ticket may be reassigned to a different agent.

</details>

<details>

<summary><strong>Can I configure how long a ticket stays in a specific state?</strong></summary>

Yes, you can configure time intervals for state transitions, such as when tickets move from "Resolved" to "Closed" or from "Waiting" back to "Open." These settings can be adjusted in the system configuration.

</details>

<details>

<summary><strong>How can I reopen a "Closed" ticket for social media platforms?</strong></summary>

Closed tickets cannot be reopened directly for social media platforms. Instead, any new customer message creates a new conversation, with the prior context available under "Previous Conversations."

</details>

<details>

<summary><strong>How can I view all conversations associated with a customer?</strong></summary>

You can view previous conversations by navigating to the "Previous Tickets" section in the right panel. Click "See More" to access a list of tickets related to the customer.

</details>

<details>

<summary><strong>What happens if an agent is offline when a ticket's "Waiting" duration ends?</strong></summary>

If the assigned agent is offline at the end of the "Waiting" period, the ticket will be reassigned to another available agent to ensure prompt handling.

</details>

<details>

<summary><strong>Can agents manually move tickets to the "Closed" state?</strong></summary>

No, tickets cannot be manually moved to the "Closed" state to ensure that customers always have the option to reopen a conversation if needed.

</details>

<details>

<summary><strong>What’s the difference between reopening a "Resolved" ticket and replying to a "Closed" ticket?</strong></summary>

For a "Resolved" ticket, a customer’s reply reopens the same ticket, typically assigned to the previous handler (if available). For a "Closed" ticket, a reply in the same thread reopens the ticket for email, while a new query on social channels creates a new conversation.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://limechatai.gitbook.io/limechat-product-guide/helpdesk/tickets/understanding-tickets/defining-ticket-lifecycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.