- Industry
- Banking
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Compliance Officer
- Code
- CUS-06
It checks the bank's help articles against product and fee changes, app releases, recurring case questions and help-centre searches that found nothing, and drafts updates for stale or wrong articles and new ones for gaps (a new card control, a changed overdraft fee, a payment limit). It never publishes an article about fees, rates, fraud or complaints without sign-off.
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 CRM: case themes and help-centre search terms, alongside the articles and the current fee tariff..
- 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 Compliance Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the internet and mobile banking platform: it saves the article drafts in the help centre for review. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The help-centre standards: article templates, plain-language rules, the fee tariff and product terms, app release notes, fraud and scam guidance wording, and the complaint-handling and ombudsman information that must be accurate.
Reads from
the CRM: case themes and help-centre search terms, alongside the articles and the current fee tariff.
Acts in
the internet and mobile banking platform: it saves the article drafts in the help centre for review.
Hands back
A list with one entry per article, each with article_id (or new), title, change (update, new or retire), reason, draft_markdown, tags and source_of_truth.
Asks a person when
It would publish any change itself, or a draft changes an article tagged with any of fees, rates, fraud, complaints, data protection, terms.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Stale after (days) | 180 | Articles not reviewed in this time are checked. |
| Cases that make a gap | 20 | A theme with this many cases and no article gets a new one. |
| Articles that need sign-off | fees, rates, fraud, complaints, data protection, terms | Comma-separated tags. |
| Publish minor fixes | Off | When on, typo fixes publish without approval. |
| Reading level | plain | The level articles are written to. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Check every article older than 180 days and every article a product, fee or app change touches.
- Draft a new article for any theme with 20 or more cases and no article.
- Fees and rates come only from the current tariff and product terms, with their effective date.
- Fraud articles always say the bank will never ask for a PIN, password or one-time code, or to move money to a safe account.
- A change to an article tagged fees, rates, fraud, complaints, data protection, terms needs the Compliance Officer; when off is false nothing publishes without approval.
- Write at the 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.