Agreed request handling time is a period defined in a contract or SLA (Service Level Agreement) within which a service provider must perform a specified action after receiving a customer request. Depending on the terms of the agreement, this may refer to the time required to acknowledge a ticket, begin diagnostics, provide a response, complete a specific stage of work, or resolve an issue.
The metric is used in technical support, IT outsourcing, managed services, equipment maintenance, and other services where the speed of handling customer requests needs to be formally defined.
Agreed request handling time should not automatically be interpreted as the time required to fully resolve an issue. Its exact meaning depends on the SLA and on which events are defined as the start and end points of the measurement period.
How Is Request Handling Time Defined?
The measurement period usually begins after a request has been registered through a communication channel specified in the contract, such as a service desk, customer portal, email, or support hotline. An SLA should define not only the handling time itself but also the rules for measuring it. These may include:
- when the measurement period begins
- the support team’s operating hours
- the priority or category of the incident
- events that may pause the clock
- the action that constitutes fulfillment of the obligation
For example, a critical incident may be handled 24/7, while low-priority requests may only be processed during business hours.
If an SLA specifies a handling time of four business hours, a request submitted on Friday evening does not necessarily have to be processed by the end of the same day. The actual deadline will depend on the service window defined in the agreement.
Request Priority and Handling Time
In IT support, handling times are typically linked to incident severity. Requests may therefore be classified by priority, such as P1, P2, P3, and P4, or Critical, High, Medium, and Low. A typical priority structure may look like this:
- P1 / Critical — failure of a business-critical service or infrastructure; the shortest handling time applies
- P2 / High — serious disruption while some functionality remains available
- P3 / Medium — an issue with limited impact on users or operations
- P4 / Low — a non-critical request, consultation, or planned change
The specific time limits for each category are defined by the service provider and customer. There is no universal handling time for P1 or P2 incidents: these values can vary significantly between service providers and SLAs.
Response Time, Handling Time, and Resolution Time: What Is the Difference?
An SLA may use several metrics related to technical support speed. It is important to distinguish between them because each measures a different stage of the request handling process:
- Response time usually indicates how quickly the provider must acknowledge the request or begin working on it
- Handling time may cover a broader stage of working with the request, although its exact scope depends on the terminology used in the specific agreement
- Resolution time defines how long the provider has to resolve the issue or bring the request to an agreed outcome
For example, an SLA may require work on a critical incident to begin within 15 minutes while allowing significantly more time for full resolution. For complex hardware failures, the resolution time may also depend on spare parts availability and the time required to dispatch an engineer.
What Affects Agreed Request Handling Time?
The required service level depends on the criticality of the IT system and the consequences of downtime. The greater the potential impact of an incident, the stricter the contractual time limits are generally likely to be. Factors considered when defining handling times include:
- support coverage — business hours, an extended service window, or 24/7
- criticality of the supported infrastructure
- availability of remote diagnostics
- whether an on-site engineer is required
- geographic location of the equipment
- availability of replacement components
- whether an external manufacturer or another service provider needs to be involved
Clearly defining these conditions is particularly important in multi-vendor support environments, where resolving a single incident may require the involvement of several organizations.
Why Define Request Handling Time in an SLA?
A formally defined time limit makes support performance measurable. The customer knows how quickly the provider is required to begin handling a request or complete an agreed stage of work, while the service provider has clear criteria for determining whether its obligations have been met.
In practice, handling time alone is not sufficient to evaluate support quality. It is typically considered alongside response time, restoration or resolution time, SLA compliance rates, service availability, and other metrics.
The agreement should also define the calculation methodology unambiguously. A statement such as “handled within two hours” without specifying when the clock starts and stops can be interpreted differently by the parties and make objective SLA performance assessment difficult.