Servicely.ai - The evolution of the Service Desk

Service Desks, or Help Desks as we used to call them, have been around for years. If we look back to the early 1980's we had the early vendors like Peregrine and BMC who gave IT support the ability to log trouble tickets and track their lifecycle.

In the late 1980's client service architectures become the order of the day so we shifted  from mainframe green screens to windows based client server technologies.

Products like HP Openview Service Desk or commonly referred to as OVSD entered the market, provide a richer user experience for the Service Desk agents. At around the same time the Helpdesk become known as the Service Desk as the focus shifted from simply helping "users" fix issues to actually viewing these users/employees as customers of the services provided by IT. The Service Desk became shop front to IT as the level of reliance on technology increased across the business. As more technology began driving business it was necessary to have clearly defined processes and SLA's on how to support this rapidly growing mix of technologies used to support the business. it become clear we needed a process framework and so ITIL was born.

Organisations across the globe invested heavily to employ process consultants to help define and document best practice processes aligned to the ITIl Framework. With  process swim lanes in place and roles and responsibilities defined we needed to educate IT staff to use a common taxonomy and understood and Incident was not a Request. Vendors acknowledged the adoption of ITIL and importance of supporting it and so  to ITIL verified was introduced with Pink Verify able to assist in verifying.

So now we had processes defined according to a framework we had people educated on Incident vs Request vs Problem and we had a tools to drive the process which relied on people - people, process, technology.

What we failed to achieve is how do we improve the service experience for our employees, call wait times increased, call resolution times increased and scaling the Service Desk was expensive, more calls resulted in more Service Desk staff. And so the inevitable happened, service experience declined with an overloaded Service Desk, employees waited days for their issues to be resolved and business productivity was impacted resulting in "we can outsource the service desk for less expense". This has  it's own challenges if not done correctly which I will talk in in a future blog.

Software vendors being the innovative crowd they are continued to innovate and SaaS was born with products like ServiceNow where Opex vs Capex being the discussion of the day. While SaaS certainly removed the operational overhead for the IT department of having to manage yet another application, it did little to solve the employees service experience when dealign with the Service Desk, which research shows the important factors are:

  1. How quickly can you solve my issue
  2. Can you solve it on first contact
  3. Can you keep me updated on the progress if you cant solve it on first contact

Instead we moved to solve only part of the problem - the load on the Service Desk and having to do more with less. We invested in self-service portals and asked users to try and solve their issues themselves with Knowledge Article before contacting the Service Desk and so the phrase "shift left" was coined.

And so we usher in a new era, and era where Artificial Intelligence (AI) enables IT to deliver a rich service experience to the employees by solving their issues quickly and on first contact. An era where AI is embedded in the enterprise application an abstracts the complexity of AI through Observe | Learn | Augment | Automate. An era where doing more with less is possible. An era where we can do more with less and deliver the best possible service experience for our employees.

Don't be stuck in the NOW.Servicely.ai the Smart | Simple | Better way to run your Service Desk

Share this post

Servicely.ai - The evolution of the Service Desk

Servicely.ai - The evolution of the Service Desk
Written by
Published on
October 5, 2021

In the late 1980's client service architectures become the order of the day so we shifted  from mainframe green screens to windows based client server technologies.

Products like HP Openview Service Desk or commonly referred to as OVSD entered the market, provide a richer user experience for the Service Desk agents. At around the same time the Helpdesk become known as the Service Desk as the focus shifted from simply helping "users" fix issues to actually viewing these users/employees as customers of the services provided by IT. The Service Desk became shop front to IT as the level of reliance on technology increased across the business. As more technology began driving business it was necessary to have clearly defined processes and SLA's on how to support this rapidly growing mix of technologies used to support the business. it become clear we needed a process framework and so ITIL was born.

Organisations across the globe invested heavily to employ process consultants to help define and document best practice processes aligned to the ITIl Framework. With  process swim lanes in place and roles and responsibilities defined we needed to educate IT staff to use a common taxonomy and understood and Incident was not a Request. Vendors acknowledged the adoption of ITIL and importance of supporting it and so  to ITIL verified was introduced with Pink Verify able to assist in verifying.

So now we had processes defined according to a framework we had people educated on Incident vs Request vs Problem and we had a tools to drive the process which relied on people - people, process, technology.

What we failed to achieve is how do we improve the service experience for our employees, call wait times increased, call resolution times increased and scaling the Service Desk was expensive, more calls resulted in more Service Desk staff. And so the inevitable happened, service experience declined with an overloaded Service Desk, employees waited days for their issues to be resolved and business productivity was impacted resulting in "we can outsource the service desk for less expense". This has  it's own challenges if not done correctly which I will talk in in a future blog.

