- Industry
- Insure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Compliance Officer
- Code
- CUS-06
It keeps the policyholder help centre accurate: it rewrites articles when a policy wording, claims process or premium payment option changes, and drafts new articles where service cases show a gap. It sends any article that describes cover or a regulatory right for compliance review.
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 document and correspondence system: the help centre articles with their tags and review dates, and the policy wording change log..
- 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 document and correspondence system: it saves the updated articles and publishes those that need no review. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The help centre articles, the policy wording change log, the claims process maps, the top service case reasons and the plain-language standard.
Reads from
the document and correspondence system: the help centre articles with their tags and review dates, and the policy wording change log.
Acts in
the document and correspondence system: it saves the updated articles and publishes those that need no review.
Hands back
A list with one entry per article, each with article_id (or null for new), title, change (new, rewrite, minor_fix or retire), body, tags and needs_review (true or false).
Asks a person when
The article is tagged cover, exclusions, cancellation_rights, complaints, free_look, or the change alters what the help centre says about cover or customer rights.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review articles older than (days) | 180 | Articles not reviewed in this long are queued for review. |
| Cases a month that show a gap | 25 | A case reason this frequent with no article gets a new article. |
| Tags that need compliance review | cover, exclusions, cancellation_rights, complaints, free_look | Comma-separated article tags. |
| Publish minor fixes itself | On | When on, typo and link fixes publish without review. |
| Reading grade | 7 | Articles are written at or below this grade. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rewrite every article affected by a wording or process change before the change takes effect.
- Draft a new article when a case reason passes 25 cases a month and no article covers it.
- Queue articles not reviewed in 180 days.
- Articles tagged cover, exclusions, cancellation_rights, complaints, free_look go to the Compliance Officer; when on is true, typo and link fixes publish directly.
- Write at reading grade 7 and cite the wording section behind each cover statement.
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.