- Industry
- Oil & Gas
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Customer Service Manager
- Code
- CUS-06
It checks help articles for fuel customers against product data sheet changes, portal releases, recurring ticket questions and searches that found nothing, and drafts updates and new articles. It puts the drafts into review in the help centre and never publishes a change to a safety data sheet, a product specification or a policy itself.
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 help centre: the articles, their tags and review dates, and search logs..
- 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 Customer Service Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the help centre: it creates or updates article drafts in review, and publishes minor fixes when allowed. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The help centre standards: article templates, the list of safety and specification articles, the review owners for each, and plain-language rules.
Reads from
the help centre: the articles, their tags and review dates, and search logs.
Acts in
the help centre: it creates or updates article drafts in review, and publishes minor fixes when allowed.
Hands back
A list of changes, each with article_id (or null for new), title, change (update, new or retire), draft, reason and publish (true or false).
Asks a person when
A change touches an article tagged safety data sheet, product specification, credit terms, pricing, emergency or retires an article.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Stale after (days) | 180 | Articles not reviewed in this time are checked. |
| Tickets that justify a new article | 10 | A question asked this often gets an article. |
| Articles a person must publish | safety data sheet, product specification, credit terms, pricing, emergency | Comma-separated. |
| Publish minor fixes itself | Off | Typos and broken links only. |
| Reading level | plain | The level articles are written at. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check every article against the current data sheets and portal, and any article older than 180 days.
- Draft a new article for a question asked 10 or more times.
- Never publish an article tagged safety data sheet, product specification, credit terms, pricing, emergency; draft it for its owner.
- Copy safety data sheet content only from the current SDS revision, never summarise hazard statements.
- Publish only typo and link fixes and only when off is on, writing at a plain level.
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.