Helpdesk SLAs
-
Consider "network issues" under normal. Who determines what's a network issue? Does it matter if it's for one person or the entire LAN? If no on can use the internet because your DNS server is down, is that a network issue, or a internet issue? DNS sounds technical, so does that mean it's a High priority?
Do you see where I'm going with this?The purpose of the SLA is to set the expectation for the end user. When you define things in terms you understand, the end user might still be confused.
-
@ambarishrh I would break off the SLA into a new topic.
-
@aaronstuder said in Best practices for helpdesk portal options for end user:
@ambarishrh I would break off the SLA into a new topic.
How do i do that (retaining the related comments) as a new topic?
-
It would also be create to create a troubleshooting category would eliminate a possible runaround of all of the employees in the search for answers.
-
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
-
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
The purpose for this is also to evaluate the existing issues, see if our small team can cater the requirements and based on the results we either get more people or increase the sla. As of now this will be visible only to IT team and based on our analysis we will release to users on a later stage with SLA that we can achieve
-
@ambarishrh said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
The purpose for this is also to evaluate the existing issues, see if our small team can cater the requirements and based on the results we either get more people or increase the sla. As of now this will be visible only to IT team and based on our analysis we will release to users on a later stage with SLA that we can achieve
SLAs are not a good tool for that. Just use good reporting for that. SLAs are adversarial, not something you ever want to use internally.
-
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
The purpose for this is also to evaluate the existing issues, see if our small team can cater the requirements and based on the results we either get more people or increase the sla. As of now this will be visible only to IT team and based on our analysis we will release to users on a later stage with SLA that we can achieve
SLAs are not a good tool for that. Just use good reporting for that. SLAs are adversarial, not something you ever want to use internally.
Yet they are integrated in several helpdesk options.
-
@kyle said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
The purpose for this is also to evaluate the existing issues, see if our small team can cater the requirements and based on the results we either get more people or increase the sla. As of now this will be visible only to IT team and based on our analysis we will release to users on a later stage with SLA that we can achieve
SLAs are not a good tool for that. Just use good reporting for that. SLAs are adversarial, not something you ever want to use internally.
Yet they are integrated in several helpdesk options.
Yes, because help desk software is a generic thing that can be used with the public, internally, or a combination of both. Just because a feature is already integrated doesn't mean it's a good option to use. I think of something like an SLA for leased lines like T1/T3.
-
@travisdh1 said in Helpdesk SLAs:
@kyle said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
The purpose for this is also to evaluate the existing issues, see if our small team can cater the requirements and based on the results we either get more people or increase the sla. As of now this will be visible only to IT team and based on our analysis we will release to users on a later stage with SLA that we can achieve
SLAs are not a good tool for that. Just use good reporting for that. SLAs are adversarial, not something you ever want to use internally.
Yet they are integrated in several helpdesk options.
Yes, because help desk software is a generic thing that can be used with the public, internally, or a combination of both. Just because a feature is already integrated doesn't mean it's a good option to use. I think of something like an SLA for leased lines like T1/T3.
I know. I just wish they were more granular in features as there are some hard coded features the are unnecessary and just clutter the classification of tickets. We currently use ManageEngine Service Desk and SLA's are built in and part of the reporting metrics despite the fact we don't use them.
-
@kyle said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
The purpose for this is also to evaluate the existing issues, see if our small team can cater the requirements and based on the results we either get more people or increase the sla. As of now this will be visible only to IT team and based on our analysis we will release to users on a later stage with SLA that we can achieve
SLAs are not a good tool for that. Just use good reporting for that. SLAs are adversarial, not something you ever want to use internally.
Yet they are integrated in several helpdesk options.
Helpdesks are often used and needed in adversarial conditions.
-
@kyle said in Helpdesk SLAs:
@travisdh1 said in Helpdesk SLAs:
@kyle said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
@scottalanmiller said in Helpdesk SLAs:
@ambarishrh said in Helpdesk SLAs:
we are a very small team now, 250+ users 3 techs. Screen connect plays a bigger role here!
Idea is to set an SLA and review this on regular basis, find out the gap and either increase headcount or if no budget for additional headcount, then increase the SLA.
With the current tech headcount, the SLA that we are thinking are:
*Resolution includes temporary fix or work-around solution.New hardware requests usually take 4-6 weeks to deliver from HP (we can keep stock of 5 but the user requests are quite a lot this year and next year as well, but no finance approval to keep more than 5 as of now), so agreed with HR on this timeline.
An SLA means that there is a punishment to you if you do not meet the requirements. What happens to the IT team if they cannot resolve these issues in the SLA time? How do you determine what is within the scope of what IT can have fixed and not?
The purpose for this is also to evaluate the existing issues, see if our small team can cater the requirements and based on the results we either get more people or increase the sla. As of now this will be visible only to IT team and based on our analysis we will release to users on a later stage with SLA that we can achieve
SLAs are not a good tool for that. Just use good reporting for that. SLAs are adversarial, not something you ever want to use internally.
Yet they are integrated in several helpdesk options.
Yes, because help desk software is a generic thing that can be used with the public, internally, or a combination of both. Just because a feature is already integrated doesn't mean it's a good option to use. I think of something like an SLA for leased lines like T1/T3.
I know. I just wish they were more granular in features as there are some hard coded features the are unnecessary and just clutter the classification of tickets. We currently use ManageEngine Service Desk and SLA's are built in and part of the reporting metrics despite the fact we don't use them.
I generally prefer light, simple helpdesks. Unless you are a huge organization, most of that extra stuff is just wasted and in the way.
