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

Action isn’t the same as progress

January 25, 2023

Action isn’t the same as progress I’ve written before that not taking action is an …

Action isn’t the same as progress Read More »

Start with the end in mind

January 18, 2023

Start with the end in mind Like so many, I probably first heard the phrase …

Start with the end in mind Read More »

It’s quiet in here…maybe TOO quiet…

January 11, 2023

It’s quiet in here…maybe TOO quiet… One of the truisms of data management is that …

It’s quiet in here…maybe TOO quiet… Read More »

It’s ALWAYS about expectations

January 4, 2023

It’s ALWAYS about expectations The headline reads: “Tesla sets record for vehicle deliveries, an increase …

It’s ALWAYS about expectations Read More »

It’s hard to get UNangry

December 14, 2022

It’s hard to get UNangry I often emphasize to my clients the importance of testing …

It’s hard to get UNangry Read More »

Some history IS important!

December 7, 2022

Some history IS important! When I’m advising clients on data conversion (moving data from one …

Some history IS important! Read More »

“Many mickles make a muckle.”

November 30, 2022

“Many mickles make a muckle.” “Many mickles make a muckle.” – George Washington Apparently, this …

“Many mickles make a muckle.” Read More »

It’s easy to collect; it’s harder to manage

November 16, 2022

It’s easy to collect; it’s harder to manage The beauty of today’s highly configurable AMS …

It’s easy to collect; it’s harder to manage Read More »

Tell them why you want the data

November 9, 2022

Tell them why you want the data Because data is so easy to collect these …

Tell them why you want the data Read More »

Don’t get hung up on something minor

November 2, 2022

Don’t get hung up on something minor I’m a problem solver. I love to solve …

Don’t get hung up on something minor Read More »

Scroll to Top