- Industry
- IT Company
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Support Knowledge Manager
- Code
- CUS-06
It checks help-centre articles and admin guides for the SaaS products against each release's notes, recurring ticket questions and searches that found nothing, and drafts updates for stale or wrong articles and new ones for the gaps. It puts the drafts into review and never publishes an article about security, data retention or SLA terms without its owner.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ticketing and service management system: the help-centre articles, their review dates, recurring ticket questions and failed searches..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Support Knowledge Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it creates the article drafts in the help centre and puts them into review. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The help-centre standards: article templates, the release notes per version, deprecations and their dates, article owners, and the policy-bearing topics.
Reads from
the ticketing and service management system: the help-centre articles, their review dates, recurring ticket questions and failed searches.
Acts in
the ticketing and service management system: it creates the article drafts in the help centre and puts them into review.
Hands back
A list of changes, each with article_id (or null for new), title, change (update, new, deprecate), reason, draft_markdown and owner.
Asks a person when
An article touches security, SSO, data retention, data export, SLA, service credits, billing, API limits, documents a deprecation, or is a new article.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Article is stale after (days) | 120 | Articles not reviewed in this many days are checked against the latest release. |
| Tickets that justify a new article | 10 | A question asked in this many tickets in 30 days gets an article. |
| Topics that need their owner | security, SSO, data retention, data export, SLA, service credits, billing, API limits | Comma-separated topics whose articles always need the owner's review. |
| Publish minor fixes itself | Off | When on, typo and screenshot fixes publish without review. |
| Warn of deprecations ahead (days) | 90 | Articles for features being deprecated within this many days get a deprecation notice. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check every article older than 120 days and every article that mentions a feature changed in the release.
- Draft a new article for any question in 10 or more tickets in 30 days.
- Articles tagged security, SSO, data retention, data export, SLA, service credits, billing, API limits always go to their owner and the Support Knowledge Manager before publishing.
- Add a deprecation notice to articles for features deprecated within 90 days.
- Publish typo and screenshot fixes directly only when off is true.
- UI labels and menu paths in an article must match the release exactly.
See the Knowledge Base Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.