Their latest post focused on self-service FAQs on the web and the author offered the following recommendations about what a good FAQ should be and should not be:
- It should not be forced. Companies should never require their customers or users to use self-service. They can suggest it or make it more noticeable, but they should never force it.
- It should be intelligent. FAQs and self-service options that are static are worthless. The systems should update based on popularity, helpfulness, etc. There should also be humans watching the self-service systems and how customers are using them. Use Google Analytics if your system doesn’t already have an analytics tool.
- It should ask for suggestions. Like Google and LucasArts, good self-service centers should ask if articles were helpful, if they helped resolve issues, etc. To take it a step further, human representatives should ask if customers tried self-service. If they say no, ask why. The answers may be surprising.
- It should be up-to-date. There are very few things that are less helpful than an out of date help center. Make sure yours stays up-to-date and contains relevant information.
- It should be easy to navigate. It should also be easy to search. Make sure your help center is easy to navigate. It should be easy to go back, easy to explore relevant entries, and all of those good things.
See more about this in an article I recently published in TMCNet: "Treat Humans Humanely and they Might Just Like IVR".
No comments:
Post a Comment