It’s month end. A report won’t run, the deadline is at four, and you’ve just been put in a queue behind forty other people. The software has worked perfectly for eleven months. That afternoon is the one you’ll remember.
Nobody writes “the support team” on a feature list, yet it shapes what customers think of the product more than anything on that list. As far as the customer is concerned, the person who answers when something breaks is the software.
Customers judge software on its worst day
On a normal day, good software is invisible. You log in, do the work and log out. The moments that stick are the ones where something goes wrong, or where you can’t work out how to do something you need done by Friday. In those moments the product is whoever picks up the phone or answers the ticket, and how quickly they understand the problem.
A customer who gets a fast, clear answer from someone who knows the product comes away trusting it more than before it broke. A customer who gets a ticket number and a script comes away shopping for a replacement.
Treat support as a cost and the product gets worse
Plenty of software companies run support like a call centre. They measure it on tickets closed per hour, push customers towards a help article and hire the cheapest people they can train in a week. On a spreadsheet, it looks efficient.
The damage shows up elsewhere. Support is the only team that hears every day where the product confuses people, which screens generate the same question and which workarounds customers have invented because a feature doesn’t do what they expected. When support is cheap and cut off from the people building the product, all of that knowledge stays in the ticket system. The same problems get answered a thousand times and fixed never.
Companies that treat support as part of the product do the opposite. The people answering calls know the product deeply, and they know the customer’s work well enough to understand what they’re trying to do. What they hear goes straight back to the people deciding what to build, and the questions that come up every week become the next improvements.
Good support teaches
The best support answers the question and leaves the customer better at their job. It explains why the report came out that way and what to check next time before picking up the phone. Over a year, a customer who gets that kind of help needs support less, uses more of the product and gets more for what they pay.
That’s a harder measure to put on a dashboard than tickets closed, and it’s the one that matters.
What to ask before you sign up
You won’t see support in a demo, so ask about it directly. Who answers when I phone? Are they employees who work on this product, or an outsourced desk reading from a script? How long do they take to respond at month end, when everyone phones at once? Can I speak to someone in support before I sign?
Then ask an existing customer the question that tells you the most. When something went wrong, how did it feel?
Hold them to it once you’ve signed
When support solves a problem, ask whether the cause will be fixed or only the symptom. When you keep asking the same question, say so, because that’s useful feedback. A good vendor will want to know. A vendor that gets defensive has told you how much they value the person on the other end of the line.
Where we stand
At Commspace, we see support as part of what our clients pay for, and we run it that way. If you’d like to see how our support team works with practices, visit www.commspace.co.za.
