Get To Know the Developer’s Support Policies<\/h2>\n
The best time to find out about a plugin’s support policy is before<\/em> you need it. That’s because support should be part of your criteria<\/a> for choosing which plugins to install.<\/p>\n If hosted at the official WordPress Plugins<\/a> repository, it’s worth checking out the plugin’s respective support forum. This will give you an idea of what types of issues are occurring and how quickly the developer responds to new posts.<\/p>\n WordPress plugin developer C. Michael Nelson<\/a> also recommends contacting support before you use a plugin, adding “That will show you how helpful they will be later, once you’re really invested in it. Avoid using plugins with bad tech support from the beginning.”<\/p>\n Besides timeliness, it’s also great to know what is and isn’t covered by technical support. For instance, some developers provide limited help with questions regarding writing custom code. And if a plugin has both free and commercial versions \u2013 the paying customers usually get priority service.<\/p>\n The more you know ahead of time, the better off you’ll be should something go wrong.<\/p>\n Perhaps the most common piece of advice I received was about providing a detailed description of the issue you’re experiencing. This makes sense as remotely (or anecdotally) troubleshooting a website works best when having as much information as possible.<\/p>\n It’s an important piece of the puzzle. So much so that GiveWP’s Director of Customer Service and Support Ben Meredith<\/a> even did a WordCamp presentation<\/a> on the subject.<\/p>\n Describing the issue starts with a few key items, according to developer Kerch McConlogue<\/a>:<\/p>\n Beyond those basics, there is plenty of other helpful information to send along, including:<\/p>\n Rick Alday<\/a>, who provides support for GiveWP, also recommends doing some basic troubleshooting before contacting support. This may allow you to find the cause of an issue, if not resolve it outright.<\/p>\n Some plugins provide troubleshooting steps in their documentation. For example, Alan Fuller<\/a> of Fullworks shared an outline<\/a> of steps that could be useful for debugging virtually any plugin. The results can then be shared with support.<\/p>\n Speaking of documentation, WordPress contributor Courtney Robertson<\/a> advised users to search within the plugin’s support area or using Google. “Add some keywords and skim for the issue BEFORE reaching out. Then state having searched for these things in the request.”, she noted.<\/p>\n The goal is to be as clear, detailed, and concise as possible. And not to worry if you don’t have in-depth technical knowledge. Just give it your best effort. As Puneet Sabherwal<\/a> opined, \u201cA sound support system doesn’t expect a user to be knowledgeable. That is a support provider’s qualification.”<\/p>\n None of us enjoy dealing with website issues. At the very least it can be frustrating. The worse the problem is, the easier it is to become impatient.<\/p>\n But it’s also worth remembering that technical support is being provided by human beings. They have feelings, strengths, and weaknesses \u2013 just like everyone else. Several support experts brought up the importance of the human element.<\/p>\n And the process takes time. Product founder and podcast host Dave Rodenbaugh<\/a> says those seeking support should, “Be patient! Support teams will respond within a day if they’re on the ball.”<\/p>\n Ian Misner<\/a> recommends responding promptly, as \u201cYou’re almost certainly going to get quicker responses\u2026Context stays fresh, which makes helping you easier.\u201d<\/p>\n Tom Sepper<\/a> is Chief Customer Officer at Kinsta web hosting. He says that “One of the things I stress for my teams is genuinely showing empathy for customers – fellow humans – and their specific situations. And that works both ways.<\/p>\n “As a user, have empathy for the human on the other end of the conversation. Support teams aren’t always the ones able to fix all problems, nor are they the cause of all problems. These individuals do what they do because they receive great satisfaction in helping others succeed\u2026showing genuine empathy in how you interact with support teams goes a very long way.”<\/p>\n A lot of effort goes into building and supporting a WordPress plugin. It’s a big responsibility<\/a>. And so much depends on starting the process on the right foot.<\/p>\n That’s why the first contact you make with technical support staff is important. As users, our job is to paint a picture of what’s happening. From there, it’s about accurate and efficient communication between both parties.<\/p>\n And while the outcome won’t always be perfect, following the advice above should increase your chances of a resolution.<\/p>\n Finally, many thanks to the experts who participated in this guide! By sharing their knowledge and experiences, they have benefited the entire WordPress community.<\/p>\n The post How to Get the Best Technical Support for WordPress Plugins<\/a> appeared first on Speckyboy Design Magazine<\/a>.<\/p>\n Source: Specky Boy<\/p>\n![\"Read](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/09\/great-wp-support-01.jpg?resize=900%2C400&ssl=1\")
<\/p>\nBe Detailed in Your Support Request<\/h2>\n
\n
\n
![\"Try](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/09\/great-wp-support-02.jpg?resize=900%2C400&ssl=1\")
<\/p>\nDemonstrate Empathy and Patience<\/h2>\n
![\"Showing](\"https:\/\/i0.wp.com\/speckyboy.com\/wp-content\/uploads\/2022\/09\/great-wp-support-03.jpg?resize=900%2C400&ssl=1\")
<\/p>\nYou Get What You Give<\/h2>\n