Software vendors being the innovative crowd they are continued to innovate and SaaS was born with products like ServiceNow where Opex vs Capex being the discussion of the day. While SaaS certainly removed the operational overhead for the IT department of having to manage yet another application, it did little to solve the employees service experience when dealign with the Service Desk, which research shows the important factors are:

  1. How quickly can you solve my issue
  2. Can you solve it on first contact
  3. Can you keep me updated on the progress if you cant solve it on first contact

Instead we moved to solve only part of the problem - the load on the Service Desk and having to do more with less. We invested in self-service portals and asked users to try and solve their issues themselves with Knowledge Article before contacting the Service Desk and so the phrase "shift left" was coined.

And so we usher in a new era, and era where Artificial Intelligence (AI) enables IT to deliver a rich service experience to the employees by solving their issues quickly and on first contact. An era where AI is embedded in the enterprise application an abstracts the complexity of AI through Observe | Learn | Augment | Automate. An era where doing more with less is possible. An era where we can do more with less and deliver the best possible service experience for our employees.

Don't be stuck in the NOW.Servicely.ai the Smart | Simple | Better way to run your Service Desk

Share this post
Servicely.ai - The evolution of the Service Desk
October 5, 2021

Stay Updated with Servicely

Sign up for our mailing list to stay in the loop with Servicely.

Sign Up
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
5 min read

Blog title heading will go here

Written by
Full Name
Published on
22 January 2021

Introduction

Mi tincidunt elit, id quisque ligula ac diam, amet. Vel etiam suspendisse morbi eleifend faucibus eget vestibulum felis. Dictum quis montes, sit sit. Tellus aliquam enim urna, etiam. Mauris posuere vulputate arcu amet, vitae nisi, tellus tincidunt. At feugiat sapien varius id.

Eget quis mi enim, leo lacinia pharetra, semper. Eget in volutpat mollis at volutpat lectus velit, sed auctor. Porttitor fames arcu quis fusce augue enim. Quis at habitant diam at. Suscipit tristique risus, at donec. In turpis vel et quam imperdiet. Ipsum molestie aliquet sodales id est ac volutpat.

Image caption goes here
Dolor enim eu tortor urna sed duis nulla. Aliquam vestibulum, nulla odio nisl vitae. In aliquet pellentesque aenean hac vestibulum turpis mi bibendum diam. Tempor integer aliquam in vitae malesuada fringilla.

Elit nisi in eleifend sed nisi. Pulvinar at orci, proin imperdiet commodo consectetur convallis risus. Sed condimentum enim dignissim adipiscing faucibus consequat, urna. Viverra purus et erat auctor aliquam. Risus, volutpat vulputate posuere purus sit congue convallis aliquet. Arcu id augue ut feugiat donec porttitor neque. Mauris, neque ultricies eu vestibulum, bibendum quam lorem id. Dolor lacus, eget nunc lectus in tellus, pharetra, porttitor.

"Ipsum sit mattis nulla quam nulla. Gravida id gravida ac enim mauris id. Non pellentesque congue eget consectetur turpis. Sapien, dictum molestie sem tempor. Diam elit, orci, tincidunt aenean tempus."

Tristique odio senectus nam posuere ornare leo metus, ultricies. Blandit duis ultricies vulputate morbi feugiat cras placerat elit. Aliquam tellus lorem sed ac. Montes, sed mattis pellentesque suscipit accumsan. Cursus viverra aenean magna risus elementum faucibus molestie pellentesque. Arcu ultricies sed mauris vestibulum.

Conclusion

Morbi sed imperdiet in ipsum, adipiscing elit dui lectus. Tellus id scelerisque est ultricies ultricies. Duis est sit sed leo nisl, blandit elit sagittis. Quisque tristique consequat quam sed. Nisl at scelerisque amet nulla purus habitasse.

Nunc sed faucibus bibendum feugiat sed interdum. Ipsum egestas condimentum mi massa. In tincidunt pharetra consectetur sed duis facilisis metus. Etiam egestas in nec sed et. Quis lobortis at sit dictum eget nibh tortor commodo cursus.

Odio felis sagittis, morbi feugiat tortor vitae feugiat fusce aliquet. Nam elementum urna nisi aliquet erat dolor enim. Ornare id morbi eget ipsum. Aliquam senectus neque ut id eget consectetur dictum. Donec posuere pharetra odio consequat scelerisque et, nunc tortor.
Nulla adipiscing erat a erat. Condimentum lorem posuere gravida enim posuere cursus diam.

Share this post
Jane Smith
15 Feb 2022
7 min read

Stay Updated with Servicely

Sign up for our mailing list to stay in the loop with Servicely.

Sign Up
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.