When you buy a ticket from JetBlue, it costs you an extra $15 to book a flight over the phone compared to doing it yourself over the Internet. The reason is obvious. Online transactions are much less costly for JetBlue, and the fee not only generates revenue but also helps the airline drive consumers to the lower-cost transaction. If you want to talk to someone on the phone, that's fine but it's going to cost you. If you don't like it, you can always call another airline.
The fee helps JetBlue keep its prices low, making it one of the most popular and profitable airlines around.
But what about government services, particularly those for which charging a fee doesn't make sense? How do you drive consumers to the low-cost transaction channel without being able to charge a fee?
Unemployment insurance is a classic government monopoly. There are no competitors offering the same service, and an unemployment insurance recipient isn't and shouldn't be charged a fee for applying for benefits. So what is a manager looking to provide better, faster, cheaper services supposed to do?
How about trying better, slower, cheaper?
When I took over as the commissioner for the Division of Unemployment Assistance in Massachusetts in 2004, the organization was focused on answering the phones quickly. Call the DUA, and your call would be answered in an average of just about three and a half minutes. The problem was, this obsession with answering the phones quickly made all the back-office operations inefficient, since it meant pulling higher-skilled workers off their tasks to take claims calls. This meant that our checks went out very slowly, which resulted in a lot of "where's my check?" calls, calls that add no value and, in a more efficient operation, wouldn't need to occur at all.
Our disputed claims backlog was also huge. The federal standard said that 80 percent of disputed claims should get a hearing in 45 days or less. For us, less than 30 percent were being heard in that time period. On my first week on the job, a very nice lawyer from Greater Boston Legal Services shook my hand, welcomed me to my new position and told me if the backlog didn't come down they'd take the agency to court.
I decided that service had to be looked at as an overall package, and that the best thing I could do for customers was to extend phone wait times. We weren't going to lose any customers over it, and unemployment insurance claimants were, by definition, people who had time on their hands.
The results came swiftly. Without the organizational chaos caused by the constant pursuit of low wait times, our backlogs came down. Within 18 months, 83 percent of our hearings were being held within 45 days, exceeding the federal standard. Checks were going out much faster too, meaning claimants got their first unemployment insurance check days earlier. This resulted in about a 20 percent drop in "where's my check?" calls which translated into 18,000 fewer calls each month.
Yes, customers now had to wait eight minutes instead of three and half, but there can be no doubt that their overall experience was improved. It's counter-intuitive, but just as JetBlue customers have an overall better experience with a $15 phone booking fee, DUA filers were better off waiting on hold for a few minutes.
The next area we tackled was also channel-related. In the early 1990s, the DUA offered just one way to "certify" your claim each week, which basically meant telling the DUA that you were still out of work and still looking. That one way was to go in person to a DUA office. This was inconvenient and costly for everyone.
By 2004, however, the problem was too many options. You could certify in person, over the phone, over the Web or by sending in a little postcard by U.S. mail.
I hated those little postcards. Twenty five percent of our certifications came in via postcards, burying us in roughly 25,000 pieces of mail. These postcards had to be reviewed and the data entered into our system by hand. It was labor-intensive, errors were common and it was a far more costly transaction than the automated "telecert" phone system or the Web.
We first tried to change behavior through training. Phone representatives were taught to encourage people to sign up for phone certification when they applied. This brought postcard usage down from 25 percent to 15 percent, but that was still too high for my liking.
When we investigated further, we found that postcards were overwhelmingly used by our Spanish-language speakers who couldn't follow the telephone prompts. So we introduced a Spanish-language version of the telecert system and the mail all but disappeared, with 96 percent of our certifications taking place through automated processes.
Even in the absence of price mechanisms and competitive comparisons, it still makes sense to examine the channels through which you deliver services. Sometimes adding a channel (such as the Spanish telecert) will allow you to do away with one entirely. Sometimes diminished service levels in one area (phone wait times) can allow you to deliver a better overall bundle of services.
Comments
AHT, Failure Demand and Improving Contact Centers
In the pursuit of costs and productivity contact center managers do or are asked to do "dumb" things. One of them is AHT which I have posted on and had discussions about many times in my blog posts and at customermanagementIQ.com. A shortened AHT (average handle time) may get visible costs down, but actual increase what we call failure demand (demand caused by a failure to something or do something right for a customer), therefore causing total costs to increase. Failure demand in organizations run about 25 - 75% of all contacts in most service industries, higher for government. This is a counter-intuitive truth and one of many we have discovered applying systems thinking techniques to such centers.
To improve call centers we teach organizations to design their organizations against customer demand. We have found techniques like lean that teach standardization of the work to not absorb the variety of demand which in turn increases failure demand from customers. IVRs contribute to failure demand and frustration. By designing against customer demand we allow the system to absorb the variety offered by customers decreasing the failure demand sometimes by 50-60% less calls coming in.
Enjoyed the article!
Regards, Tripp Babbitt
www.newsystemsthinking.com
What are the incentives for public sector managers?
Aside from the negative pressure of facing a lawsuit, are public-sector managers rewarded in a systematic, positive way for improving "customer" service, cutting costs and improving efficiency? Or are public sector managers incentivized to preserve the status quo, ask for more money, and increase their budgets --and their salaries?
Rewarding public sector managers
I've worked 20 years as a public purchasing manager in four different agencies. Public sector managers are rarely rewarded for process improvement, even more rarely for customer service improvement. I'd surmise this is because public agencies must operate a balanced budget and little spare funds are available for reward recognition. There are no cruises to Hawaii for salesman of the year. In the private sector, a top performer is far more likely to be rewarded. I feel public managers are more likely to push the process improvement envelope simply because it makes the job easier or truly does improve customer service. Again, personal belief - I feel this done out of dedication rather than the seeking of rewards and recognition. Your reward for creating improvement in the public sector is that you hopefully attain promotion and get to keep your job. The adage of "make yourself invaluable" is highly exemplified in the public sector.
incentives
No, we are not rewarded with money or budgets. We make creative changes to improve the process and make it more efficient. I think it's a sickness quite frankly. . .
Engineering Government
This is a fine example of how engineering principles can be applied to government for increasing efficiency. How can managers in the government be incentivized to make changes like this? Bureaucratic inertia is an awfully hard force to combat, yet the author has proven it can be accomplished. I just wonder how our governments can make radical systemic transformations like this one, especially when it involves job losses and turf battles.
Longer Wait Times & Customer Service
I would like to comment on John O'Leary's article titled, "How longer waits can mean better customer service." The topic strikes me as one of those that becomes a huge issue in times of economic crisis, and frankly if customer service was acceptable in the good times people might be more forgiving, esp. in government. Unfortunately, having worked in government, there is a prevalent attitude within the ranks that recipients of social services are not entitled quality, timely customer service as it is. Therefore, I think an article such as this may unleash the unseen beast that has been kept at 30 minute wait times to this point.
O'Leary does make a good point of focusing on a bundle of service, but I think it is unreasonable to suggest that everyone's needs can be provided for in an automated system. Technology is a huge blessing in terms of making information available at the click of a button and making application processes more convenient and faster; that, in itself, is motivation enough for people to use it. We have to be realistic though, and I think educated, intelligent people forget this, not everyone 1) is comfortable with the technology, 2) has convenient access to the technology, or 3) has the mental capacity to navigate the system which can be very intimidating to even the most intelligent (esp. with the legalese that in inherent in some information).
Just because information is available doesn't mean people can find or understand it, that is why we need customer service. We do need to focus on providing all-around service and in a way that says "our service to you is important," no matter who is being served. If we can't value person-to-person service, we're missing the point; and I don't know anyone who thinks that even 10 minute wait time communicates a desire to provide customer service.
Longer Wait Times and Human Nature
Although the comment relating to technology and access is of interest it completely ignores human nature. People tend to do what is the easiest, most familiar, and most convenient, even given excellent alternatives. Joe public as an individual does not care how his/her actions affect the efficiency of the system. Joe just wants quick service. If the phone service is familiar and quick...Joe will use it and ignore all other systems. Its easier to pick up the phone and within minutes or even seconds the problem (in his mind) belongs to someone else. Also, people are rarely forgiving of public service no matter the quality. They see their own experience and globalize it. Bad experiences are specially memorable and often generate feedback and public comment. Good experiences are rarely remembered and commented upon even less. It is not that we as a society do not value person-to-person service...it simply that we cannot afford it. Social Service programs should be financially efficient and they should address the needs which they were created to address. Social Service programs should not necessarily be "easy" or "convenient". The boon of computers and automation is to free workers and save that resource for other than the repetitive task.