> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Client health

> Read-only board of every client's open Freshservice tickets, most urgent first: what is waiting on us, past due, late for a first reply, or unassigned, plus technician load.

**Client health** (`/planning/client-health`) shows every client's open Freshservice tickets in one place. Forge keeps a read-only mirror of the Freshservice ticket list, refreshed about every two minutes, and this page summarizes it. Freshservice stays the system of record: make ticket changes there. Nothing on this page writes to Freshservice.

> [!NOTE]
>
> The page needs the **See service desk** permission (`service_desk:read`) granted at platform scope. Without it the page explains what is missing and shows no ticket data. Setting up which Freshservice workspaces are mirrored also needs **Manage knowledge** (`knowledge:manage`).

![Client health (light)](https://mintcdn.com/gloo-b243725a/Oy6fCvRRRIfRoE5z/forge/images/console/planning/client-health-light.png?fit=max\&auto=format\&n=Oy6fCvRRRIfRoE5z\&q=85\&s=4ff114a7321f212305cf00a22b936049)

Client health — Forge Console at `/planning/client-health`

## What you can do

* See each client's open tickets with an attention level (**Needs attention**, **At risk**, **Watch** or **On track**), most urgent first.
* Hover or focus the info icon beside any column name to read what the column counts.
* Sort by any column except **Age mix**, search clients by name, show **Customers only**, or click a summary card to filter the table.
* Expand a client to list its open tickets, oldest first. Each subject links to the ticket in Freshservice.
* Check technician load: open, waiting-on-us and overdue tickets for each assigned technician, with unassigned tickets on their own row.
* With **Manage customers** and **See customers**, expand a client marked "Not linked to a customer" and link it to a Forge customer.
* With **Manage knowledge**, choose **Manage sources** to mirror a Freshservice knowledge source, turn a mirror off, set what custom statuses mean, run the daily reconcile now, or reset where the next sync starts.

## Set up a mirror

A mirror is a switch on an existing Freshservice knowledge source. It uses that source's workspace, account, credential and catalog, so there is nothing else to configure.

**1. Sync the knowledge source**

Create the Freshservice knowledge source in **Knowledge → Synchronized sources** and wait for its first sync. Until then it is not offered as a mirror.

**2. Enable the mirror**

Choose **Manage sources**. Under **Add**, pick the knowledge source, optionally a **History from** date (the backfill reads the last 12 months without one), and choose **Enable**. The first sync starts within a few minutes. If the window holds more than 40,000 tickets, the first sync moves **History from** forward to the earliest day that fits, so the backfill can finish; the card shows the new date and the audit log records the change. The list shows up to 50 knowledge sources and says so when more exist.

A mirror you turned off stays under **Sources**, not **Add**. Until its first pass completes, its card offers **History from** with **Enable from this date**, which turns it back on and restarts the backfill from that date. **Enable** alone resumes where it stopped.

**3. Set status meanings**

Open the mirror's **Status meanings**, choose a meaning for each custom status, and save. Only the rows you changed are sent.

Choosing **Disable** stops the mirror, even when its knowledge source has been removed. Its tickets leave the board, and enabling it again resumes where it stopped.

## Read the columns

| Column | What it counts |
| - | - |
| **Client** | The customer these tickets belong to. Gray rows are Freshservice departments not yet linked to a Forge customer. |
| **Open** | Tickets not yet resolved or closed. |
| **Waiting on us** | Open tickets where the next step is ours, not the client's or a third party's. |
| **Past due** | Open tickets whose resolution due time has passed. |
| **Late first reply** | Tickets past their first-response due time with no reply from us yet. |
| **Unassigned** | Open tickets with no technician assigned. |
| **Age mix** | How long open tickets have been open: under a week, 1–4 weeks, 1–3 months, 3–12 months and over a year. Hover the bar for the counts. |
| **Oldest** | How long ago the oldest open ticket was created. Hover for the exact date. |
| **Quietest** | The longest any ticket waiting on us has gone without an update. A dash means nothing is waiting on us. |

Ages read in the largest whole unit that fits: hours, days under two weeks, weeks under 60 days, months under a year, then years (for example "3 wk", "7 mo", "4 yr").

## Attention levels

Each client linked to a customer gets one level, from the first rule that matches. Hover or focus the level to see which rule set it. "Quiet time" is how long the least recently updated ticket waiting on us has gone without an update.

* **Needs attention:** 10 or more late first replies, or at least 5 open tickets with 45% or more of them past due.
* **At risk:** any late first reply, or at least 5 open tickets with 25% or more past due, or 30 days or more of quiet time.
* **Watch:** any past-due ticket, or 7 days or more of quiet time.
* **On track:** none of the above.

The level also colors the row's left edge: red, amber, purple or green.

## Sort, filter and search

* **Order.** By default the most urgent clients come first, then the clients with the most open tickets, then by name. Click a column name to sort by it; click again to reverse. **Most urgent first** returns to the default order.
* **Linked and unlinked rows.** Clients linked to a Forge customer always come first, on alternating stripes. Freshservice departments not yet linked to a customer follow on gray rows, marked "Not linked to a customer". Tickets with no department appear under **No department**.
* **Summary cards.** **Open**, **Waiting on us** and **Unassigned** are totals. Click **Past due**, **Late first reply** or **Needs attention (clients)** to show only the clients they count; click the same card again to show every client.
* **Search and Customers only.** The search box matches client names. **Customers only** hides the unlinked departments. The count beside them shows how many clients are listed.

## How tickets are counted

* **Client.** A ticket belongs to the Forge customer its Freshservice department maps to. A department with no customer mapping appears under its own name.
* **Waiting on us / on the client.** Each Freshservice status has a meaning: waiting on us, waiting on the client, waiting on a third party, resolved, or closed. Standard statuses use default meanings; an operator sets the meaning of custom statuses.

## Map a client to a customer

A client marked "Not linked to a customer" is a Freshservice department that no Forge customer is
mapped to yet. With **Manage customers** and **See customers**:

**1. Expand the client**

Expand its row on the board. **Customer** sits above its open tickets.

**2. Find the customer**

Type part of the customer's name and pick it from the active organization customers that match.

**3. Save**

Choose **Map to** the customer. If the customer has no organization yet, Forge creates it first. The client's tickets move to the customer as you save, so its row leaves the unlinked clients at once; a client with a very large ticket history finishes moving within moments.

The mapping applies to every Freshservice department of that name, across mirrors and signed
Freshservice webhooks from a company of that name (a name longer than 120 characters matches on the
mirror only). Mapping the same department again replaces its customer.

## Key state to watch

* **Mirror status banner.** For each mirror it names the knowledge source and shows, in plain words with the error code in small text: whether the first full pass is still running, when it last synced, any sync or daily-reconcile error, when a lane that failed will retry, the reconcile phase, departments the catalog has no name for yet, and statuses that still use the default meaning. With no mirror set up it says "No Freshservice source is mirrored yet".
* **Truncation.** The board reads at most 3,000 open tickets, split evenly across mirrors, and a client's drill-in lists at most 500. The page says so when it hits either limit.
* **Departments not in the catalog yet.** A ticket whose department the knowledge source has no name for keeps its client. A new one shows under "Department `<id>` (not in catalog yet)" until the knowledge source syncs again.
* **Lag.** Changes made in Freshservice appear after the next sync, typically within about two minutes. Deleted and spam tickets, and tickets moved to another Freshservice workspace, drop off the board after the daily reconcile.

## Related surfaces

> [card] [Planning overview](https://docs.gloo.com/forge/console/planning/index.md)
>
> The other Planning pages, including the customer directory.

> [card] [Permissions reference](https://docs.gloo.com/forge/reference/permissions)
>
> What **See service desk** and **Manage knowledge** grant and which roles include them.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.