> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/build/process-packs.md).

# Process packs: ready-made metrics and a board for month-end close, inventory, customer service and hiring

When a source is recognised as a month-end close, an inventory and supply chain process, service tickets or hiring and onboarding, add the metrics that process is usually watched by, and a draft board, in one click and in your own step names. On the employee portal, a case that is a ServiceNow or Zendesk ticket shows the ticket’s status changes and public replies beside it.
## The packs

- Month-end close: days to close, late closes, time to reconcile, reconciliations redone, closes in progress.
- Inventory and supply chain: replenishment lead time, late replenishments, days in transit, replenishments in progress.
- Customer service (service tickets): time to first response, time to resolve, resolved late, reopened, open tickets.
- Hiring and onboarding: time to offer, offer acceptance, offer to start, days to set up accounts, candidates in progress.
- A metric whose steps the source does not have is left out. Metrics are broken down by the first usual column the source has, such as company, warehouse, priority or department.

## Apply a pack

1. Open the process page of a cases table. When a source’s kind of process is one of the four above, its Metrics section shows the pack and what it adds. Only the organization’s owners and admins see and apply it.
2. Click Apply. Duaer adds the metrics the source does not have yet, unpublished, and a draft board named “pack · source” with up to 4 KPIs, a line chart, a bar chart and a cases table.
3. Check, change or delete the metrics in the metrics library and publish those you want; adjust the board and publish it to the employee portal.
4. Applying again adds only what is missing. Applying is in the audit log, with the pack and counts only.

## The ticket beside a case

- A ServiceNow source’s case is its ticket; any other case is a Zendesk ticket when its link or one of its columns is a Zendesk ticket address.
- When the case is opened on the employee portal, Duaer reads the ticket live with the organization’s ServiceNow credential or the Zendesk account connected for knowledge, and shows its status changes and public replies, the latest 50 at most, with a link to the ticket.
- Internal notes (ServiceNow work notes, Zendesk internal notes) are never read or shown. Duaer does not store the ticket.
- Only people who see the case see its ticket; a link to a Zendesk account the organization has not connected shows nothing.
## Questions

### My source is not recognised as one of these kinds. Can I still use a pack?

Yes. Choose the kind of process in the source’s mapping; its pack then shows on the process page.

### Do the pack’s metrics show on the employee portal at once?

No. The metrics and the board are drafts until you publish the metrics in the metrics library and the board on the process page.

### Do I need another connection for the ticket timeline?

No. ServiceNow uses the source’s credential, Zendesk the account already connected for knowledge.

## Related

- [See the process in your data and generate workflows in Duaer](https://doc.duaer.com/build/process.md)
- [Add a process source in Duaer](https://doc.duaer.com/build/process-sources.md)
- [Process boards: built once by an admin, each employee sees their own figures](https://doc.duaer.com/build/process-boards.md)
- [Track numbers in Duaer with one metrics table](https://doc.duaer.com/build/duaer-metrics.md)
- [Knowledge sources you can connect to Duaer](https://doc.duaer.com/knowledge/sources.md)