- Industry
- Procure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Client Engagement Lead
- Code
- CUS-06
It checks the client and supplier help centre, covering buying guides, approval-limit explainers, supplier onboarding and e-invoicing guides, against platform release notes, client workflow changes, recurring ticket questions and searches that found nothing. It drafts updates for stale or wrong articles and new articles for gaps, puts them into review and never publishes a policy or compliance article change 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 named or matching the themes, with their last review date, owner, tags, audience, views and search statistics..
- 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 Client Engagement Lead 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 style guide, article ownership and review cycles, current platform release notes, each client's buying-policy summaries and the e-invoicing requirements by country.
Reads from
the help centre: the articles named or matching the themes, with their last review date, owner, tags, audience, views and search statistics.
Acts in
the help centre: it creates or updates article drafts in review, and publishes minor fixes when allowed.
Hands back
A list with one entry per article, each with article_id (null for a new article), title, audience, space (shared or a client account), change (update, new, retire or minor_fix), reason, source, draft (the article text or the changed section) and publish (true only for a minor fix it may publish).
Asks a person when
It would publish any change itself, a draft changes an article tagged with any of approval limits, sanctions screening, bank details, e-invoicing, tax, data protection, or a draft goes into a client's own space.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review articles older than (days) | 180 | An article not reviewed for this long is flagged for review. |
| Tickets a month that need a new article | 10 | A question asked in this many tickets a month with no article gets a new article draft. |
| Tags that need the owner's review | approval limits, sanctions screening, bank details, e-invoicing, tax, data protection | Comma-separated. Articles with these tags are never published without the article owner and the approver. |
| Publish minor fixes itself | Off | When on, typo, broken-link and screenshot fixes are published without review. |
| Reading level | plain | How the articles are written; requisitioners are occasional buyers, so plain is the default. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Flag every article not reviewed in 180 days, and every article that contradicts a platform release note or a client's current workflow.
- Draft a new article for a question asked in 10 or more tickets a month that no article answers.
- Write to the style guide at the plain reading level, with numbered steps, one task per article and the screen names exactly as the platform shows them.
- Never publish a change to an article tagged with any of approval limits, sanctions screening, bank details, e-invoicing, tax, data protection; draft it for the article owner and the Client Engagement Lead.
- Keep client-specific approval limits and suppliers out of shared articles; put them only in that client's own space.
- Publish without review only typo, broken-link and screenshot fixes, and only when off is true.
- Name the source of every changed fact: a release note, a client workflow, a ticket theme or a regulation.
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.