Language

Swift Support brings tickets, SLAs, assets, changes, contracts, projects and an AI that understands your data into a single ITSM platform, on your own server or in the cloud.

Contact
Business hours

Monday to Friday, 9:00 a.m. to 6:00 p.m. (Mexico City time)

Service desk

Turn the most common requests into standardized services. Your users choose what they need —a new laptop, access to a system, a software install— and Swift Support creates a ticket with the right category, priority and SLA.

Service catalog with laptop request, system access, password reset, software and printers
Service catalog

What it is and how it helps

Much of a service desk’s work is not failures but predictable requests: equipment for a new hire, access to the ERP or CRM, a corporate password reset, installing an application or fixing a printer. The service catalog organizes them so they are always requested the same way.

Each catalog service has a name, a user-facing description, a category, an associated SLA, a default priority and a status (active or inactive). You can feature the most requested services so they show up first in the portal, and see how many tickets each one has generated.

Because every request creates a ticket, the service enters the same assignment, SLA and CSAT flow as the rest of the operation. With custom fields you can capture the specific information each service needs, and with approvals you can ask for authorization when the service requires it.

Key capabilities

Standardized services

Name, description, category and priority defined once and applied to every request.

Featured services

Highlight the most requested services so users find them instantly.

SLA per service

Associate each service with the service level that matches its complexity.

Every request is a ticket

It enters the same assignment, tracking and satisfaction flow as the rest of the desk.

Demand per service

See how many tickets each service has generated to plan resources.

Turn on or off

Publish or withdraw services from the portal without losing their history.

Custom forms

Add your own fields to capture the data each service requires.

How it works

  1. 01

    Design the catalog

    Identify recurring requests and create one service for each, with its category, priority and SLA.

  2. 02

    Publish it on the portal

    Active services appear in the self-service portal; featured ones first.

  3. 03

    The user requests

    They choose the service, fill in the details and submit; an automatically classified ticket is created.

  4. 04

    Handle and measure

    The ticket follows its normal flow and the catalog shows the accumulated demand for each service.

Why it matters

Predictable requests, predictable service

The catalog removes ambiguity: users know what they can ask for and the team receives complete, well-classified requests. Over time, demand per service becomes valuable information for sizing staff, inventory and budget.

  • Consistent requests
  • Automatic classification
  • The right SLA for each service
  • Visibility of demand
  • Better user experience
  • A foundation for automation
Catalog access from the self-service portal menu
FAQ

Questions about Service catalog

If your question is not here, write to us and we will gladly answer it or show you the module in a demo.

  • Yes. Active services appear under Catalog in the portal menu, and those marked as featured are shown first.
  • A ticket is created with the service’s category, priority and SLA, and it enters the normal assignment and handling flow.
  • Yes, using custom fields for services, configurable in Settings.

Ready to see Swift Support with your own processes?

Book a guided demo: we review how your team works today and show you the modules that will add the most value.