Adjusting the Knowledge "Attach" button in Incidents

MaxB43973023201
Tera Contributor

Hello,

 

How do you guys do to know if an Knowledge article has been used to resolve an incident/ticket within SN? I handle Knowledge for an IT Service Desk and we have alot of Knowledge that should only be seen by our Service Desk and not end-users. If we use the "Attach" button in the incident it would send it to the end-user whilst it may not be available to them or anything relevant for them.

 

In one of our test environments, I have experimented with modifying the setup so that the article URL is no longer embedded into the additional comments field for the end-user. However, we still aim to utilize this "Attach" button to be able to send articles to end-users, when it's available and suitable but this would not be possible if we do this change.

 

I think what I am looking for would be something like this:

Clicking attach asks you if you want to attach it and send it to the end-user OR ask if you want to only attach it without sending Knowledge to end-user.

 

Generally just curious to know how people do. We're trying to work with KCS so every incdient should have an Knowledge article attached and if not, then one should be created or a knowledge gap should be reported.

1 ACCEPTED SOLUTION

Mike Van Vooren
Kilo Guru

For us, we made 2 adjustments.  The first is that we switched which notes the attaching occurs with.  Instead of the OOB way of attaching to External (Customer) notes, we have it attach to Internal (Work) notes.  That ensures that none of the Callers can see the article attached by default.  The 2nd adjustment we made was a new button on the Incident form called "Share KA".  If the Incident Worker knows the article is End User facing and might have some information to help self-solve their issue, they can choose to click the button.  That would then add an External (Customer) note and trigger an email to the user with a link to the article.  As was mentioned earlier, it doesn't stop the Incident worker from sharing an IT article they do not have permission to see.  The only thing I don't like about this part of the solution is that we can't track how often the "Share KA" button is used.

View solution in original post

8 REPLIES 8

I am not sure how much of a customization it was to create that button since I am not a developer.  We have had it for many years, so there may be newer and better ways to do this that is more OOTB.

Hi Mike,

 

Can you please help me with the object name which you have customized to attach knowledge link to work notes instead of comments

Hey @Mike Van Vooren, can you tell me more about how you've set up the "Share KA" button?

 

I like the idea behind the OOB "Attach" button to share knowledge articles with the end user but want to direct them to the SP instead of the KB, and have the content/links easier to find by sending a wrap up email.

 

I've been having my own discussion about it here.

Keszia
Giga Guru

I'm very late to the party but at the article level, you can also decide who can see the article using the Can Read/Cannot Read options:

Keszia_0-1739326601444.png