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

AI is a journey, not a destination

April 15, 2026

AI is a journey, not a destination Lately I’ve noticed a lot of associations talking […]

Action produces information

April 8, 2026

Action produces information “Action produces information. If you’re unsure of what to do, just do […]

Why a single source of truth is so beneficial…

March 25, 2026

Why a single source of truth is so beneficial… The holy grail of data management is […]

Just because you can, doesn’t mean you should

March 18, 2026

Just because you can, doesn’t mean you should I’ve worked in and with associations for well […]

Data doesn’t need to be perfect to be useful

March 4, 2026

Data doesn’t need to be perfect to be useful “Your data doesn’t have to be […]

Don’t just clean data, clean reports and queries

February 25, 2026

Don’t just clean data, clean reports and queries One of the reasons I exhort my […]

Don’t forget, your staff have day jobs…

February 18, 2026

Don’t forget, your staff have day jobs… The vast majority of my work is finite […]

Beware the automated “How did we do?” trap!

February 11, 2026

Beware the automated “How did we do?” trap! One of the downsides of technology is […]

Hindsight is 20/20

February 4, 2026

Hindsight is 20/20 I’m currently working with a client that is moving from their legacy […]

Cheaper now; costlier later.

January 28, 2026

Cheaper now; costlier later. Most of my clients are very cost-conscious, understandably. After all, who […]

Leave a Comment

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

Scroll to Top