# Agent and Ticket Analytics FAQ's

<details>

<summary><strong>How are ticket and agent metrics affected when all agents are offline?</strong></summary>

Incoming tickets stay unassigned in the queue until an agent or admin assigns them. While in the queue, **Queue Time (QT) is tracked**, but **Agent Metrics are not recorded** since no agent is assigned.

If the ticket remains in the queue during business hours, Queue Time is tracked separately but does not impact **Agent FRT, WT, or RT**. If outside business hours, timers pause and resume when business hours start.

</details>

<details>

<summary><strong>What happens when at least one agent is online?</strong></summary>

Tickets are immediately assigned to an agent when they arrive, and all relevant metrics start tracking.

</details>

<details>

<summary><strong>How is Waiting Time (WT) calculated?</strong></summary>

* **Agent WT** measures the time between a customer’s message and an agent’s reply.
* **Ticket WT** is the total waiting time, including periods in "Waiting" or "Follow-up" states.
* When a ticket is unassigned (in queue), **Agent WT is not tracked**, but **Ticket WT continues** if waiting for action.

</details>

<details>

<summary><strong>When does ‘Handled Time’ start counting?</strong></summary>

Handled Time starts when a ticket is assigned, reassigned, or transferred. Each time a ticket moves to a new agent, the Handled Time counter resets.

</details>

<details>

<summary><strong>How is agent inactivity handled, what happens to the metrics if there is no activity on the ticket?</strong></summary>

If an agent does not act on an assigned ticket, **Agent FRT applies** if no response is sent, and **Agent RT applies** if unresolved. If the ticket is still in the queue, **Agent Metrics are not tracked**, but **Ticket RT and WT continue tracking**.

</details>

<details>

<summary><strong>Do Business Hours impact metric calculations?</strong></summary>

Yes. If a ticket arrives outside business hours:

* **Agent FRT and Ticket FRT pause** until business hours resume.
* **Agent WT and Ticket WT pause** for fairness in response tracking.
* **Ticket RT continues tracking** as it measures total resolution time.

SLAs only consider business hours, ensuring no penalties for delays outside working hours.

</details>

<details>

<summary><strong>Why can Ticket Waiting Time (WT) be greater than Ticket Resolution Time (RT)?</strong></summary>

Ticket RT applies only to resolved tickets, while Ticket WT includes unresolved ones. If a ticket waits a long time but is resolved quickly, WT may be higher than RT. If unresolved, WT keeps increasing, whereas RT stops tracking.

</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/analytics/agent-and-ticket-analytics-faqs.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.