Skip to main content

just enough service details


The bane of many technicians existence is completing their paperwork. It goes without saying that if we are going to charge a customer "x" we should at least tell them what we did in some comprehensible manner. What does the customer really want… a summarization which wraps up what has occurred; if the call was related to troubleshooting, what can be done to avoid this incident in the future.  Certainly an explanation as suggested requires more than just pure documentation of the events which have occurred during a service call (scheduled or unscheduled). Drawing conclusions, leaning on intuition, and having the ability to articulate  passed, current, and future scenarios, is where the challenge exists for many field workers.



Remember for a moment the last time that you were composing a correspondence that contained technical information. You probably wrote a little more than you should have, reviewed it, moved some things around and hopefully removed some of the extraneous content, and ended up with a clean crisp summarization. Could it be that the challenge we have with getting field workers to adequately complete their paperwork is related to:

  • complete understanding of field conditions | let's consider for a moment that your field worker is really a parts swapper. Their understanding of systems is basic enough to guide them towards logical conclusions on what major component has failed and through a process of trial and error have replaced components until the system appears to be running correctly. If this describes your field worker how do we expect to articulate what the actual issue is if they themselves are not clear?
  • bury the meaning in words | we have all had those field workers who write a short story on every service call. For years I have written documents and created recommendations and I can tell you personally that writing a two page document is much easier than writing one paragraph. In order to titrate information down to a digestible block of words you must fully understand not only the field conditions but also understand your client.
  • writing skills | over the years attempts have been made to obviate the content related to writing out service tickets. Based on problem codes, nature's of call, we can insert fixed lines of words that describe what the likely issue is for the field worker when using digital devices. However, the root problem still exists with the technician and their ability to quickly articulate issues to our clients. Forget about writing skills for a moment, if the field worker has a challenge describing issues found in the field to the client than the client's confidence in your organization will diminish.



One of the keys to having a financially successful service organization is managing your AR and your days sales outstanding (DSO). As we know from experience high DSO numbers can be an indicator of how the client perceives your organization and levels of service delivered. One of the contributing factors is the confidence level that the client has with you and your field workers. Providing the right information prepared in a manner that is both insightful and actionable will contribute positively to your DSO reduction efforts.



-----

Next post:  does empathy play a role in service delivery?

-----

Comments

Popular posts from this blog

why transform?

Why do I want to change, who said anything was wrong with my stack of papers and sea of Excel files?   We solve problems, that is a key characteristic of any successful service organization, if it isn't broke why fix it?   Often, when discussing a transformation from paper or cobbled together systems to a cohesive digital approach, folks struggle with the gap between what they currently do and how digital tools can help.   You really need to look at where the pain points are in your organization and how these compare to your business objectives.   Consider writing down these points on the whiteboard in no particular order, spend a few days shuffling and consolidating into a prioritized list.   Once you have the "why" and the "what" identified, the old remaining step is "how".   Some of the most popular observations over the years have been; Slipping through the cracks :   you know, not the major muscle movements, instead those little i...

expert at everything...not a problem

Well... I would say sometimes there certainly is a perceived notion that one person is an expert at everything. For the worker "everything" may be defined as the specific area in which you were hired or are constantly scheduled. Our opinions are frequently influenced off of past experience, or information we've received from their coworkers. Unfortunately this only gives us partial insight to that workers expertise and often is limited to their most recent history. Narrowly focused accounting is made of the skills that this individual possess. Come on, can't we figure out a way to leverage all of the skills of a particular worker? One of the challenges has always been that relationship between the activities which need to be accomplished and the myriad skills of individuals within your workforce. In addition, even if you could inventory and get a pretty good handle on the skill sets, they are constantly changing (with any luck) and thus the ineffective process of ...

Digital distance

As influential Irene entered the dispatch department this hot July afternoon all that she heard was the tapping of keyboards.   The energy felt like a controlled, almost clinical environment.   It wasn't that many years ago when the sense of chaos, wrapped in genuine human concern for our clients, filled the room with a much different feeling.   Could it be that our ambitions to become more efficient, by leveraging technology has simply created a reason for us not to communicate verbally with one another?    Hasn't the idea all along been centered around our ability to spend more time with our customers? Making each and every one of them feel as if they are our most important client?   Certainly I'm not suggesting we go back to big chief tablets and number two pencils.   Yet, we need to reflect and strike a balance between digitization and delivery. By pure coincidence, avid Andy was composing a memo attempting to give his opinion, without tr...