# Understanding Ticket Assignment

***

## Assignment Algorithms

### 1. Round Robin Assignment:

Round Robin assigns tickets to agents in a circular manner, ensuring each agent receives an equal number of tickets over time.

Example: If there are three agents (A, B, C) and five tickets:

* Ticket 1 goes to Agent A
* Ticket 2 goes to Agent B
* Ticket 3 goes to Agent C
* Ticket 4 goes to Agent A
* Ticket 5 goes to Agent B

**Benefits of Round Robin:**

* **Fair Workload Distribution:** Ensures each agent receives an equal share of tickets.
* **Predictable Assignment:** Agents can anticipate their workload more easily.
* **Simplicity:** Easy to implement and understand, without complex decision-making processes.

***

### 2. Load Balanced Assignment:

Load Balancing assigns tickets based on the current workload of each agent, ensuring no single agent is overwhelmed.

**Example:** If there are three agents (A, B, C) with different workloads and five tickets:

* Agent A has 2 tickets, Agent B has 5, and Agent C has 7.
* Ticket 1 goes to Agent A (3 total)
* Ticket 2 goes to Agent A (4 total)
* Ticket 3 goes to Agent A (5 total) \[A: 5, B: 5, C: 7]
* Ticket 4 goes to Agent A (6 total) \[A: 6, B: 5, C: 7]
* Ticket 5 goes to Agent B (6 total) \[A: 6, B: 6, C: 7]
* Ticket 6 goes to Agent A (7 total) \[A: 7, B: 6, C: 7]
* Ticket 7 goes to Agent B (7 total) \[A: 7, B: 7, C: 7]
* Ticket 8 goes to Agent A (7 total) \[A: 8, B: 7, C: 7]
* Ticket 9 goes to Agent B (8 total) \[A: 8, B: 8, C: 7]
* Ticket 10 goes to Agent C (8 total) \[A: 8, B: 8, C: 8]

### **Benefits of Load Balancing:**

* **Balanced Workload:** Distributes tickets based on current load, preventing agent overload.
* **Efficiency:** Ensures agents are utilized to their fullest capacity.
* **Adaptability:** Adjusts to changing workloads and agent availability in real-time.

***

## Round Robin vs Load Balancing

| Feature       | Round Robin                               | Load Balancing                       |
| ------------- | ----------------------------------------- | ------------------------------------ |
| **Pros**      | Fair workload distribution                | Balanced workload                    |
|               | Predictable assignment                    | Efficient use of agent capacity      |
|               | Simple to understand and implement        | Adapts to real-time changes          |
| **Use Cases** | Agents have similar skills                | Agents have varying workloads        |
|               | Fairness and predictability are important | Preventing agent overload is crucial |

### 3. Centralized Assignment Management Page

This central page allows for easier management and oversight of ticket assignment settings.

However, ***users can still define assignment logics at the inbox level***, providing the flexibility to tailor assignment methods to specific needs.

<figure><img src="/files/De6wGaNTxuvoMCmgKfry" alt="" width="563"><figcaption></figcaption></figure>

### **Centralized Management Benefits:**

* **Simplified Configuration:** Manage all assignment settings from one place.
* **Flexibility:** Customize assignment logic for each inbox while maintaining overall control.
* **Efficiency:** Easily switch between Round Robin and Load Balancing as needed.

We believe these updates will enhance your ticket management experience by providing fairer workload distribution and more efficient ticket handling.

***

## Defining the Assignment Logic

{% stepper %}
{% step %}
Navigate to the settings section in the CRM.
{% endstep %}

{% step %}
Open "Ticket Assignment."
{% endstep %}

{% step %}
Here you will find the option to define the assignment process (Automatic vs. Manual) for each inbox.
{% endstep %}

{% step %}
Under Automatic Assignment logic, the user can choose the algorithm as per their use case: Round Robin or Load Balancing.
{% endstep %}

{% step %}
Finally, the user also has the option to define whether automatic assignment should take place only when agents are online or even if they are offline.
{% endstep %}
{% endstepper %}

***

Refer to the following link for video demo:

{% embed url="<https://drive.google.com/file/d/1rZAGoNcMCvHmKsmi7SpSEVx052xwOzM_/view?usp=sharing>" %}
How to assign tickets
{% endembed %}

***

### How to select the assignment logic as per the use case?

