Address Article Feedback

Overview

Addressing feedback in a timely manner is essential to keeping knowledge resources up to date. When someone gives feedback on an article, everyone in the group that owns the article receives an email.

 

In this article:

 

Address article feedback

  1. Locate an article with Feedback using one of the following methods:
    • Click the article link at the bottom of the feedback notification email message 
    • Click the Feedback button in the Knowledge Base to see a list of feedback customers have left for articles.

      TDX Knowledge Base Feedback navigation button highlighted
      • The list will default to articles that you own (if any).
      • Change the Owner to your Group to see all the feedback for your Group's articles.

        TDX Knowledge Base feedback search by owning group
    • Search the Knowledge Base for a particular article.
  2. Scroll down to the bottom of the article.
  3. Click the Feedback link. The number of comments is listed in parentheses.

    TDX Knowledge Article Feedback button highlighted
  4. Read the Comments.
    • Note: The first line of the feedback is determined by whether the customer clicked Yes, or No to the question Was this helpful?
  5. Determine the appropriate action
    • Should the existing article be updated? If so continue to the next step.
    • Should the existing article be retired? If so follow the retire article process.
    • Should a new article be created? If so Create a Knowledge Article.
  6. Right-click Edit Article in the right column, and select Open in new window. This allows you to refer back to the feedback that was provided as you make the necessary changes to the article.
  7. If the article has already been Published then click Save Draft.
  8. Return to the browser window displaying the Feedback.
  9. Click Marked Addressed. The feedback is addressed and the link changes to Mark Not Addressed.

    TDX Knowledge Article feedback mark addressed button highlighted

 

Following-up with customer who added feedback

A customer took the time to provide feedback on an article. Customer feedback is about taking the opportunity to look at what we're doing, as well as how, and then acting on what we learn to improve our organization, and community. It is important to respond to the person so they know their feedback has been received.

If it's good feedback, thank the customer for taking the time sharing their thoughts. It is not uncommon in the IT industry to only hear feedback when something is broken, or a customer is unhappy. However, organizations can learn, and improve, from positive feedback as well.

When responding to negative feedback, thank the customer for bringing the issue to our attention, and let them know what was done, or not done, to address it.

 

Important
Be cautious when dealing with negative feedback. Knee jerk reactions to criticism, or worse, total silence can be just as bad as never knowing about an issue.

 

Regardless of the type of feedback provided, contact the person via email and thank them for their time and helpful feedback.

Details

Article ID: 212
Created
Tue 7/7/20 9:48 AM
Modified
Thu 7/30/20 2:57 PM
https://service.alaska.edu/TDClient/36/Portal/KB/ArticleDet?ID=212
service.alaska.edu
crawl=CC-MAIN-2022-49
49776
application/http; msgtype=response
sha1:YMQZTBEUFYAPSZI3NIOKVLAO7I5PTDQA
<urn:uuid:0d9f9944-445e-48f0-8c75-6ea27b8d2003>
2022-12-02T09:47:41Z
40.90.247.53
application/xhtml+xml
sha1:T24UF6UQMMOLUDP4UBVQO3RVDHPEXJEI
<urn:uuid:471402f0-5d77-4eaa-a94e-731b39d9b859>
https://service.alaska.edu/TDClient/36/Portal/KB/ArticleDet?ID=212
response
<urn:uuid:38e27015-a0ce-463a-b525-7f9f7ea12ba2>
isPartOf: CC-MAIN-2022-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-8
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/