Skip to main content
Not Taken : Idea will not be considered

Internal Notes on Solution Articles

Related products:Freshservice
  • July 21, 2022
  • 5 replies
  • 127 views

bryanpds
Apprentice
Forum|alt.badge.img+1

Solution Articles should have a field to be able to add “internal notes”. This would be helpful for information on when the information was last verified, caveats to the information that is presented, etc. 

 

It would be visible in the agent-side of the knowledge but not in the portal.

5 replies

dengstrom
Contributor
Forum|alt.badge.img+3
  • Contributor
  • April 10, 2023

Agreed! I have upvoted this request. I made the same request before noticing this one. 

 

 


alyssia.correa
Skilled Expert
Forum|alt.badge.img+8
New IdeaNot Taken : Idea will not be considered

pOttenbacher
Contributor
Forum|alt.badge.img+3
  • Contributor
  • June 10, 2025

Why was this not taken? Can we please have some feedback instead of just seeing what equates to “Ticket closed” on these ideas that are worth more consideration than that?


Forum|alt.badge.img+3
  • Contributor
  • November 21, 2025

Not everyone is responsible for writing or maintaining Solution articles. Some agents are taking a high volume of tickets and just need a quick way to notify the person who owns the article that something needs to be updated. Forcing those agents to open the article in edit mode, save a draft, and send for approval is the wrong workflow. Internal comments would let them flag issues without touching the content or becoming article editors.

This is bad knowledge management.

Knowledge management is supposed to make it easy for the people doing the work to share what they’ve learned. When you block agents from leaving internal comments on Solution articles, you remove the simplest and most natural path for sharing that knowledge.


  • November 23, 2025

Why was this idea not taken! That is terrible. Especially when it comes to feedback in regards to an article, this is a good idea. If someone wants to add notes to a knowledge article where even just the knowledge officer can read, that would be very useful.

 

Or even hide different section for different Requester groups to see. E.g. only allow part of the article to be seen my Requester Groups and then the Technical information can only be visible to the agents. That way you do not have to create two separate articles for the same process. It is all in one article but various sections are hidden for only certain groups to be able to see.