## TL;DR
Define FCR as tickets resolved by the first assigned group without reassignment or reopen within 7 days, then build the report on assignment history and reopen counts. The pitfalls are reassignments that do not count as failure and reopens that do; get the definition agreed before building.

## The error
```text
(Metrics task; no error.)
```

## Steps
1. Agree the definition with stakeholders: resolved by first touch group, no reassignment, no reopen within N days. Expected: documented. FCR arguments are always about the definition.
2. In ServiceNow, report on incidents resolved where assignment group never changed and the ticket was not reopened. Expected: report built. Use the assignment history, not just the current group.
3. Exclude appropriately: tickets auto-routed then correctly handled count as FCR for the final group; define this. Expected: exclusions documented.
4. Track reopens: a ticket reopened within 7 days was not really resolved. Expected: reopen rate alongside FCR. FCR without reopen tracking lies.
5. Review monthly by category and group. Expected: reported. Low FCR in one category points at training or KB gaps, not agent effort.

## When to use
- Implementing FCR measurement
- Diagnosing resolution quality issues

## When not to use
- SLA compliance reporting
- Individual performance punishment (FCR is a team metric)

## Compatibility
- ServiceNow ITSM reporting; concepts transfer to any ITSM

## Variants
### First-contact resolution vs first-call resolution
Phone-first orgs measure calls; chat/ticket orgs measure touches. Pick one.
### Including self-service
Deflected tickets can count separately; do not mix them into agent FCR.

## Why it happens
FCR predicts customer satisfaction better than speed metrics. But it is definition-sensitive, so the definition must precede the dashboard.

## Edge cases
- Never use FCR alone to judge agents; it punishes agents who take the hard tickets.
- Reassignment for correct routing is not an FCR failure of the first agent; define it as such.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Q8uzqSdoGbV2yrMw15qo7Q