Skip to main content

Celebrating National Customer Service Week (Part 1)

Times are tough and many organizations are looking for ways to reduce costs. However, even in difficult times, investing in the people, processes and technology used to serve customers is sure to reap a positive return. National Customer Service Week (NCSW), held October 5-9 in 2009, provides an excellent opportunity to explore ways to better serve your customers. It is also an excellent time to let the employees who serve your customers know how important they are to the success of your organization.

Always the first week in October, NCSW is designed to raise awareness of customer service and the vital role it plays within an organization. It is also an opportunity to say thank you to those who work in customer service for a job well done. Organizations take part in NCSW by hosting events in their workplace. These events can be large or small, serious or fun, they can be held all through the week or just on one day…. it's up to each organization to decide how to celebrate.

Many organizations use this week as an opportunity to provide training and refocus the efforts of their staff on the needs of their customers. In IT, a common misconception is that the Service Desk is responsible for customer satisfaction because of its role as a single point of contact. However, every team in IT is part of the value network that creates value for customers, and each team must understand the importance of its contribution.

Celebrating National Customer Service Week doesn’t have to cost a lot. It really just takes a little creativity. For example:

  • Begin each meeting or training class with a review of team goals and how they contribute to customer satisfaction.
  • Celebrate achievements such as an increase in your customer satisfaction rating. Food is always a fun and easy way to celebrate!
  • Send a daily email with positive customer feedback and inspiring customer-related quotes.
  • Offer a “lunch and learn” series focused on the soft skills needed to deliver excellent service such as listening skills, communication skills and customer service skills.
  • Launch a project aimed at creating better relationships between your Service Desk and second- and third-line support teams by creating Operational Level Agreements (OLAs) that clearly spell out roles and responsibilities.
  • Review your policies and processes and ensure they are not standing in the way of excellent customer service. Begin with a review of recent customer satisfaction surveys and complaints to ensure changes fully address your customers’ needs and expectations.

Best practice frameworks such as ITIL® and ISO/IEC 20000 are aimed at ensuring the focus always stays on customer needs and expectations. In fact, customer satisfaction by definition is “the difference between how a customer expects to be treated and how the customer perceives he or she was treated. Achieving high customer satisfaction begins with understanding customer requirements. It also involves determining how best to manage expectations in terms of the service levels that can be delivered given existing capabilities and resources.


Join me next week for a look at how to ensure your processes are “customer friendly.” In the mean time, get planning! National Customer Service Week is two weeks away and so you’ve got plenty of time.

What have you got planned?

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…