# Automation Rules
***
## Event
You can choose from a variety of specific update events that will trigger your automation rule. Types of Events:
* **Conversation Created:** This event occurs when a new ticket is generated.
* **Conversation Opened:** Triggered when the status of a ticket changes to "open."
* **Conversation Resolved:** Activated when a ticket's status is updated to "resolved."
* **Message Created:** This event is initiated when a new message is added to the conversation.
* **Assignee Changed:** Occurs when the assigned agent for a ticket is modified.
* **Team Changed:** Triggered when the team handling a ticket is altered.
* **Conversation Closed:** Activated upon closing a conversation or ticket.
***
## Conditions
Set conditions that must be met in order for the automation rule to be applied. Operators such as `"equal to"`, `"not equal to"` are used on the following instances to create conditions:
* **Inbox:** Set conditions based on the inbox where the conversation resides.
* **Status:** Define conditions regarding the status of the conversation (e.g., open, resolved).
* **Email Subject:** Apply conditions based on specific keywords or phrases in the email subject.
* **Assignee:** Set conditions based on the assigned agent for the ticket.
* **Team:** Define conditions based on the team responsible for handling the ticket.
{% hint style="info" %}
The conditions are specific to the events, some of these conditions may or may not be applicable for certain events.
{% endhint %}
***
## Actions
Define the actions that should be taken when the conditions are met. Types of Actions:
* **Assign a Team:** Automatically assign the conversation to a specific team.
* **Assign an Agent:** Directly assign the conversation to a particular agent.
* **Assign a Label:** Tag the conversation with a specific label for easy identification.
* **Send an Email to the Team:** Trigger an email notification to the designated team.
* **Mute Conversation:** Silence notifications for a specific conversation.
* **Resolve Conversation:** Automatically mark the conversation as resolved.
* **Send a Message:** Initiate an automated message to the customer or team.
* **Create a Ticket:** Integrate with third-party CRM tools (such as Freshdesk or Kapture) to automatically generate a ticket for further management.
***
**Combinations of events, conditions, and actions can be used to create rules that automate a large number of tasks and reduce the need for human intervention.**
This feature will provide a more efficient and customized experience by automating certain tasks and actions, you can save time and reduce the risk of human error. This ensures that your team can focus on the tasks that require their expertise, leading to a more streamlined and effective workflow.
***
## Examples:
We want to add an automation rule where all the tickets coming in from Instagram Channel are assigned only to the Instagram agents team.
{% stepper %}
{% step %}
**Step 1:** Click on “**Add Automation Rule**” and you should be able to see a pop up
{% endstep %}
{% step %}
**Step 2:** After filling **`“`Rule Name`”`** and `“`**Description**`”` select the appropriate “**Event**” from the list of events.
{% endstep %}
{% step %}
**Step 3:** Set Conditions that must be met in order for the automation rule to be applied. In this case, the condition defines “When inbox is equal to Instagram”
{% endstep %}
{% step %}
**Step 4:** Add what should be the next step when the above conditions are met by selecting the appropriate value from the list of Actions .
{% endstep %}
{% endstepper %}
Here, the action is the following: Assign that ticket/conversation to the IG Team.
***
To know how to create an automation rule, check this video:
{% embed url="" %}
***
## FAQ'S
What types of events can trigger an automation rule?
Automation rules are triggered by the following events:
* **Conversation Created** – When a new ticket is generated.
* **Conversation Opened** – When a ticket status changes to "open."
* **Conversation Resolved** – When a ticket is marked as "resolved."
* **Message Created** – When a new message is added to the conversation.
* **Assignee Changed** – When a ticket is reassigned to a different agent.
* **Team Changed** – When a ticket is transferred to another team.
* **Conversation Closed** – When a conversation or ticket is closed
What conditions can be set in automation rules?
Conditions determine when a rule applies. Some examples include:
* **Inbox** – Apply rules based on the inbox (e.g., Instagram, WhatsApp, etc.).
* **Status** – Define conditions based on ticket status (e.g., open, resolved).
* **Email Subject** – Use keywords in the subject line to trigger actions.
* **Assignee** – Apply rules based on the assigned agent.
* **Team** – Define rules based on the team handling the ticket.
Can I create multiple conditions and actions in a single rule?
Yes, automation rules allow **combining multiple events, conditions, and actions** to build powerful workflows.
How do automation rules improve efficiency?
* **Saves time** by reducing manual ticket assignments.
* **Minimizes errors** by ensuring tickets go to the right team or agent.
* **Improves response times** by automating repetitive tasks.
* **Enhances organization** by categorizing and tagging conversations effectively.
---
# 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/settings/automation-rules.md?ask=
```
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.