For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Posted: Tue Jul 01, 2008 4:08 pm Post subject: FCR and FLR
First Call resolution ( FCR) appeared a task too daunting so we have proposed a "First Line resolution" where in the opening and the resolving group is the same. Only the Service Desk can open the tickets, the SD and the support teams can resolve them and only the SD can close them after users' confirmation. What we proposed is to measure the first line's performance against the 2nd and the 3rd line of support. The First Line Resolution (FLR) should go up as a continual Service improvement Plan.
having said that, I feel like proposing something out of the world. Do we know something like the first line Resolution? Can anyone please help me with the most accepted definitions of the FCR for the IT Service desk?
not an ITIL question again, but is there any ?
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Tue Jul 01, 2008 8:29 pm Post subject:
viv,
I don't see how there can be definitions.
The advantage of first call fix is the perceived speed of resolution for the user (and the subsequent trimness in the bureaucracy because there is less transitioning).
The cost of first call fix is the level of expertise tied up at the phones, sometimes performing tasks way below their skill level. The higher the first fix target the greater the cost to achieve it.
What are your customers paying for? What is acceptable to them?
If you set high targets do your customers/users sometimes worry that the front line staff are trying to do things at the very edge of their capability rather than pass it back to second line?
The answer has to lie in a- the requirements (e.g. urgency and impact for the business); b- the skill level in the front line; c- the staffing level in the front line; d- the profile of calls you receive (in terms of technical complexity etc.); e- costs. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
I think I know sth like first line resolution.
We use it besides FCR in order to show that besides FCR you do some work as well.
We sometimes close tickets after some time just because the user does not have time to implement the solutions on the phone, etc.
Still I completely agree with Diarmid - it depends on what the business requires.
Joined: Oct 07, 2007 Posts: 441 Location: Jakarta, INA
Posted: Wed Jul 02, 2008 10:53 am Post subject:
Hi,
I just don't get it. Why do you want to measure performance by FCR?
Wouldn't it be more useful if it's used to measure the effectiveness of related processes?
What if the number of FCR drops in one period because most calls were have to be resolved at 2nd level? Does that mean that the SD didn't perform?
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Wed Jul 02, 2008 6:38 pm Post subject:
Hi,
rzesie wrote:
Are there any other measures than FCR or FLR that can measure if the service desk is solving enough tickets?
All you need is another set of classifications for calls. One that identifies whether the call is of a type that can and should be resolved at the service desk. Then target, say, 95% of those.
Of course you need the definitions and the training requirements to match the classifications and you need the staffing resource to match the call volumes. The service desk can only resolve calls within its capability!
Is your customer paying for 50% first fix? Do you have clear definitions on the nature and volume of calls that this applies to? Is your customer involved in call analysis and review?
When you offer a first fix percentage then you have to bound it with the assumptions about the calls so that you can change it if the nature of the calls changes. This can happen because the business has changed or because the users have become more sophisticated and no longer make simple calls or for lots of other reasons. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Thanks for the reply. I completely agree with you. Measuring first line fix rate only on the categories that are "solvable" is the best way to check service desk performance.
Unfortunately I'm in a position where my SD is presented with a contract which we must fullfil and the 50% of first contact is required.
You are also completely right about the changing nature of calls but the only thing I can do is propose reviews.
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Thu Jul 24, 2008 9:33 pm Post subject:
Jacek,
I think you need some risk analysis on that contract. If it might be leading to problems then you will be into difficult negotiations with your customer. Developing a good relationship which emphasizes that you have a common interest in the quality of the service will be key.
I think that some of the other regular posters will have a better practical understanding in this area than I do. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum