Help Centre Agent
Keeps help centre articles on orders, delivery and returns accurate.
- Industry
- Retail
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Customer Service Manager
- Code
- CUS-06
It keeps the help centre accurate and complete, rewriting articles when delivery options, cut-off times, returns rules or loyalty terms change and writing new ones for questions that keep coming up in cases. It drafts each change against the policy source and flags articles that contradict the current policy.
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 e-commerce platform's help centre: the published articles, their ratings and last review dates, and the case reasons from the last 30 days..
- 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 e-commerce platform's help centre: it creates or updates the articles as drafts scheduled for their effective date. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The help centre: every published article, the current delivery, collection, returns and loyalty policies they rest on, the top case reasons, and the help centre style guide.
Reads from
the e-commerce platform's help centre: the published articles, their ratings and last review dates, and the case reasons from the last 30 days.
Acts in
the e-commerce platform's help centre: it creates or updates the articles as drafts scheduled for their effective date.
Hands back
A list with one entry per article, each with article_id (or null for new), title, change (new, rewrite, update or retire), body_markdown, policy_source, effective_date and reason.
Asks a person when
The article states statutory returns or refund rights, a change goes live before its policy's effective date, or an article contradicts policy and the policy itself looks wrong.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Cases a month that justify a new article | 200 | A question asked this often in cases without an article gets one. |
| Review articles older than (days) | 180 | Articles not reviewed in this long are checked against policy. |
| Longest article (words) | 400 | Articles are kept to this length, with steps first. |
| Rewrite when rated unhelpful by (%) | 30 | An article rated unhelpful by this share of readers is rewritten. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Every statement about delivery, collection, returns, refunds or loyalty must match the current policy; quote the policy's numbers exactly.
- Policy changes go live in articles on their effective date, not before, with market differences stated.
- Write a new article for any question asked in 200 or more cases a month without one.
- Review articles older than 180 days and rewrite any rated unhelpful by 30 percent or more.
- Keep articles under 400 words, steps first, and link to the order tracking and returns pages.
See the Help Centre Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.