<table data-header-hidden data-full-width="true"><thead><tr><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Use Case</strong></td><td><strong>Agent Type</strong></td><td><strong>Assignment Logic</strong></td><td><strong>Configuration</strong></td></tr><tr><td>Tickets are assigned to agents who are <strong>online</strong> in a cyclic order (without considering the current status of their concurrency status). Assignment stops if the agent is <strong>offline</strong> or their <strong>concurrency</strong> is <strong>filled</strong>.</td><td>Support Agent</td><td>Round Robin</td><td>Online Only</td></tr><tr><td>Tickets are assigned to agents in a cyclic order <strong>(without considering the current status of their concurrency status)</strong> regardless of their online or offline status and the</td><td>Support Agent</td><td>Round Robin</td><td>Online and Offline</td></tr><tr><td>Tickets are assigned to agents such that the agent with the lesser number of tickets is assigned new tickets. The agent with the greater number of tickets is not assigned new tickets until the other agents have the same number of tickets.</td><td>Support Agent</td><td>Load Balanced</td><td>Online Only</td></tr><tr><td>Tickets are assigned to agents such that the agent with the lesser number of tickets is assigned new tickets regardless of their online or offline status.</td><td>Support Agent</td><td>Load Balanced</td><td>Online and Offline</td></tr><tr><td>Agents are supposed to keep tickets in an open state for a longer duration to increase the probability of conversion. Tickets are assigned in a cyclic manner without considering the number of assigned tickets.</td><td>Sales Agent</td><td>Round Robin</td><td>Online Only</td></tr><tr><td>Agents keep tickets in an open state for longer durations to increase the probability of conversion. Tickets are assigned in a cyclic manner regardless of the number of assigned tickets.</td><td>Sales Agent</td><td>Round Robin</td><td>Online and Offline</td></tr><tr><td>Technical issues require immediate attention. Tickets are assigned to the agent with the least number of tickets currently, ensuring quicker resolution.</td><td>Technical Support Agent</td><td>Load Balanced</td><td>Online Only</td></tr><tr><td>Technical issues need to be addressed promptly. Tickets are assigned to the agent with the least number of tickets, regardless of their online status.</td><td>Technical Support Agent</td><td>Load Balanced</td><td>Online and Offline</td></tr></tbody></table>

### See this video to know more about managing ticket assignment

{% embed url="<https://drive.google.com/file/d/1ppRnYpL73a88_R2snFPFxjUPg9oP92tL/view?usp=sharing>" %}

***

## FAQ's

<details>

<summary><strong>What should I consider before choosing between Round Robin and Load Balancing for my team?</strong></summary>

Consider factors like team structure, ticket volume, urgency, and the skills of agents. Use Round Robin if the team has equal capacity and skills, and fairness is the priority. Use Load Balancing if agents have varying workloads or skills, or if resolving tickets efficiently is critical.

</details>

<details>

<summary><strong>What is the difference between Round Robin and Load Balancing algorithms?</strong></summary>

Round Robin assigns tickets to agents in a cyclic order, ensuring fairness and predictability. Load Balancing assigns tickets based on the agent's current workload, ensuring efficiency and preventing overload.

</details>

<details>

<summary><strong>How does Round Robin handle concurrency limits if an agent is already managing too many tickets?</strong></summary>

Round Robin doesn’t consider an agent’s current workload. It assigns tickets in a cyclic order, which might result in overloading agents if concurrency settings aren’t monitored.

</details>

<details>

<summary><strong>What happens when all agents in a Load Balancing configuration have equal workloads?</strong></summary>

If all agents have equal workloads, the algorithm typically defaults to assigning tickets in a cyclic order, starting from the next available agent, ensuring no downtime in ticket handling.

</details>

<details>

<summary><strong>What if a ticket needs immediate escalation and the assigned agent is unavailable in a Load Balancing setup?</strong></summary>

If the assigned agent is unavailable, you can create an escalation workflow in the system to reassign the ticket to the next agent with the least workload or manually intervene to handle the escalation.

</details>

<details>

<summary><strong>How does the "Online and Offline" option in Load Balancing impact agent workload distribution?</strong></summary>

When using "Online and Offline," tickets can be assigned to offline agents, potentially leading to a backlog when they return online. This configuration is best used when immediate assignment is critical, regardless of agent availability.

</details>

<details>

<summary><strong>How can I prevent overloading certain agents in a Round Robin setup?</strong></summary>

Use concurrency settings to limit the number of tickets each agent can handle. Alternatively, consider switching to Load Balancing, which dynamically adjusts assignments based on current workloads.

</details>

<details>

<summary><strong>Can I customize how tickets are balanced in Load Balancing?</strong></summary>

Yes, you can pair Load Balancing with additional automation rules to prioritize tickets based on agent expertise, ticket urgency, or SLA requirements, providing a tailored workload distribution.

</details>

<details>

<summary><strong>Can agents manually reassign tickets assigned by Load Balancing or Round Robin?</strong></summary>

Yes, agents or admins can manually reassign tickets. However, frequent manual intervention might indicate that the selected algorithm or configuration needs refinement.

</details>

<details>

<summary><strong>What metrics can I track to evaluate the effectiveness of my assignment algorithm?</strong></summary>

Track metrics like agent workload distribution, ticket resolution time, agent response time, and SLA compliance. These will indicate whether the chosen algorithm is meeting your team's objectives.

</details>

<details>

<summary><strong>What happens if I switch from Round Robin to Load Balancing mid-operation?</strong></summary>

Ongoing tickets remain with their assigned agents. The new algorithm will apply to all future assignments, ensuring a seamless transition without disrupting existing workflows.

</details>

<details>

<summary><strong>Can I customize assignment settings for different inboxes?</strong></summary>

Yes, assignment logic can be customized at the inbox level, allowing you to tailor settings for each team or process while managing all configurations centrally.

</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-ticket-assignment.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.