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
Be grateful
Be grateful As Thanksgiving approaches here in the US, I’m reminded of two words: Be […]
Do you really need to approve them?
Do you really need to approve them? I often joke that the very best (because […]
Negativity bias is why we need database PR
Negativity bias is why we need database PR I’ve written before how cognitive biases can affect […]
A system change requires a culture change
A system change requires a culture change By its very nature, when you introduce a […]
Where is that data?
Where is that data? This is what data management nirvana looks like: When the question starts with […]
Be deliberate, but act quickly
Be deliberate, but act quickly Be deliberate, but act quickly. These are my words of […]
Why associations don’t like the “S” word
Why associations don’t like the “S” word A couple of weeks ago I asked my […]
The “S” stands for “Standard”
The “S” stands for “Standard” In a conversation with a past client, we were discussing […]
Is that meaningless data?
Is that meaningless data? I’m not a big quotes guy, but one of the few […]
Be aware of unintended consequences
Be aware of unintended consequences I’ve written before that every decision involves a trade-off. When […]
