Plan requirement
| Subscription | Suite Enterprise or higher, Knowledge Enterprise |
| Access | Agent |
There is no review date on an article. Reminders come from a verification rule, which is a different shape and changes how you set them up.
How reminders arrive
- In Knowledge, click the settings icon and select Article verification.
- Create a rule with a Frequency and Filters that select the articles it covers.
- Check the Owner on those articles, because the owner is who gets the emails.
The rule runs weekly. Any article it covers that has not been verified within the frequency is set to unverified, lands on the Needs verification list, and its owner starts receiving reminder emails every two weeks. Verifying the article is the only thing that stops them.
Set the frequency for a reason
Not a blanket year for everything. The frequency belongs to the rule rather than to the article, so the way to give one article a different rhythm is to give it a label and a rule of its own. Tie the interval to what makes those articles go stale.
- A subject that changes with every release. Short interval, its own rule.
- Process and policy. A year is usually right.
- Anything mentioning a year in the text. Worth a label so it is checked before that year ends.
A known release date or a contract renewal is not something a rule can be pointed at. Those are diary entries, and pretending the tool will remember them for you is how they get missed.
The owner is the whole mechanism
Reminders go to the article's owner, so an article owned by somebody who has left sends its reminders nowhere and quietly ages. An owner that is a group survives people changing jobs, which is the argument for using one.
Reviewing is not rewriting
Most reviews take two minutes: read it, confirm it is still true, verify it. Only some need work.
Teams that treat review as a rewrite stop doing it, which is why framing it as a quick check matters.
Comments
0 comments
Article is closed for comments.