Appearance
Service Catalog
The Service Catalog automatically classifies your resolved tickets into a structured hierarchy of categories, services, and tasks — giving you a clear, data-driven view of what your team actually delivers.
Overview
Instead of manually defining your service offerings, the Service Catalog builds itself from your real ticket history. As tickets are resolved, they are automatically organized into categories, services, and tasks. New services and tasks emerge as your ticket data grows — no manual creation required.
Accessing the Service Catalog
Navigate to Advisor and click into the Service Catalog card, or go directly to the Service Catalog page.
What You See
The top of the page shows summary metrics:
| Metric | Description |
|---|---|
| Tickets | Total resolved tickets classified into the catalog |
| Hours | Total time logged across all classified tickets |
| Services | Number of unique service groups discovered |
| Task Types | Number of individual task types discovered |
Below the summary, the catalog displays a hierarchical tree. Expand a category to see its services, and expand a service to see individual tasks with ticket counts, total hours, and average time per ticket.
Click into a task to view the individual resolved tickets that were classified under it.
Scope Management
Each task can be labeled to describe how it fits into your service delivery model — for example, whether it is included in standard agreements, has limitations, or is billed separately. Tasks start unlabeled until you classify them.
You can edit scope labels individually or select multiple tasks for bulk editing. Optionally add scope notes to document your specific terms.
Organizing the Catalog
- Drag and drop tasks between services, or services between categories, to reorganize the structure.
- Company filtering lets you view the catalog for a specific client or across your entire organization.
How It Works
The catalog is populated automatically from your resolved tickets. No manual setup is needed — the catalog starts building as soon as you have resolved tickets flowing through Junto.