> For the complete documentation index, see [llms.txt](https://docs.klink.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klink.cloud/how-to-use/call/inbound-call-handling/inbound-call-queue-groups.md).

# Inbound Call Queue Groups

### 📞 Inbound Call Queue Groups

**Overview:**\
Inbound Call Queue Groups allow you to route incoming calls to different groups of agents based on business needs. This helps manage call distribution effectively, ensuring that the right team handles the right type of call.

***

#### 🔧 What is a Queue Group?

A **Queue Group** is a collection of agents who are assigned to handle a specific type of incoming call. Each group can have its own **ring strategy**, business hours, and agent members.

***

#### 🧩 Why Use Multiple Queue Groups?

Using multiple queue groups helps:

* Separate teams by department (e.g., Sales, Support, Billing)
* Prioritize VIP customers to a special queue
* Route calls based on language preference, location, or service type

***

#### ✅ Example Setup:

Let’s say your business has two teams: **Sales Team** and **Support Team**.

You can create two separate queue groups:

1. **Sales Queue Group**
   * Ring Strategy: Ring All
   * Agents: Alice, Bob, Carol
   * Used for: Inquiries from new customers or product demos
2. **Support Queue Group**
   * Ring Strategy: Fewest Calls
   * Agents: David, Emma, Frank
   * Used for: Existing customer support requests

When a customer calls:

* If the caller presses **1 for Sales**, they are routed to the **Sales Queue Group**
* If the caller presses **2 for Support**, they are routed to the **Support Queue Group**

**Call Queue Ring Strategies – How Incoming Calls Are Assigned to Agents:**

When a call enters the queue, the system uses a “ring strategy” to decide which agent gets the call. Here are the available options:

* **Ring All**: Rings all available agents at the same time. Whoever picks up first handles the call.
* **Least Recent**: Sends the call to the agent who hasn’t received a call in the longest time.
* **Fewest Calls**: Sends the call to the agent who has handled the fewest number of calls so far.
* **Random**: Rings agents in a completely random order.
* **Round Robin (Rrmemory)**: The system remembers the last agent it tried and rings the next agent in line.
* **Linear**: Always rings agents in a fixed order, starting from the top of the list every time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.klink.cloud/how-to-use/call/inbound-call-handling/inbound-call-queue-groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.