As an entrepreneur setting up your ecommerce business, design standards for your help pages are not necessarily the first things you think of. But for customer loyalty they’re vital.
If your customer has to get help post-purchase, they want quick, easy answers to their simple questions. CEB, a research firm who investigate best practices in customer loyalty, reported that 67% of customers prefer self-service over talking to your team.
Recent studies have found intuitive and simple self-service to be vital for customer lifetime value:
It’s clear that ecommerce businesses need to present help pages in the most efficient way for our customers.
So how can we make self-service so simple that it keeps our customers happy and reduces the support queue for our customer service teams? By analyzing what goes into truly great help pages and designing our templates, themes and layouts to be frictionless for the customer to navigate.
That means applying these seven design standards to our help pages.
If you’re not familiar with what a design standard is, they’re simply a set of rules that web designers follow to align with visitors’ expectations. Design standards are guidelines for clarity and usability.
To give a clearer picture of what goes into a great example of a help page, we looked across the top 50 ecommerce retailers to find out how standard these standards really are. Using guidelines from a Nielsen Group article, we use the following thresholds:
Note: The sites included in this research are the top retail ecommerce sites in the “Shopping” category on Alexa.
Only 38% of top retail ecommerce sites have a well placed search bar.
70% of retail businesses have easily accessible links to their frequent questions or FAQs.
96% of retail businesses have short help page titles – making short tiles with main keywords a design standard.
80% of retail businesses are giving clear categories and topics for their readers – this is just on the level of a standard.
90% of retail businesses make it easy to request further help. We considered a “contact us” button, an email address, or an icon for a live chat or messenger app as a way to request help.
Only 66% of retail ecommerce help pages are using white space in their formatting to help the reader’s eye. White space among retail ecommerce stores is a convention and not a standard.
Only 24% of help pages offer navigation options that aren’t too overwhelming for customers.
Not all design standards are standard. Three out of seven retail ecommerce help pages met criteria for design standards. Of the four remaining design standards, these fell into two conventions and two confusions.
Let’s look at why these design standards matter and some examples of websites that use them well, and not so well.
Having a search bar is a design best practice, it helps your customers easily navigate to relevant help pages.
A help page without a search bar means your customer has to click and navigate their way around, read plenty of lists and hopefully stumble across the right page. This makes for a really high effort and frustrating customer experience.
Good example: This search bar catches your attention as soon as you hit their help page.
Bad example: This help page forces customers to click around to get their answer.
Having a table with 5 to 6 FAQs on your help page reduces the amount of inbound support request you receive.
Deflecting requests for help away from your support team is the goal of all help pages.
Your support teams are already understaffed and have a big support queue to deal with. Having a clear section to give customers quick help is essential. If you don’t, it results in frustrated customers and angry emails for your support team to handle.
Good example: This page caters to common problems, and directs customers straight to the FAQ section.
Bad example: By other design standards this help page is ideal, but it needs a devoted section of 5-6 FAQs if they want to help customers faster.
Similar to how people Google search in “caveman English”, expect help page browsing to be the same.
According to CoSchedule, a tool that helps you write better headlines, when skimming content most readers tend to read the first and last three words of a headline.
If you’re looking at giving customers information on your ecommerce store’s return shipping costs, a headline like “Return Shipping Costs: What Charges to Expect” is going to work a lot better for content scanning than “What Is the Price of Return Shipping to Company A?”
Good example: Address the problem in the least amount of words to help customers scan titles quickly.
Bad example: Not offering help pages is bad enough, but making the focal point of your knowledge base to increase revenue is even worse.
Icons or at least organized text is a great way to communicate and display the categories or topics where your customer might need help. Customers don’t want to spend a lot of time trying to help themselves. They want to get in, grab their answer and go.
Good example: These clear categories give customers the best chance of self-service success.
Bad example: A list is better than nothing, but putting that information in a table would create effortless browsing.
There may come a time when a customer’s need is too complicated for one help page. This is why having a phone number, email address, contact button or live chat option is essential to helping customers get their solution with the least amount of effort.
Offer the channel where you can provide the best help as quick as possible. If you don’t man the phone, don’t list a phone number. List an email address instead.
Good example: Sets clear expectations of availability and offer multiple channels where the customer can achieve help.
Bad example: Typically you’d expect an email address or contact form right at the bottom of the page, but neither of those are listed. There’s a telephone number, but what’s it for – sales or customer service? Let the customer know!
White space is an essential part of readability on your help pages. If they’re not structured clearly and readers are not able to scan pages easily, expect a lot of support requests because they just won’t be bothered to look over a poorly designed page.
Along with headings, subheadings and bullet points, images and videos add a better dynamic to your help pages but also help break up large pieces of text.
Good example: Personal introduction offering many ways to self-serve that the eye can easily navigate.
Bad example: This help page is too crowded. It takes a lot of work to find the option you’re looking for.
Your customers are there to help themselves not to browse more products. Be empathetic to your customer’s needs and keep your navigation relevant to what they might struggle with, instead of trying to upsell them.
Good example: A great example of helping a customer get the kind of support they need right off the bat.
Bad example: Will the navigation along the top help you get specialized help with a watch or will you be looking at the online catalog for new watches? Keep navigation relevant to getting answers more easily and more quickly.
There’s a lot to analyze in design standards. While compiling this list we had to be careful that we weren’t crossing over into what goes into web design standards of a homepage.
What we did was use the research at the top of this article, empathize with the customer and put ourselves in their shoes. Then we simply asked ourselves, what would a help page look like if it provide a frictionless customer experience?
We also looked outside of the area of retail and at bigger businesses that showcase excellent design examples of knowledge bases and help pages.
Look how easy both of these help pages from Netflix and Lynda make it easy for customers to get in and get out with an answer, just like the customer wants:
Retail ecommerce businesses might have specific design requirements and needs which draw them away from adhering to design standards. Some of those reasons could be due to brand standards, coding standards, and accessibility standards.
But with the risk of breaking web conventions, you also break the user experience of your website.
Results from a Nielsen Group survey on Bucknell University’s website redesign on how it broke away from some long-established conventions reported that prospective students and users of the site found it increasingly hard to find the relevant information.
Although the website redesign sparked a lot of social and blog attention, both good and bad feedback from critics, the site actually ruined its user experience with several participants struggling to find:
In moving away from web design standards, Bucknell University actually ruined its prospective business by hiding core information behind a fancy design.
Whether you’re searching the web for a help page template, theme or layout, there are design requirements you should consider when you build a help page to give your customers easy self-service.
Understand that the design of your help page dramatically effects the amount of effort a customer has to put into finding the correct bit of information to help themselves to a solution. You want to present this information in the most intuitive way possible and make it easy for all of your customers to find a solution.
While no web conventions strictly exist for a help page, it can be agreed that arranging your information in the most effective way through clear topics or categories, using smart titles for your articles and always providing the option for your customer to seek further help is a best practice when it comes to building a great help page.