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

There is nothing so permanent as business rules

November 25, 2020

There is nothing so permanent as business rules Nobel Prize-winning economist Milton Friedman said, “There’s nothing […]

Budget for feature discovery and adoption

November 18, 2020

Budget for feature discovery and adoption When developing a budget for implementation of a new […]

Customize staff pages for better user adoption

November 11, 2020

Customize staff pages for better user adoption The single most important element to data management […]

Don’t ask questions for which you already know the answer

November 4, 2020

Don’t ask questions for which you already know the answer I was recently completing an […]

All decisions involve risk

October 28, 2020

All decisions involve risk Whether it’s choosing a new AMS or introducing a new product […]

Try flowcharting your processes

October 21, 2020

Try flowcharting your processes Working with a client recently on their membership join process reminded me […]

“I just want a system I don’t have to fight with.”

October 14, 2020

“I just want a system I don’t have to fight with.” I asked my client: […]

Inertia Contributes to Bad Data

October 7, 2020

Inertia Contributes to Bad Data Without knowing anything about your organization or its data, I’d […]

What are you doing with new contacts?

September 30, 2020

What Are You Doing with New Contacts/ I was very interested to read in a […]

Be Aware of Selection Bias

September 23, 2020

Be Aware of Selection Bias I wrote recently about the mistaken perception of older members […]

Leave a Comment

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

Scroll to Top