Measuring customer service

Measuring customer service

When I work with clients on AMS selection, one question that often comes up is: "How good is the software company's customer service?"

"Customer service" means different things to different people. For example, here are the customer service complaints I most commonly hear:

  • "They won't let me talk to a human. All issues have to be submitted via their ticketing system and I have to wait weeks for a reply."
  • "Every time I ask a question, they tell me they're going to bill me for the help."
  • "The customer service staff I talk to don't understand how we use our system and are never able to help us."

For me, the true measure of customer service is how the software company responds when they have objectively made a mistake. In other words, it's not the mistake I judge, but how they respond to it. Case in point:

I was working with a client on an AMS implementation. In the course of discussions with the business analyst (BA) during the implementation, the BA stated that an online portal for single sign-on (SSO) was available for a $5,000 fee. Hearing this in the meeting, I was a bit stunned, because I had recalled from their RFP response that the SSO was included as baseline functionality (i.e., no additional fee).

I showed the RFP response to the BA, who said "Let me check with my manager." A little while later he told us: "The salesman made a mistake in his response, but we will honor it and not charge you the $5,000."

The mistake was clearly theirs. But their response is how I measured them. They could have easily said "Sorry, that was answered incorrectly, you still have to pay for this," but they chose the correct path of honoring their word.

It wasn't the mistake I judged them by, but how they responded to it when it was pointed out. That was good customer service.

Wes's Wednesday Wisdom Archives

Don’t ask for what you don’t need!

September 14, 2022

Don’t ask for what you don’t need! Recently I received a bill from a doctor’s …

Don’t ask for what you don’t need! Read More »

It is never done – so celebrate!

September 7, 2022

It is never done – so celebrate! A client of mine recently had their official …

It is never done – so celebrate! Read More »

MDR (Minimum Data Required)

August 31, 2022

MDR (Minimum Data Required) I’ve written about minimum viable product (MVP) in software development in the …

MDR (Minimum Data Required) Read More »

Simpler and Faster is Better

August 24, 2022

Simple and Faster is Better Earlier this week I was fortunate enough to attend a …

Simpler and Faster is Better Read More »

Patience and grace

August 17, 2022

Patience and grace A past client of mine recently told me: “You inspire confidence and …

Patience and grace Read More »

Sometimes you just have to try it and see what happens

August 10, 2022

Sometimes you just have to try it and see what happens The single greatest key …

Sometimes you just have to try it and see what happens Read More »

Training and testing

August 3, 2022

Training and testing I’ve written before that the best form of training follows this process: …

Training and testing Read More »

How to save a “failing” project

July 27, 2022

How to save a “failing” project It is not unusual for me to receive a …

How to save a “failing” project Read More »

How to avoid the “IT black hole”

July 20, 2022

How to avoid the “IT black hole” Going all the way back to my days …

How to avoid the “IT black hole” Read More »

The “People” are important!

July 13, 2022

The “People” are important! I’ve written a lot about people, process, and technology over the …

The “People” are important! Read More »

Scroll to Top