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

# Review helpdesk improvements

> Use repeated ticket evidence to find blockers and opportunities worth fixing.

**Improvements** surfaces patterns observed across helpdesk work, such as a missing procedure, weak system access, repeated customer dependencies, or an operational step that consistently needs a person.

It is an evidence and prioritization surface. An improvement does not silently change a ticket plan, update a runbook, or enable automation.

## Review an improvement

1. Read the summarized pattern.
2. Open the supporting tickets and confirm they represent the same underlying issue.
3. Identify the owner of the process, system, account relationship, or guidance.
4. Decide whether to act, gather more evidence, or dismiss the item.
5. Record the change in the system that owns it.

## Common responses

| Pattern                      | Possible response                                                        |
| ---------------------------- | ------------------------------------------------------------------------ |
| Missing or unclear procedure | Create or revise a runbook or skill.                                     |
| Tool repeatedly unavailable  | Check connection health, account mapping, Availability, and role access. |
| Account-specific exception   | Add an account-level runbook customization or context.                   |
| Customer dependency          | Improve the communication template, approval path, or documented owner.  |
| Wrong ticket classification  | Review triage mappings and examples.                                     |
| Repeated handoff             | Improve the stop condition, evidence collection, or escalation path.     |

## Close the loop

After changing the process, monitor new tickets to see whether the pattern declines and whether a new failure mode appears. Use [Insights](/insights/overview) and run outcomes alongside qualitative technician feedback.

<Tip>
  Prioritize improvements that remove friction from many tickets without weakening safety. A smaller, observable procedure change is usually easier to validate than a broad prompt rewrite.
</Tip>