A year and a half ago I released my first premium WordPress plugin, Advanced Ads. It’s true that once the plugin was out, my most important task was support. Support is a crucial element that determines not only the success of the project, but also how happy everyone will be, me included.
With this in mind, I constantly optimized my approach to providing support. Let me share with you what I learned. Read on to find out:
- what I learned about support,
- the four sides that will help you understand each request,
- which fears of mine proved to be unfounded,
- what an efficient support system looks like,
- how to optimize support.
What Is Support?
The main purpose of support is to help people use and understand a product. Therefore, support is not only an email reply or documentation. It extends to the following:
- making features self-explanatory,
- writing understandable labels,
- fixing issues caused by other plugins,
- making the user feel like you are ready to help.
Beside helping others use your product, you also benefit from support.
The Few Speak for the Many
I spend a lot of time with every problem reported for the first time, because I know that for every person who reaches out, many more might not and either live with the pain or go somewhere else.
Further Reading on SmashingMag:
- Supporting Your Product: How To Provide Technical Support
- WordPress Essentials: How To Create A WordPress Plugin
- How To Deliver Exceptional Client Service
- Making A WordPress Plugin That Uses Service APIs
If your plugin is a free product hosted on an open platform like the WordPress plugin directory or is a paid product in a marketplace like Envato, many people will at least scan the reviews. I am extremely proud of the 4.8 rating of Advanced Ads, and almost all of the reviews emphasize the support. This probably doesn’t hurt sales.
Learn More About Your Users
Most of the features and add-ons of Advanced Ads are based on feedback from users. Be open and they will tell you what features they are looking for. Their feedback will also help you find mistakes in your documentation, missing examples and poorly labelled buttons.
The Four Sides Of A Message
I was lucky to have learned of the four-sides model during my studies in university. It basically states that only when all four aspects of a message are considered can a conversation be considered effective.
Let’s take a look at the contents of a not-so-uncommon support request:
I can’t activate the plugin.
Facts are the objective matter. In this statement, the user is telling us that it is technically impossible for them to activate the plugin.
You might reply with a solution if the message is clear, or you might ask for details, like whether they are referring to installing the plugin or activating the license key.
What is the sender telling you about him or herself? Because some key information is missing, they might be inexperienced in asking for support. They also might be in a hurry, given the brevity.
The user is also telling me what they think of me. Do they value my time less than their own? Are they embarrassed to ask for my help and so are keeping it short? In general, adding some friendly words or even a simple “Hi” is a good start for both sides.
Finally, the user wants me to do something. Clearly, their message has no obvious call to action, so you need to find out. Sending a link to the instructions or a list of possible issues, plus an invitation to contact you again with more information, is normally a welcomed reply to general questions of this nature.
Taking the four aspects of a message into account helps me to find out a lot more information in even the shortest of requests and helps me to anticipate the right response in terms of both content and tone. Normally, their following reply to you will tell you whether you’ve done well.
Putting yourself in their shoes also helps. I worked as a freelance developer for a couple of years and am a publisher myself, so there is hardly a situation I haven’t found myself in. Just letting the user know that you can relate to their situation is a huge step forward in any conversation that has a rocky start.
Keep in mind the four-sides model not only for messages you receive, but for ones you send out as well.
Being Right Is Not Helpful
The four-sides model also tells us that being right does not necessarily help. It might address the technical issue yet ignore the mental state of the user.
Consider the following reply from a plugin developer on WordPress when a user expressed worry about their ad statistics:
The stats in [plugin’s name] work just fine, but they are often hindered by caching plugins and crap like that.
While they might be right that there is a compatibility issue, the user is left without a way forward and might feel bad for choosing a caching plugin and instigating the error.
As a German with a right-to-the-facts mentality, I had to learn to address the non-factual side of messages before starting my business. Now, I find that addressing the underlying aspects of a conversation helps to solve problems much better than addressing the facts only.
Things I Learned About WordPress Users
Advanced Ads was not my first plugin in the WordPress directory, so I knew that support requests could be tough. Would users constantly complain, demand more features, or leave bad reviews without giving me the chance to fix them?
The truth is that all of these happen but, thankfully, are the exception. In fact, I do have to compliment the community for all of the positive feedback and help I’ve received.
Users Read Documentation
People are definitely reading the documentation and tutorials and watching the videos to learn how your software works and how to fix their issues. I know this because most requests of a kind stop after a solution has been added to the documentation.
It also helps to make users aware of the documentation by linking to it in your reply, rather than copying the text into your message.
Users Are Thankful
I’ve learned that most users appreciate hard work, a friendly tone and genuine concern for their problem. Helpful support still seems to be the exception, so standing out in this area should be easy for you.
24⁄7 Support Is Not Needed
A small team can’t possibly offer support around the clock. So, the more you show that you are just a human being, the more people will respect that you breathe, eat, sleep and have weekends, too. 24⁄7 support is not needed, so you don’t need to promise it.
Users Do Try Hard
Most WordPress users are not tech-savvy. However, I’ve learned that they are eager to try. They don’t seem to have a problem sending a
debug.log file or copying a message from the error console, if you provide a link to a tutorial.
Negative Feedback Is Not the End
The first review Advanced Ads received on WordPress had a rating of one star. I was devastated and thought that was the end already. After going back and forth with the user, we cleared up the issue, and step by step, the review changed to five stars.
Direct messages from users often start out negative, too. If you understand the frustration people can have when something doesn’t work as expected and you’re cool and helpful in your reply, you might experience a conversation like this:
Client: I would like my money back for the Pro purchase. None of the features are useable. Please let me know the next steps for getting a refund. If you do not agree that a refund is needed, I’ll initiate a dispute with PayPal or, ultimately, with my credit card linked to PayPal.
Me: There is no need to open a dispute.
To be honest, I would like to learn more about the issue to be able to prevent it, in case it is not a conflict caused by another plugin. But your first priority is your site, and as a publisher I respect that without condition.
I just initiated a refund through PayPal and hope you find a working solution for your site.
Client: Thanks, Thomas. Yeah, there are a lot of moving parts of my site. […] I really do appreciate your help. The plugin is the best I have tried among the many for ad injection. Keep up the good work.
When you consider the four sides of a message, you will see that this conversation was saved with the “relationship” side, not by arguing. It started with a dispute and ended with a motivating compliment.
Show That You Exist
If you are now convinced that users have a positive attitude towards your software, you’ll probably want them to reach out to you. How do you do that?
I started by putting my name (and picture) on almost everything. You can find it in the sidebar of the home page, on WordPress and even in some messages in the plugin.
As a result, the vast majority of emails I get start with “Hi Thomas.” Many of them even include a small remark about how much they like my plugins or the articles I write about ads.
Think for a moment about the plugins you use and which of them have personal branding. How do you feel about them?
Personalization also helps both sides to remember that humans are involved. It is harder to curse someone whose name you know than to curse Company X that doesn’t even have an imprint on the website.
A Decent Help Desk
My first version of a help desk was simply my email inbox. There was really no reason to set up anything sophisticated before knowing whether this project was going to succeed. The only thing I regret is using my personal email address, rather than a dedicated one.
When Advanced Ads became my main project, the second version of my help desk was the bug-tracking tool Redmine, which I’ve used for other projects. This was better for following threads and for asking others to help out.
More than a year after getting started, I switched to Help Scout. I saw it being used by Yoast and Easy Digital Downloads and had been finding helpful advice on its blog. This was definitely a huge step forward in support, especially because of certain features:
- It integrates with my plugin store, resends receipts with one click, displays license keys and links to purchases.
- It adds and removes subscribers to my MailChimp newsletter.
- It prepares common replies.
- You can set internal notes for yourself and colleagues.
- Keyboard shortcuts are supported.
Another useful feature is that users can rate replies. I personally find the written feedback most important to improving my service.
For those of you who provide support of some kind, here are a few more tips that might help you.
Having a dedicated page where users can leave feature requests and vote for other people’s ideas almost eliminated such requests from my help desk. I set up a feature requests page using the Idea Factory plugin.
The page is also a practical way to say no to feature requests, because the votes makes it obvious which ones you should focus on.
Set Up an FAQ Page
When I reply to requests outside of my help desk and ask people to contact me directly via email, I don’t give an email address, but rather link to the support page. Users will find the address there, as well as a short FAQ section and links to common issues.
Find the Lesson in Every Request
I believe there is a lesson in every support thread. It could be an issue to solve, a tutorial to write or a label to change. You don’t need to act on every single one, but over time you will see patterns.
Learn to Say No
Despite my genuine willingness to help, saying no is the key to staying sane. I can’t help every user set up the plugin, fix every third-party theme or implement every feature request. Start practicing actively saying no once per day and you will notice that you have more energy to focus on key tasks.
Be Honest With Yourself
I am not a miracle worker, and even the best support system is time-consuming. Be aware that you might be spending most of your week on support. Your time (and income) should justify this.
Set the Tone
If you like people and value the time they spend getting in touch with you, then hardly anything can go wrong in support. Set a positive and welcoming tone with a simple line in your initial reply. Some examples:
I am sorry to hear about your issue.
Thanks for reaching out.
I hope you are well.
I am glad to hear from you again.
You’d be surprised by how this changes the rest of the conversation.
Nurture Your Passionate Users
After a while, you will notice a few passionate users. They are the ones who update first, read your update messages and contact you when something doesn’t work.
The funny thing is that they are often the ones who first get in touch about issues, or make complaints or otherwise give negative feedback.
Be Nicer Than the Last Message
As a rule of thumb, try to be one level nicer than the message you get. Either add a nice comment or simply don’t act on your first negative impulse. Of course, saying that you’re overwhelmed with joy when a user sends you a bug report might be a bit much.
The lesson I’ve learned in support is that it is often more about people than hard facts. This is especially true when dealing with people who are building their first WordPress website, purchasing their first premium product or writing their first email to a help desk. When we welcome these people to the community with a helpful and positive reply, we not only help them fix their issue, but strengthen the community as a whole.
After all, the foundation of WordPress is communication. On that note, let me know your thoughts in the comments.