---
title: "Service management"
canonical: "https://docs.cuesystem.com/space/TAM/2812051463/Service%20management"
format: markdown
---
> Macro (children)


> Macro (toc)

This section allows services to be created and managed. These may include, for example:

- Catering orders (e.g. water, coffee, sandwiches)
- Cleaning requests
- Building maintenance requests (e.g. air-conditioning or office furniture repairs)
- AV support requests (e.g. issues with AV or IT equipment)

Proper *Service* configuration allows additional requests to be created for reserved events in CUE Assist, helping to ensure their smooth operation.

> ℹ️ For service management to work correctly, a Connection Agent for API operations must be configured for each resource where services are to be available.


![image-20260821-183444.png](media://06c9b19b-85c1-454c-9705-1945ede37f51)


### Name

This column shows the name of the service category, such as Catering, Cleaning, etc. Each category can contain multiple services, such as water, coffee, or tea, which can be displayed using the + button in the first column. The :expand: button displays the individual services for all service categories in the list.

### Type for unit

This column specifies the service type used on the resource unit. The unit processes and presents the service to users under this type. A maximum of two *Service* types (such as AV Support or Building maintenance), one *Catering* type, and one *Cleaning* type can be configured for resource units. Each Service and Catering type can contain up to 10 service items, while the Cleaning type can contain only one service item.

> ℹ️ Once the service category is saved, its *Type for unit* cannot be changed.

### Resource order in CUE Assist

When selected, the service can be ordered in CUE Assist as a *Service request*, independently of a specific event. This allows users to request the service for a resource as needed, for example when an unexpected maintenance issue occurs.

### Event order in CUE Assist

When selected, the service can be ordered in CUE Assist as an *Order* linked to a specific event, typically in advance. For example, catering such as water or coffee can be ordered for participants when creating a meeting reservation.

### At the earliest 

This field specifies how many minutes before the event starts the service becomes available for ordering. Before this time, the service is not available in the order menu. If no value is specified, the service can be ordered at any time.

> ℹ️ For example, if a reservation is created in CUE Assist three days in advance, but Catering can be ordered only one day before the event, the catering order cannot be placed when the reservation is created. It can be added to the event later, once the configured ordering period begins.

### At the latest

This field specifies how many minutes before the event starts the ordering period closes. If no value is specified, the service can be ordered at any time until the event ends.

### Inactivated

This column indicates whether a service has been deactivated and provides a filter for displaying services by their status. When set to *No*, only active services are displayed. When set to *Yes*, only deactivated services are displayed. Deactivated service items can no longer be added to new requests, but remain included in previously created orders. Hovering over a selected Inactivated checkbox displays the date and time when the service was deactivated. If no filter is applied, both active and deactivated services are displayed.

> ℹ️ Service categories created in CUE Admin cannot be permanently deleted. If a service category is no longer intended for use, it can only be inactivated. Inactivated service categories can be displayed by setting the filter in the Inactivated column to *Yes* and can then be reactivated using the :PLUS: button for the corresponding category.

### Service count

The number in this column indicates the number of service items included in the corresponding service category.

### User count

The number in this column indicates how many users are assigned to the group responsible for the service category. Service requests are routed to these users. For example, the AV Support category can be assigned to technicians who receive an email when an AV support request is submitted.