Recent searches


No recent searches

Feature request: Ability to have an 'Internal' section (visible to Agents & Admins) at the bottom of articles that are only visible to Signed-In Users



Posted Feb 19, 2025

We would like to request a supported method to have an ‘Internal’ section to the bottom of articles that are visible to customers.  So, for articles that are visible to ‘Signed-in Users’, we would like to be able to have a section at the bottom of the article which is only visible to ‘Agents and admins’. 

 

The use case is that it is convenient to be able to add notes for internal viewers that provides further background on the subject matter, like the ticket that an article was spawned from, or the Jira that it is linked to, or any further internal information that is relevant.  Internal Notes would be a reference to help internal agile communication.

 

Presently, we have a customized method that we use to do this.  Internal Comments can be added to our articles using a simple Custom CSS and JavaScript.  The Internal section is seen when viewed by an Admin/Agent, but is not seen when viewed by a Signed-in User (a customer).  

 

The trouble is that when we implement Ultimate Bots (recently renamed to Zendesk ‘AI Agents Advanced’), then although the internal text is not seen by the Signed-in User, the Ultimate bot answer does provide information from that internal section to the user.  We don't want this to happen.

 

After discussing this with Zendesk support in ticket 13337690, we have been told that our ‘Internal section method’ is out of scope and an Ultimate Bot limitation, as the bot does not have a way of knowing what it should/should not tell the enduser(requester).

 

So our Feature Request is two fold:

 

1) Provide the ability to insert an ‘internal section’ to the bottom of Signed-in Users articles, that is viewable to Agents/Admins

2) Ensure that Ultimate Bots ( Zendesk ‘AI Agents Advanced’) do not make suggestions to Signed-in users, based on the information in the internal section

 

Workaround until the feature is implemented:

- Have two articles.  One containing Signed-in user visible info, and a second article that holds the internal information and references the public article.


2

2

2 comments

Upvote from me. This is something that would be very useful. 

 

For example having a customer process for raising an issue, followed by an internal area that provides the process for the support team to follow to resolve the issue for the client.

 

This is functionality that's also available on other knowledge based applications, so will be valued here and saves time having to create two separate articles.

0


image avatar

Shawna James

Community Product Feedback Specialist

Hey there,
 
Thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review. For others who may be interested in this feature request, please add your support by upvoting this post and/or adding your use case to the comments below. Thank you again!

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post