Customer Service: Answers – Organizing answers

Through click-track analysis and feedback on answers, your answers are automatically organized. Answer rankings are constantly updated using the solved count value and presented to your customers with the most useful information first. RightNow uses 3 techniques to gather useful information about answers.

  • Explicit customer feedback: By default, the Answers page offers customers a way to rate answers through the “Was this answer helpful?” option. Their responses automatically raise or lower the solved count of answers.
  • Explicit ranking of the answers: You can explicitly rank answers at certain levels in the knowledge base using the Display Position setting. This is often useful when new issues arise.
  • Click-track analysis: RightNow analyses the path each customer takes through the knowledge base. The use and benefits are two-fold:
  1. Answer relatedness: An affinity map is built which relates answers that customers view to other answers viewed during the same visit. Through the SmartAssistant feature, RightNow Service suggests answers to them based on the historical relationships of that answer to other answers in the knowledge base. The suggested answers appear as learned links on the Relationships tab.
  2. Implicit ranking: The click-track data is also used for answer ranking. Each time an answer is viewed by a customer or suggested by an agent, its solved count is increased

The Solved Count feature collects information about the usefulness of answers in your knowledge base and uses this data to rank your answers. Implicit data is compiled by how customers select and view answers. Explicit data is compiled by how customers rate the effectiveness of individual answers. Both long-term and short-term solved counts are used to calculate the score. Solved counts from the customer portal account for 75% of an answer’s score, and agent solved counts for 25 %. Using the solved count values, RightNow can dynamically rank the answers by their usefulness and present customers with the most effective answers first.

An answer’s score value is a calculated value equal to the answer’s solved count combined with any “fix at” positions specified for the answer in the Display Position drop-down menu when adding or editing an answer.

  • Implicit ratings: gathered as customers view answers. If a customer views an answer, the solved count of the 1st answer is increased, but not as much as the 2nd viewed answer. In other words, the answer that the customer views last receives the largest solved count increase. Previously viewed answers receive a smaller increase in their solved counts. The solved count is also increased when an agent uses a SmartAssistant suggested answer when responding to a customer’s question.
  • Explicit ratings: gathered from the response to the question, “Was this answer helpful?”. This question is displayed on the Answers page on the customer portal.

Over time, an unused answer’s solved count will gradually decline or age. For example if an answer has not been viewed for 30 days (the default setting), the solved count will automatically be reduced. The solved count of unused answers also declines at a constant rate over time. Ultimately, if an answer has not been viewed for an extended period of time, the answer’s solved count can reach zero.

When an answer’s solved count reaches zero, this usually means that the answer has not been viewed for a long time, and it is safe to assume that the information may be outdated or not useful. By default, these aged answers are automatically set to the Review status when their solved count reaches zero. This enables you to easily sort the outdated answers and update them.

When a customer submits comments or suggestions from the feedback form, an unresolved incident is automatically created.

Customer Service: Answers – Seeding knowledge base

Customers use your site to find answers to their questions about the services and products your organization provides. To assist your customers in finding the information they are looking for, you can create answers to common questions and post them on your customer portal. As a result, you are able to provide a better customer experience because your customers are able to quickly find the answers to their questions.

You can format answers to include links, tables, graphics, and other features, making your support site more interactive and visually appealing. In addition, RightNow provides you with a revolutionary method of knowledge base management that enables you to overcome the critical problems associated with a manually constructed knowledge base.

Maintenance of your knowledge base is minimized because of automated processes that learn from customers using your site, then automatically rank answers and display the most useful answers first.

Seeding the knowledge base

RightNow ability to start with only 15 to 20 answers eliminates the need for a comprehensive initial knowledge set, which significantly speeds and simplifies the implementation. Most organizations can build their initial seed from existing online questions and answers, documents, or customer support interactions.

RightNow Propose Answer feature enables agents to suggest that certain incidents become public answers, allowing you to seamlessly create public answers from the real issues that your customers are facing (agents must have Propose permission in their profile).

Creating useful answers will enhance the search process for customers, allowing them to find pertinent information quickly without needing to do multiple searches. A knowledge base containing well-crafted answers will also optimize the self-learning features of RightNow that continually index, group, link, and rank the answers in the knowledge base.

These self-learning features are the backbone of self-service, enabling you to present the most historically useful answers first and to suggest answers related to the customer’s current question. In addition, effective answers will make your maintenance tasks easier as information ages and changes.

