While working for a telecom operator, I tested the idea of having people paying more for dedicated support. We did a market study. I turned out that customers are not ready to pay for support. Cognitively, paying for a service and paying on top for this service to work well is not consistent. As a result, people have minimal support and complain. But they don't value good support either. NB: companies do pay for (ins…
Building relationships with customers through support didn't turn out as hoped
121–130 of 205 posts
Re: Building relationships with customers through support didn't turn out as hoped
#122IMO this is the problem with the standard App Store business model: free with In-App Purchase. In that situation, the vast majority of people who email you are not customers but rather freeloaders.
My own App Store apps are all upfront paid, which eliminates the freeloaders, so support emails never overwhelm me. Perhaps I'm not maximizing my potential revenue, but I'm doing fine and prefer this business model and relationship with users.
Even with regard to bug reports, paid customers are more invested in doing some "work", responding to my requests for more information about the issue, because they've already invested money into the app and want a return for their investment.
Re: Building relationships with customers through support didn't turn out as hoped
#123US Mobile, TJ's, Amazon, Apple, Mullvad, HN come to mind when I think of companies with great support and I recommend them because of it.
All of these are closer to essential services with competition and frequent problems so I appreciate and interact with the support frequently.
Re: Building relationships with customers through support didn't turn out as hoped
#124The author hired someone with technical knowledge, but that's not enough. Technical knowledge and people skills are different things. If someone has taken the effort to contact you, they likely already have a bad first impression of you. If your response is focused on "educating the customer" or is too conscious of what's fair for the business itself, it will probably not impress. Great customer support is the kind t…
> If someone has taken the effort to contact you, they likely already have a bad first impression of you. Quite the opposite. If somebody has a bad first impression, they will not bother contacting a business. They'll find an alternative.
If I contact a company to decide if I want to become their customer, I probably like them.
If I contact a company about a post-sales problem or for technical support, it's a different story.
Re: Building relationships with customers through support didn't turn out as hoped
#125When I started doing technical interviews I wanted to be different than other companies giving canned unfortunately.
I naively thought that explaining candidates what went wrong would be appreciated, because I would've wanted to know if I was in their position.
To the guy that had 20 technologies in their CV but failed to answer on any topics I would suggest:
"Anything you put on a CV increases the risk of you being asked about it. Maybe try to move those you don't want to talk about to previous experiences instead of a "skills" section. If you list C but can't answer basic pointer or compilation questions, or you put Node.js but can't talk about eventemitters or TypeScript but can't describe a union, you are casting a giant doubt in the other 17 technologies you have listed, even though you might be great at them."
Just to be met with a 300+ likes post on LinkedIn about how my company expected the impossible, was _hiring a team instead of an individual_ and how I was the worst interviewer in the world.
I thought it was a one off, but months later I would get occasionally angry candidates emails arguing my feedback and how I didn't understand how good they are.
Then I realized why corporate bs talk it is the way it is. Genuine content and feedback, especially in the social media age is a liability, it has more cons than pros.
Re: Building relationships with customers through support didn't turn out as hoped
#126This seems an incorrect assumption, or at least a conclusion built on incomplete information and consideration of additional factors. The first one that comes to mind is that these customers will on average be the heaviest users. That doesn’t make them less valuable, that makes them the exact ones most like to be willing to refer others to your product and the most able to do so with specifics on their recommendations and, hopefully, a positive endorsement of the service received, not just the product features.
This implies another aspect as well: even if good support weren’t to get you wider positive awareness, poor customer service and even average service that nonetheless has more negative recommendations to other can lose you business, and that too can have a compounding effect.
In general there’s also no getting around the fact that a smaller number of people will (or should) have disproportionate support requests, unless you’ve got a very homogeneous user base with homogenized use patterns. Or your products &/or documentation are of poor quality.
It’s probably not a bad idea also to take most support requests that aren’t inherently specific to a customer and require intervention as an opportunity & need to review your documentation, perhaps auto surface the most relevant bits it when a person submits a request with a an option “if this answered your question click here and we’ll mark your message as resolved, otherwise we have it, and will be in contact with”.
There’s no getting around the need to provide support and it’s possible for some businesses there could be an ideal global min/max that provides least effort & service cost for then elasticity of price & quality and customer tolerance, but I think if you find yourself in the mindset of “what’s the worst I can get away with” instead of “most I can afford to optimize long term contentment and good will referrals, you could be looking at things wrong. I’m not sure what “relationship” should mean in any case, if not something like what I’ve described.
Re: Building relationships with customers through support didn't turn out as hoped
#127Re: Building relationships with customers through support didn't turn out as hoped
#128Earlier quoted context omitted.
> If someone has taken the effort to contact you, they likely already have a bad first impression of you. Quite the opposite. If somebody has a bad first impression, they will not bother contacting a business. They'll find an alternative.
It depends on the nature of the interaction. If I contact a company to decide if I want to become their customer, I probably like them. If I contact a company about a post-sales problem or for technical support, it's a different story.
Then that's not your first impression.
Re: Building relationships with customers through support didn't turn out as hoped
#129Earlier quoted context omitted.
That isn't the same thing at all. If I buy version 2 then it's mine and I can continue to use it for as long as I want, if I'm happy with the feature set. I can ignore version 3 or choose to buy it. If I buy it then I now own two products instead of one. Sometimes the older version might even be better (e.g. features I like have been removed or made worse). With a subscription model I'm forced to pay again and again…
In theory you are correct but realistically you will upgrade.
Given "there was a time that subscriptions for software were virtually unheard of", it's safe to assume we're talking about more than a couple of years ago. To talk as if most users always used to upgrade, suggests you might be young enough not to remember the software industry before a decade or two ago.
In general, users very much didn't upgrade. That's exactly why the industry forced subscriptions on us. They weren't getting income anymore, when the older version of their software did the job perfectly well.
Re: Building relationships with customers through support didn't turn out as hoped
#130>I’ve rarely gotten useful answers from support from services I use. I thought if I used my own product every day, read every email and answered it thoughtfully, people would appreciate this, and it would build some degree of loyalty and appreciation. I run an app with 16,000 users and receive 2–5 support tickets per week. I read every one of them. Around 20% of my app has been built based on user suggestions. People…
This is all going to hinge in a tremendous way based on what kind of app you have and who your users are.
Sometimes people link to our "guides", like this one https://macrocodex.app/knowledge/measure/bodyfat/
my app is in fitness field https://macrocodex.app/ and the people who use it are:
1. Bodybuilders
2. Overweight / obese / skinny fat / underweight individuals
3. General gym crowd
Bodybuilders, well they immediately understand the app on first impression.
One user told me he has kidney disease and asked if I could add a “low protein” diet mode, so he could reduce protein intake below standard recommendations. I had never faced this requirement before, but after hearing him out, I decided to add it. This is just one of the many interactions.
Then there is another group, people who have spent a long time being underweight or overweight and have started attributing it to genetics. I often see posts like “I am genetically fat” or “I am an ectomorph / hardgainer"; "I can’t gain weight no matter how much I eat” in subreddits and fitness groups. Don't you dare to call them out of anything, they'll get mad! but are willing to give app try especially if they hear about it from someone else.
They typically use it for 2–5 weeks, and then they start gaining or losing weight depending on their goal. They are genuinely surprised that it’s possible.
Once they start seeing results, they usually just keep going.
I am not particularly good at communication, nor a guy with social skill.