This SLA is written according to customer's perspective.
Service Level is defined as the number of contacts handled within a defined acceptable period of time as a percentage of total contacts offered. If your SLA target is 80% in 20 seconds: SLA = (Contacts handled <20 seconds)/(Contacts Handled)
You can measure the customer's level of satisfaction based on the feedback that he will provide.
Where one party delivers services to another, it is a good idea to have some kind of agreement setting out the basis on which the service is provided. Such agreements would normally contain, among other things, a description of what is to be provided, the key performance indicators, the way the service is to be charged for (where relevant) and the responsibilities of each of the parties. In ITIL SLM, the agreements between the internal IT service provider and the business customers that it supports are known as Service Level Agreements (SLAs) and it is through SLAs that SLM manages the relationship between itself and its customers. It would be hard to find IT services provided by IT giants like TCS, Infosys, Wipro etc., where they do not have any accepted/agreed upon SLAs with their customers. In order to be effective, the SLA must be a written document signed off by all parties affected by it. SLAs are important so they will rarely be agreed without negotiation between the IT service provider and the customer, beginning with a Statement of Intent that sets out the terms, conditions and targets to be agreed. It has to be in a language that both sides will understand, and this means in the language of the customer and not the technical language or jargon of the provider. The SLA defines (in language that has meaning to the customer) precisely what is to be delivered and when and where it is to be delivered. It also defines the standard of quality to be delivered, usually in terms of performance and availability. It will define the responsibilities of both the service provider and the customer. This is important. It makes little sense for a service provider to commit to deliver a service without making it clear what is expected of the customer. The SLA will include contact details, what should happen if something goes wrong, the way any disputes should be handled, any provisions for redress, the mechanism for getting the SLA changed if necessary and the period over which the agreement will stand unless otherwise changed by agreement. If the service is to be charged for, then the way charges are to be determined and the arrangements for invoicing should be included. Charges may also be included in a separate document, the Tariff, referenced in the SLA. It is common in IT for individual services to be shared by a number of customers, and individual customers will use a range of services. This means that there is a choice in designing SLAs: they can be customer-based, where an SLA covers a range of services delivered to a particular customer; or they can be service-based, where a common SLA covers all customers of a given service.
The Customer service level rin a supply chain is a function of several different performance indices.
Zone of indifference is a service level where your customer service is forgettable!
ITIL defines a Service Level Agreement (SLA) as an agreement between an IT service provider and a customer. The SLA describes the IT service, records service level targets, and specifies the responsibilities for the IT service provider and the customer. A single SLA may cover multiple IT services or multiple customers.
Some organizations choose a multi-level SLA approach, where elements of services common to all customers are covered by a corporate-level SLA. Issues relating to a particular customer or customer group, no matter what the service, are then covered by a customer-level SLA and all issues relating to a specific service for the customer or customer group are covered by a service-specific SLA. The SLA for a service must be based on realistic, achievable targets (e.g. for performance and availability), and the achievement of these targets depends on the performance of the internal and external services that underpin the delivery of the main service. Putting it another way, SLAs must reflect the levels of service actually being delivered or that can be delivered. They are about what can be done rather than what we would like to be done. If a customer requires a different level of service, this would normally be dealt with by raising a Service Level Requirement. In order for SLM to be confident about the achievement of its SLA targets, it must have specific agreements with the internal and external providers. These agreements fall into two distinct types: • Underpinning Contracts (UCs) • Operational Level Agreements (OLAs) Both should be negotiated, agreed and in place before a commitment is made to the relevant SLA.
Some organizations choose a multi-level SLA approach, where elements of services common to all customers are covered by a corporate-level SLA. Issues relating to a particular customer or customer group, no matter what the service, are then covered by a customer-level SLA and all issues relating to a specific service for the customer or customer group are covered by a service-specific SLA. The SLA for a service must be based on realistic, achievable targets (e.g. for performance and availability), and the achievement of these targets depends on the performance of the internal and external services that underpin the delivery of the main service. Putting it another way, SLAs must reflect the levels of service actually being delivered or that can be delivered. They are about what can be done rather than what we would like to be done. If a customer requires a different level of service, this would normally be dealt with by raising a Service Level Requirement. In order for SLM to be confident about the achievement of its SLA targets, it must have specific agreements with the internal and external providers. These agreements fall into two distinct types: • Underpinning Contracts (UCs) • Operational Level Agreements (OLAs) Both should be negotiated, agreed and in place before a commitment is made to the relevant SLA.
Service Level is defined as the number of contacts handled within a defined acceptable period of time as a percentage of total contacts offered. If your SLA target is 80% in 20 seconds: SLA = (Contacts handled <20 seconds)/(Contacts Handled)
A SLA is a service-level agreement. It is often used to refer to the delivery time or when the service will take place.
A service-level agreement (SLA) is a negotiated agreement between two parties where one is the customer and the other is the service provider.
Service level agreement
Service-level-agreement
A customer wants two new computers added to the existing SLA without additional cost.
SLA stands for "Service Level Aggreemenet". It is the commitment from an organization to deliver certain level of services. Else, there will be compensation clauses in the form of rendering extra services or waivers, etc.
SLA makes business and customer interrelationship.It makes the the customer clearly known about what they expect from a quality service and refund or payment in case service was not properly delivered. so sla makes a customer trained. for an example a service may be consisting of different services and each service has a different vendor. in that case if any service fails all other services may disturbs . So if customer has exact idea he will contact the exact fault service provider not all the service providers.
To reduce your hold time for our customers you have to be aware of the queues to your department and be pro active in watching your SLA or ABD rate. CSR's should be aware of what the minimum level is expected of them and by making sure that they are not in codes. CSR's should be able to roll there calls and update systems with the customer on line and not the use of a code after they have hung up. ABD- Abandon rate of calls SLA- Service Level of Answer