Use the following guidelines to create clear, focused answers:

  • Create one-topic answers: Think of each public answer in your knowledge base as one topic or the answer to one question. One-topic answers improve searching and grouping, which enable customers to easily find answers. One-topic answers provide brief, pertinent information without clutter. A knowledge base of unique answers also simplifies management and maintenance.
  • Provide adequate detail: Because RightNow indexes the text of the Summary, Question, and Answer fields into words and phrases for text searching and answer grouping, answers should contain an adequate amount of text that explains the issue. With limited text, there are very few indexed words for the answer, and the words that are indexed cannot fully represent the context of the answer. As a result, the answer may be difficult to find during text searching. With too much text (over two pages), you run the risk of writing about several topics and covering too broad of a context. The resulting set of indexed words may not span the entire text of the answer. In effect, the answer can be found during dissimilar searches in which that answer is not relevant.
  • Write a concise summary: The quality of the summary, meaning how closely it summarizes the contents of an answer, is critical to the effectiveness of the answer and affects its display position, how it links to related answers, and how it is grouped with similar answers. On the Answers page, customers will choose to open and read or skip over an answer based on the summary. Without a concise summary, customers may not open the answer, which directly impacts its display position and how it is linked with other answers. The summary should state what the customer can expect to learn by reading the answer or what question will be answered.
  • Create explicit keywords: Sometimes, you may not be able to capture the entire contents of an answer in the one-sentence summary. The Keyword field is an additional field, not viewable by customers, used during keyword indexing of an answer. You can enter supplemental keywords, phrases, or text that represents the answer’s contents. Keywords should be separated by commas, with grouped words separated by spaces (for example, “cell phones, calling plans, accessories”). You should be deliberate with the words you enter because they are weighted higher. Be sure to include a thorough, yet concise section of keywords.

When you publish answers, you make them available to the public on your customer portal. Answers can be either public or private, as well as have specific visibility settings for each interface or for contacts based on access levels defined in their SLAs.

Whether answers are visible on your customer portal is determined by what you specify in certain fields. The five key fields that determine how and where answers are presented are Answer Status, Answer Access Level, Language, Products and Categories, and Conditional Sections.

In order for answers to appear on the customer portal, the Status, Access Level, Language, Product, and Category fields must be set to a visibility that allows access by customers. If even one field does not allow visibility, the answer will not be available on the customer portal.

In addition, if you have sections within an answer with restricted visibility, that section must be assigned an access level associated with the answer. The five fields that control answer visibility are described in detail below.

  • Answer status: The primary factor that determines the visibility of answers is answer status. There can be many custom answer statuses, but all must be either a Public or Private status type, which is determined when the custom status is created. Answers set to a status that has a Private status type can never be viewed on the customer portal, regardless of their access or language assignment. Public answers may be viewable through the customer portal, depending on the other fields selected. Two of the default answer statuses are Review and Proposed, both of which have a Private status type. When agents propose an incident to become an answer, it is copied and set to the Proposed status with an access level of Everyone. Since the Proposed status is a Private status type, the answer will not be visible to customers. An answer changes to the Review status when its solved count reaches zero or when the date specified when adding or editing an answer is reached. The Review status will automatically remove the answer from the customer portal.
  • Answer access level: Access levels determine whether customers can view answers on a per-interface basis. If an answer is set to an access level that has customer visibility on one of the interfaces, then that answer is viewable by everyone on that interface, provided the remaining fields also allow visibility. If an access level does not provide visibility to customers for a certain interface, access can still be given to specific contacts by assigning them SLAs that allow privileged access. One of the default access levels for answers is Everyone. This access level allows all customers to have access to the answer on all interfaces (Example of other Access Levels: Platinum, Gold, Silver).
  • Language: Answer visibility is also determined by the language assigned to it. If assigned to a specific language, an answer will only be visible on the interfaces using that language, as long as the answer status and access level also allow visibility.
  • Products and categories: The visibility settings for the products and categories associated with the answer will also affect the visibility. If the answer is assigned to a product or category that is not visible to customers on a particular interface, the answer will also not be visible to customers, unless it is assigned to another product or category that is visible on the interface. In other words, if you have an answer that is assigned to two products, and one of the products is not visible on the interface, but the other product is, your answer will appear on the interface. However, if the answer is assigned to two products, and neither product is visible on the interface, your answer will not appear on the interface under any circumstances.
  • Conditional sections: Conditional sections help control visibility of certain sections within an answer. If a section of the answer is assigned an access level that is not visible to customers on a particular interface, but the answer is visible, then customers are able to view the answer but not the conditional section.

Customizable Menus: Answer statuses

An answer’s status controls whether it is public and describes its state in the knowledge base. RightNow Service provides 4 default answer statuses, described in the following list. Every answer status is associated with a status type that is either Public or Private.

  • Private: The Private answer status prevents answers from being displayed on the administration interface and the customer portal. It is associated with the Private status type.
  • Proposed: Answers with the Proposed status are incidents that agents have submitted as potential answers for the knowledge base. Proposed answers are associated with the Private status type.
  • Public: Answers with the Public status are visible on the customer portal. Public answers have a Public status type.
  • Review: The Review answer status means the answer should be evaluated to determine if it is still necessary. An answer’s status is set to Review when it has been part of the knowledge base for a specified amount of time or when it’s solved count reaches zero. Answers with a Review status are associated with a Private status type by default.

If you delete a custom answer status, all answers with that status are changed to have either a Public or Private status, depending on the status type of the deleted answer status. For example, if you delete a custom answer status with a Public status type, all answers that were associated with that status are changed to Public status with the Public answer status type.

(Click to enlarge)
(Click to enlarge)