Why are FAQs applicable to the enterprise?
A lot of people think FAQs (especially if you pronounce this | faks |) are only for online digerati (i.e., online techies). However, at their root, FAQs are the best answers to the most common questions asked by your customers or staff. This is applied knowledge management for customer care and internal support—albeit at a manually intensive, low efficiency level. If you could make this knowledge easily accessible by your customers or staff, you would have far fewer calls to your contact center or help desk (saving you lots of money).
Why are FAQs better than other forms of knowledge management?
So we established that FAQs are nascent forms of knowledge management…so what? Why is this better than other forms of knowledge management (KM), such as inferential case management systems, expert artificial intelligence system, Bayesian knowledge trees or recommendation engines?
Every year, customer support organizations pour millions of dollars into systems and approaches to automate knowledge management to achieve the triple goal of reducing contact center calls, call time and callback rate. Most of these programs do their job of managing knowledge but rarely achieve these reduction calls for a simple reason: they manage knowledge in a way that is optimal for IT, not in a way that is optimal for how human beings obtain knowledge. (If you don’t believe me, contact me to discuss over $200-million USD of real-world examples using ALL of the alternate KM techniques listed above.)
When people call you for help, they start by asking a question. Once they ask this question, they do not want to proceed down a tree of 19 other questions (they case-based version of “Twenty Questions”), they simply want an answer. If you have ever studied contact center traffic, you will find that on a given day or week, the large people are calling about limited set of items. If you can pull together the answers to the questions and make them easily to access, you can address the large majority of your customers’ (or staff members’) needs. Basically, this is management and provision of FAQs for your staff and customers.
If FAQs are better, why are enterprises not widely using them?
If you ever managed a FAQ list, you know this it is intensely manual process:
- First, you need to look at all your submitted questions
- Next, you need to categorize them and combine similar questions into one
- Then you need to write answers
- Finally, you need to post all of this in an easy-to-use format
This is hard enough in a static world. It is next-to-impossible in a dynamic world where the question of the day or week is always changing—and at high volume. This is why few enterprises use FAQs for knowledge management and support.
Why IFAQs (a.k.a. FAQs 2.0) is the answer
Interactive FAQs allow enterprises to manage and scale use of FAQs to manage customer care and support knowledge. To see why, we first need to define what an IFAQ is:
I•FAQ |ˈī fak| (noun)
Abbreviation for: Interactive Frequently Asked Question(s)
Definition: Content organization in the form of questions and answers about the use or operation of a particular product or service that is managed using a two-way flow of information between those asking the questions and those providing the answers.
- Open IFAQs enable anyone to ask questions or provide answers. These fully leverage open network behaviors, both for maximum flow of information and maximum exposure to redirection
- Hybrid IFAQs enable anyone to ask questions but limit who is able to provide answers (usually to approved experts). Hybrid IFAQs respond more slowly but add the benefit of providing enterprise-certified answers
Both types of IFAQs are social networks. Managers of these networks can moderate their content to ensure user generated content remains focused on the core topics of the IFAQ
Alternate terminology: FAQ 2.0 |ˈfak toō pɔint ō|
With non-interactive knowledge management systems, the enterprise has to “guess” what knowledge it staff or customer needs. Enterprises typically do this by analyzing past requests then providing knowledge to their support staff – after the fact.
IFAQs turn this around entirely:
- First and foremost, customers drive the process. They submit questions directly to the enterprise. (The enterprise responds by answering these questions.)
- This dynamic builds the true list of most frequently asked questions. As this occurs, customers can look at the answers to these common questions (instead of asking new questions)
- It is adaptive in real-time. When customers have a new concern, they immediate ask these questions. As soon as the enterprise answers the new question all other customers can see it. This can prevent call volume by detecting and publicly address of new issues as soon as they emerge
What makes a good IFAQ service?
To be effective an IFAQ service must have the following features and characteristics:
- Have an easy-to-use, intuitive interface. If you do not provide this, your customers will not want to use it
- Support multimedia content. A picture can be more useful than a thousand words; a video contains thousands of pictures (i.e., frames). Allowing both questions and answers to contain pictures, videos, audio and documents will make them much more compelling (compelling enough to get someone to use these vs. picking up the phone).
- Be able to organize questions around topics and calls-to-action. If you do not provide this you will get the “big pile of questions and answers” that makes it impossible for people to find what they need. I call social calls-to-action “social campaigns”
- Enable customers to submit, rate, and comment upon content. If you do not do this, you will not know if your answers are like, helpful or even correct. By letting users vote on your content, you can drive the best content to the top. But letting them expand upon it, you can learn better ways to present your answers to make them more effective.
- Provide rich moderation controls. You need to be able to manage what who can ask questions and who can answer them. You also need to be able to edit and remove duplicate or incorrect content. You also need to enable your users to report inappropriate content (and automatically remove content when a set number of people report this). If you do not provide this, you will lose control of your network
- Support enterprise integration. You will want to add this onto your enterprise. That means you will want to be able to integrate with employee directories and your CRM or ITIL Management systems. This is the difference between making an amateur or proof-of-concept IFAQ and an enterprise one.
- Integrate business intelligence. If you cannot analyze and report on how the IFAQ is used, you cannot measure its enterprise value.
Essentially, these are all principles of delivering a robust, purpose-driven social network focused on ideation.
How close are we to this?
To quote the old “Six Million Dollar Man” show, “we have the technology; we can build [it].” However, it is not a question of having the technology, it is more of positioning it use. Positioned correctly, you not only can use this for customer care but also to drive revenue: Imagine answering a question with a description, instructional video and hyperlink to purchasing a product or service to perform this. That turns a cost of support into a sales lead. (If this sounds unreal, a quick demonstration example can be found here).