The knowledge section in the context panel uses Answer Bot to automatically provide relevant suggestions that you can use to answer questions in your tickets. You can also manually search your help center to find additional content, then link to the content or quote the content directly in the ticket (see Searching, linking, and quoting content in tickets).
To flag an article in Knowledge
- In the ticket that you are working on, click the Knowledge icon (
) in the context panel. - Search for the article you want to flag, then click the article to open it.
- Hover over the paragraph that you want to add feedback to.
- Click the More menu icon (
) to the right of the paragraph that you want to provide feedback for, then click Add feedback.
Note: You can only flag articles, you cannot flag Community posts.
- In the Add feedback field, describe what needs to be changed.
- Click Send feedback.
You'll receive a confirmation notification that your feedback has been submitted, with a link to the ticket that was created.
The ticket includes:
-
A link to the article that needs the update
-
A link to the ticket that is the source of the update
-
The user name of the agent who flagged the ticket
-
The inline comments added by the agent
-
On Enterprise plans, the ticket is automatically assigned to the owner of the article to review. If the information about the owner is not available, the ticket will remain unassigned. On other plans, the ticket will remain unassigned.
The article you flagged is captured in the Knowledge Capture dashboard for reporting (see Analyzing your Knowledge Capture activity).
6 Comments
Is it possible to configure the review workflow? For example, we already have a system built that sends 'flagged' articles to review by a senior agent level for triage, before landing at the top Publisher level. We use triggers and macros to make the flow work. This gives us much more control and helps drive accountability with knowledge.
Hello, I just wanted to propose an update to this article. We just spend two weeks of emailing back and forth with ZD-support, only to find there's an important distinction to make, in regards to a flagged article being automatically assigned to the author and your currently subscribed (guide) plan.
The article owner feature is an Enterprise Guide plan only feature! In essence there will be no ticket automatically assigned to the author of the article if your guide plan is Professional or lower. Flagging is available in the plans indicated by this article. A yellow note block pointing out this distinction to the other readers will possibly save others the time.
ZD-support was outstanding, I'd like to add! Very attentive, folllowed-up every single day, even if there was no update available from the internal team. A workaround has been proposed which is still to be verified, but I have no doubt it will work as proposed.
Hi Jan-Willem Rossée,
Thanks for bringing our attention to this. There was ambiguity in the article. We have updated it to indicate that the owner (not the author) is assigned to the ticket.
Hello, we just started with article flagging with one of our agents and this is what's happened: 1) She was able to flag the article and submit the ticket however I, the manager of Help Center content cannot see the flagged ticket and haven't received a notification either that an article was flagged. Notes for your investigation: neither the creator nor the author of the article still work at our company. Does this explain why I can't find the ticket?
2) We did a 2nd test, in which the agent flags an article and this time they weren't even able to "send feedback", the system would just spin for over 5 minutes. She even logged out and in of Zendesk to refresh the system, but it still would just spin. Clicking on cancel would also not stop the process. (Please see screenshot.)
Thanks in advance for your help. Our admin is on vacation and I'm desperate for help before we start with training.
Hi Shirin,
Thank you for reporting these issues. We are looking at the first one. We will soon deploy the fix for the second one.
Please sign in to leave a comment.