Operational Hours  

Configure and manage operational hours for the Sites, Support Groups, and Regions configured in your application. Operational hours are used to calculate request completion time, SLA, or time spent by technicians on the requests. Operational hours enable you to configure critical automations during business hours.

Use case: For instance, you can set region-specific working hours (e.g., 9–6 local time) for global support teams in New York, London, and Singapore to ensure accurate SLAs and technician availability.

 

To configure operational hours,

Note: Operational hours are applied in the following order: Group > Site > Region. If none are available, base operational hours will be used. Base operational hours refer to the fallback default working hours. For timezone selection, if an operational hour is configured for a group, the timezone of the site associated with that group will be used

 

 

 

 List View Operations 

From the list view, you can perform the following actions

 

Note: Use Special Operational Hours for temporary schedule changes or variations specific to certain dates. If any operational hour is set as default, then the previous default operational hour will be deleted.

 

 

 

Special Operational Hours

Use Special Operational Hours to configure temporary schedule adjustments for special events or holidays.

Use case: For instance, you can use special operational hours to temporarily reduce or disable support hours during year-end change freeze (e.g., Dec 25–31) to reflect limited staffing and prevent SLA breaches.

To configure special operational hours,

 

Note: You cannot associate multiple special operational hours configured with overlapping time periods to one operational hour.

 

List View Operations

From the list view, you can perform the following actions: