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

Just start. And it’s never done.

August 27, 2025

Just start. And it’s never done. Last week I had the opportunity to lead a […]

Don’t ask if you’re not going to answer!

August 20, 2025

Don’t ask if you’re not going to answer! In the past week, on three different […]

Seek forgiveness rather than permission

August 6, 2025

Seek forgiveness rather than permission “Seek forgiveness, not permission.” I can’t remember when I first […]

Is a 360 degree view necessary?

July 30, 2025

Is a 360 degree view necessary? “A 360 degree view of our members should NOT […]

Why data matters

July 23, 2025

Why data matters I write about data because managing our data effectively will help us […]

It’s about process

July 16, 2025

It’s about process I’m in the midst of adding an AI agent to my website […]

Data integrity reports

July 9, 2025

Data integrity reports I speak and write a lot about data integrity reports. So I […]

The most important training tip

June 25, 2025

The most important training tip I’ve been sitting in a lot of database training sessions […]

Be careful about getting tangled

June 18, 2025

Be careful about getting tangled “We had done a lot to tangle ourselves up.” – […]

Discipline. Always discipline.

June 11, 2025

Discipline. Always discipline. I’ve been producing a newsletter in some form for over 25 years […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top