It’s a common misconception that generating/managing help center content takes a lot of energy; I know I used to believe it. The reality is that this view is far from the truth. Excellent sources of help center content are all around you. Below you will find a breakdown of some very surprising sources of help center content.
It’s time that I tell the story of the first help center that I ever built.
This introspective tale is one full of mistakes and hard lessons (it’s also incredibly embarrassing). In sharing this moment, it is my hope that I will be able to prevent at least one person from making the same mistakes that I have.
Anybody can build a help center; it’s not that complicated. The difficulty lies in actually making your help center useful. Without careful planning and forethought, the only thing that you will end up with is a haphazardly strung together series of text. And, the only results this will provide you with is you and your users/team/customers wasting untold amounts of time.
Whether you’re designing a new help center, or updating an existing one, it’s important to have a solid grasp on common design patterns that are at your disposal. In this article, we will not only walk you through the three most common help center design patterns, but we will also explain what they mean for you.
How much does support cost you? How do you calculate the Return on Investment (ROI) for the money that you put into helping your customers? Is there even an actual ROI? These are not uncommon questions.
Published content on your site, or in your application, needs to be perfect, right? It needs to be revised, precise, and in line with guidelines. But is that really true?
frequently always get asked about the approval process. And our answer might surprise you: sure, we can implement customized approval processes for customers in genuine need, but we’re honestly against it.